Difference between revisions of "User:Alsroot/trash/Frame Panels"

From Sugar Labs
Jump to navigation Jump to search
Line 21: Line 21:
 
== Detailed Description ==
 
== Detailed Description ==
  
Basic points:
+
* Follow [[Design Team/Proposals/Journal]] mockups
* follow [[Design Team/Proposals/Journal]] mockups
+
* Support plugins for different UI modes
* support plugins for different UI modes
 
 
** Journal plugin(for 0.86+ its a part of sugar package, for <0.86 releases it could be separate activity as well)
 
** Journal plugin(for 0.86+ its a part of sugar package, for <0.86 releases it could be separate activity as well)
 
** Books plugin, Calibre-like(or so) for browsing books(formed in separate activity)
 
** Books plugin, Calibre-like(or so) for browsing books(formed in separate activity)
Line 29: Line 28:
 
** Video plugin for browsing view files(formed in separate activity)
 
** Video plugin for browsing view files(formed in separate activity)
 
** ..
 
** ..
* provide all necessary functionality for plugins
+
* Provide all necessary functionality for plugins
  
 
'''NOTE''' Separate activities is not a task for this feature proposal.
 
'''NOTE''' Separate activities is not a task for this feature proposal.

Revision as of 11:11, 9 July 2009


Summary

One code base for all object browsing related functionality.

Owner

Current status

  • Targeted release: 0.86
  • Last updated: Thu Jul 9 00:36:45 UTC 2009
  • Percentage of completion: 0%

Detailed Description

  • Follow Design Team/Proposals/Journal mockups
  • Support plugins for different UI modes
    • Journal plugin(for 0.86+ its a part of sugar package, for <0.86 releases it could be separate activity as well)
    • Books plugin, Calibre-like(or so) for browsing books(formed in separate activity)
    • Audio plugin for browsing audio files(formed in separate activity)
    • Video plugin for browsing view files(formed in separate activity)
    • ..
  • Provide all necessary functionality for plugins

NOTE Separate activities is not a task for this feature proposal.

Benefit to Sugar

Browsing different types of sugar object looks the same in many cases(search, tagging etc.). So, keep unified code base and do not split it could be useful idea.

Scope

  • affects Journal code in sugar package
  • adds new activity for <0.86 releases
  • Datastore API should provide tags functionality for 0.86+

How To Test

In progress..

User Experience

All objects browsing features will look equally. It should mean that users will reuse theirs Journal experience in browsing books for example.

Dependencies

For >=0.86, all functionality will come from sugar package, for <0.86 it will be packaged in activity.

Contingency Plan

None necessary, revert to previous release behaviour.

Documentation

Release Notes

In progress..

Comments and Discussion

Features Subpages