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

From Sugar Labs
Jump to navigation Jump to search
 
(31 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
<noinclude>{{GoogleTrans-en}}{{TOCright}}
 
<noinclude>{{GoogleTrans-en}}{{TOCright}}
−
[[Category:Feature Page Incomplete]]
+
[[Category:FeatureObsoleted|Unified Browser for Objects]]</noinclude>
−
[[Category:Feature|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 ==
  
−
Plugins for different view types in Journal.
+
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 ==
  
−
Purposes to have special Journal plugins API instead of regular activities:
+
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.
−
* security reasons, browsing Journal entries and launch/remove/change objects could be denied for regular activities in next sugar releases
 
−
* Journal integration
 
  
−
==== UI modes ====
+
Any of four panels could be stuck i.e. let user see its components all time.
  
−
Unified Browser supports plugins for different UI modes:
+
=== Predefined components ===
−
* Journal objects-centric plugin
 
−
* Books plugin, Calibre-like(or so) for browsing books
 
−
* Audio plugin for browsing audio files
 
−
* Video plugin for browsing video files
 
−
* Plugin to browse .xol collections(instead of using sidebar in Browse)
 
−
* ..
 
  
−
So, we could have plugins for different purposes i.e. Journal plugin could be very common/simple but something like plugin for Books/Video/etc can have some special UI features (that look redundant in Journal plugin).
+
* rings switch
−
 
+
* activities list
−
For sugar-0.88+, Journal will load all installed plugins and provide possibility to switch between them, for <0.88 plugins will be formed in separated activities.
+
* clipboard
−
 
+
* users list
−
For sugar-0.88+, Journal plugin will be packaged with sugar, other plugins could be packaged into activities and have separate code base. In 0.88+ environment, these activities will use plugins engine from current sugar, for <0.88 environments (and for 0.88+ glucose releases when plugin uses newer engine), plugins engine will be packaged into activity bundles.
+
* sources list
−
 
+
* network component
−
'''NOTE''' Separate plugins/activities is not a task for this feature proposal.
+
* notification area
−
 
 
−
==== Plugins engine ====
 
−
 
 
−
Browser provides backwards compatible and versioned plugins engine API:
 
−
* ''v0'' engine for glucose-0.84/0.86
 
−
* ''v1'' engine for glucose-0.88(+)
 
−
 
 
−
Engine provides all necessary functionality for plugins:
 
−
* TreeViewModel as a source of objects; so, all pulugins should use TreeViewModel for list widgets
 
−
** for local objects (rich client for <0.88 and thin client for >=0.88)
 
−
** for remote p2p objects
 
−
** for remote server objects
 
−
** aggregated sources (combine several sources)
 
−
* UI widgets, like TreeView, TableView, tag clouds etc.
 
−
* shell related procedures(like activate objects)
 
  
 
== 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 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 ==
  
 
* affects Journal code in sugar package
 
* 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 75: 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 ==

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

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

Retrieved from "https://wiki.sugarlabs.org/index.php?title=User:Alsroot/trash/Frame_Panels&oldid=90239"