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

(9 intermediate revisions by 4 users not shown)

Line 1:

<noinclude>{{GoogleTrans-en}}{{TOCright}}

[[Category:~~Feature Ready for Release Manager]]~~

[[Category:FeatureObsoleted|Unified Browser for Objects]]</noinclude>

~~[[Category:Feature~~|Unified Browser for Objects]]</noinclude>

<!-- All fields on this form are required to be accepted.

Line 43:

Line 42:

* 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 ==

Line 50:

== UI Design ==

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

* all of four frame panels could be stuck

* manage components, way to add-new/remove/move components

~~Necessary operations:~~

* 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~~

* switch between bookmarks

* change view plugin for current set

* share bookmark

* let other users know that someone has shared bookmarks

== How To Test ==

Line 66:

Line 60:

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

@@ Line 1: / Line 1: @@
 <noinclude>{{GoogleTrans-en}}{{TOCright}}
-[[Category:Feature Ready for Release Manager]]
+[[Category:FeatureObsoleted|Unified Browser for Objects]]</noinclude>
-[[Category:Feature|Unified Browser for Objects]]</noinclude>
 <!-- All fields on this form are required to be accepted.
@@ Line 43: / Line 42: @@
 * 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 ==
@@ Line 50: / Line 50: @@
 == UI Design ==
-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.
+* all of four frame panels could be stuck
+* manage components, way to add-new/remove/move components
-Necessary operations:
+* 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
-* switch between bookmarks
-* change view plugin for current set
-* share bookmark
-* let other users know that someone has shared bookmarks
 == How To Test ==
@@ Line 66: / Line 60: @@
 == 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 ==