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

 
(79 intermediate revisions by 5 users not shown)
Line 1: Line 1:
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}{{TOCright}}</noinclude>
+
<noinclude>{{GoogleTrans-en}}{{TOCright}}
 +
[[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 8: Line 9:
 
== Summary ==
 
== Summary ==
  
One code base for all object browsing related functionality.
+
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 ==
 +
 
* Name: [[User:alsroot| Aleksey Lim]]
 
* Name: [[User:alsroot| Aleksey Lim]]
 
* Email: [[Special:Emailuser/alsroot|send an email]]
 
* Email: [[Special:Emailuser/alsroot|send an email]]
  
 
== Current status ==
 
== Current status ==
* Targeted release: 0.86
+
* Targeted release: 0.88
 
* Last updated: Thu Jul  9 00:36:45 UTC 2009
 
* Last updated: Thu Jul  9 00:36:45 UTC 2009
 
* Percentage of completion: 0%
 
* Percentage of completion: 0%
Line 21: Line 23:
 
== Detailed Description ==
 
== Detailed Description ==
  
Keep all object browsing related functionality in one code base. This code base will have several UI modes i.e. Journal mode(for objects-centric notion), Calibre-like mode(for browsing books), Rhytmbox-like mode(for audio files) etc.
+
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 ==
  
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 a useful idea.
+
* 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 ==
  
It affects Journal code in sugar package, adds new activity for <0.86 releases.
+
* 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 ==
 
== How To Test ==
Line 37: Line 60:
 
== User Experience ==
 
== User Experience ==
  
All objects browsing features will look equally. It should mean that users will reuse theirs Journal  experience in browsing books for example.
+
* sugar frame as a regular GNOME panels
  
 
== Dependencies ==
 
== Dependencies ==
  
For >=0.86, all functionality will come from sugar package, for <0.86 it will be packaged in activity.
+
Existed glucose dependencies.
  
 
== Contingency Plan ==
 
== Contingency Plan ==
  
Eat my socks.
+
None necessary, revert to previous release behaviour.
  
 
== Documentation ==
 
== Documentation ==
  
None other than this page.
+
* [[Design Team/Proposals/Journal]]
  
 
== Release Notes ==
 
== Release Notes ==
''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the release team and shipped with the release.''
+
 
 +
''In progress..''
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==
 
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
 
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
 
==[[Features]] Subpages==
 
{{Special:PrefixIndex/Features/}}
 
 
[[Category:FeaturePageIncomplete]]
 
[[Category:Feature]]
 
[[Category:Feature for 0.86 Journal]]
 

Latest revision as of 15: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

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..

Comments and Discussion