628
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + − [[Category:Feature|Unified Browser for Objects]]</noinclude> Line 51:
Line 50: − What we see in current Journal view, will be Journal plugin. Plugin could use the whole window(API will provide default components like Journal toolbar), so bookmarks related UI components should be placed to frame window.+ − + − Necessary operations:+ − − − * switch between bookmarks − * change view plugin for current set − * share bookmark − * let other users know that someone has shared bookmarks Line 67:
Line 60: − All objects browsing features will look equally. It should mean that users will reuse theirs Journal experience in browsing books for example.+
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>{{GoogleTrans-en}}{{TOCright}}
[[Category:Feature Ready for Release Manager]]
[[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.
== 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
* create new bookmark, process could be initiated by plugin's UI component but we need common method to name newly created bookmark
* delete stored bookmark
== How To Test ==
== How To Test ==
== User Experience ==
== User Experience ==
* sugar frame as a regular GNOME panels
== Dependencies ==
== Dependencies ==