628
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + + Line 8:
Line 9: − One code base for all object browsing related functionality.+ + Line 21:
Line 23: − This code follows [[Design Team/Proposals/Journal]] mockups.+ − − ==== UI modes ==== − − Unified Browser supports plugins for different UI modes: − * 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 − * .. − − 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). − − For sugar-0.86+, Journal will load all installed plugins and provide possibility to switch between them, for <0.86 plugins will be formed in separated activities. − − For sugar-0.86+, Journal plugin will be packaged with sugar, other plugins could be packaged into activities and have separate code base. In 0.86+ environment, these activities will use plugins engine from current sugar, for <0.86 environments(and for 0.86+ glucose releases when plugin uses newer engine), plugins engine will be packaged into activity bundles. − '''NOTE''' Separate activities is not a task for this feature proposal.+ − + − Browser provides backwards compatible and versioned plugins engine API:+ − + − + − + − Engine provides all necessary functionality for plugins:+ − * TreeViewModel as a source of objects; so, all pulugins should use TreeViewModel for list widgets+ − + − − ** for remote server objects − − − − 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.+ + + + − + − + + + + + Line 71:
Line 60: − All objects browsing features will look equally. It should mean that users will reuse theirs Journal experience in browsing books for example.+ − For >=0.86, all functionality will come from sugar package, for <0.86 it will be packaged in activity.+ Line 91:
Line 80: − − [[Category:Feature Page Incomplete]] − [[Category:Feature]] − [[Category:Feature 0.88]]
User:Alsroot/trash/Frame Panels (view source)
Revision as of 15:50, 5 November 2013
, 15:50, 5 November 2013no edit summary
<noinclude>{{GoogleTrans-en}}{{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.
== 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 ==
* Name: [[User:alsroot| Aleksey Lim]]
* Name: [[User:alsroot| Aleksey Lim]]
* Email: [[Special:Emailuser/alsroot|send an email]]
* Email: [[Special:Emailuser/alsroot|send an email]]
== Detailed Description ==
== 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.
==== Plugins engine ====
=== Predefined components ===
* rings switch
* ''v0'' engine for glucose-0.82/0.84
* activities list
* ''v1'' engine for glucose-0.86(+)
* clipboard
* users list
* sources list
* network component
** for local objects(rich client for <0.86 and thin client for >=0.86)
* notification area
** for remote p2p 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 ==
* 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
* adds new activity for <0.86 releases
* Datastore API should provide tags functionality for 0.86+
== 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 ==
== User Experience ==
== User Experience ==
* sugar frame as a regular GNOME panels
== Dependencies ==
== Dependencies ==
Existed glucose dependencies.
== Contingency Plan ==
== Contingency Plan ==
== 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 -->