Difference between revisions of "User:Alsroot/trash/Frame Panels"
Jump to navigation
Jump to search
| (16 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
<noinclude>{{GoogleTrans-en}}{{TOCright}} | <noinclude>{{GoogleTrans-en}}{{TOCright}} | ||
| − | [[Category: | + | [[Category:FeatureObsoleted|Unified Browser for Objects]]</noinclude> |
| − | |||
<!-- All fields on this form are required to be accepted. | <!-- All fields on this form are required to be accepted. | ||
| Line 10: | Line 9: | ||
== Summary == | == 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 == | == Owner == | ||
| Line 24: | Line 23: | ||
== 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 == | ||
| − | * | + | * 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 | |
| − | * | ||
| − | |||
== Scope == | == Scope == | ||
| Line 63: | Line 50: | ||
== UI Design == | == 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 == | == How To Test == | ||
| Line 79: | Line 60: | ||
== User Experience == | == User Experience == | ||
| − | + | * sugar frame as a regular GNOME panels | |
== Dependencies == | == Dependencies == | ||
Latest revision as of 14:50, 5 November 2013
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
- 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
Scope
- 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
- sugar frame as a regular GNOME panels
Dependencies
Existed glucose dependencies.
Contingency Plan
None necessary, revert to previous release behaviour.
Documentation
Release Notes
In progress..