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

From Sugar Labs
Jump to navigation Jump to search
Line 51: Line 51:
== UI Design ==
== 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.
* all of four frame panels could be stuck
* manage components, way to add-new/remove/move components
Necessary operations:
* components could have shell level key shortcuts
* 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 ==
== How To Test ==

Revision as of 00:28, 13 December 2009


Treat frame as a containers(upper, left, right and bottom) for predefined or custom components i.e. having GNOME panels analog in sugar.


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

  • let users more freedom to organize sugar shell how they want
  • provide to activity developers a way to integrate theirs activities to shell UI(useful for activities that work in background and requires some kind all-time-present indicator in UI)
  • having stable API for panel components, activity developers have more freedom and aren't stuck to core releases e.g. Network activity/component(analog of NM widget in GNOME) could support several sugar releases and previous release sugar users will benefit from last Network component.
  • previous sugar release users will benefit from last updates of predefined components as well


  • affects Journal code in sugar package

UI Design

  • all of four frame panels could be stuck
  • manage components, way to add-new/remove/move components
  • components could have shell level key shortcuts

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.


Existed glucose dependencies.

Contingency Plan

None necessary, revert to previous release behaviour.


Release Notes

In progress..

Comments and Discussion