Changes

Jump to navigation Jump to search
no edit summary
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 ==
   −
The reason to this feature is having Journal views for different purposes i.e. Journal plugin could be very common/simple but views for Books/Video/etc could have some special UI features. Another benefit of Journal plugins is that we can have non-core plugins and distribute them from ASLO.
+
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.
   −
Purposes to have special Journal plugins API in addition to activities API:
+
Any of four panels could be stuck i.e. let user see its components all time.
* security reasons, browsing Journal entries and launch/remove/change objects could be denied for regular activities in next sugar releases
  −
* Journal integration
  −
** fast access to plugin views
  −
** ObjectChooser integration
     −
Plugins API will provide necessary functionality:
+
=== Predefined components ===
* TreeViewModel as a source of objects; so, all pulugins should use TreeViewModel for list widgets
+
 
* UI widgets, like TreeView, TableView, tag clouds etc.
+
* rings switch
* shell related procedures(like activate objects)
+
* 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 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 51: 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 ==
628

edits

Navigation menu