Difference between revisions of "User:Alsroot/trash/Frame Panels"
| Line 24: | Line 24: | ||
== Detailed Description == | == Detailed Description == | ||
| − | The reason | + | The major reason is to let activities like FileShare or Chat special UI representation in shell's interface. It could be also useful if user wants fast access to some activities like Journal replacements. |
| − | + | Any of four panels could be stuck i.e. let user see its components all time. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | === | + | === Predefined components === |
| − | * | + | * rings switch |
| − | * | + | * activities list |
| − | * | + | * clipboard |
| − | * | + | * users list |
| − | + | * sources list | |
| − | + | * network component | |
| − | + | * notification area | |
| − | |||
| − | * | ||
| − | |||
| − | |||
| − | * | ||
| − | * | ||
== Benefit to Sugar == | == Benefit to Sugar == | ||
Revision as of 00:18, 13 December 2009
Summary
Treat frame as a containers(upper, left, right and bottom) for predefined or custom components i.e. having GNOME panels analog in sugar.
Owner
- Name: Aleksey Lim
- Email: send an email
Current status
- Targeted release: 0.88
- Last updated: Thu Jul 9 00:36:45 UTC 2009
- Percentage of completion: 0%
Detailed Description
The major reason is to let activities like FileShare or Chat special UI representation in shell's interface. It could be also useful if user wants fast access to some activities like Journal replacements.
Any of four panels could be stuck i.e. let user see its components all time.
Predefined components
- rings switch
- activities list
- clipboard
- users list
- sources list
- network component
- notification area
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.
- for now, some activities have similar functionality(browsing Journal entries), so having plugins, we will use the same theme for browsing features in sugar
- encourage developers create new view for different purposes(books, media etc.)
- having plugins we don't stick to sugar releases, deployers could create/change plugins that support not only last sugar but version which is in deployment
- having bookmarks, users can have fast access to his books/media-files/etc in the Journal(and using proper view plugin to browse them)
- shared bookmarks is more powerful and useful method of network sharing(in comparing with "Send to" option)
Scope
- affects Journal code in sugar package
UI Design
What we see in current Journal view, will be Journal plugin. Plugin could use the whole window(API will provide default components like Journal toolbar), so bookmarks related UI components should be placed to frame window.
Necessary operations:
- create new bookmark, process could be initiated by plugin's UI component but we need common method to name newly created bookmark
- delete stored bookmark
- switch between bookmarks
- change view plugin for current set
- share bookmark
- let other users know that someone has shared bookmarks
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
Existed glucose dependencies.
Contingency Plan
None necessary, revert to previous release behaviour.
Documentation
Release Notes
In progress..