Changes

Jump to navigation Jump to search
Line 24: Line 24:  
== Detailed Description ==
 
== Detailed Description ==
   −
The reason for 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
     −
=== Data model ===
+
=== Predefined components ===
   −
* the whole variety of Journal objects could be represented by sets(default set is all objects)
+
* rings switch
* any set has tag list of objects in set, every tag has count of objects in this set
+
* activities list
* any set could be reduced by query terms(tags or/and search string)
+
* clipboard
* every set could be bookmarked(by saving query terms)
+
* users list
* bookmarked sets could be shared for other sugar users
+
* sources list
 
+
* network component
=== View model ===
+
* notification area
 
  −
* data sets could be browsed in various Journal plugins(default plugin is Journal)
  −
* user can change view plugin any time to browse current set
  −
* user can reduce current set by changing query terms(process of querying entirely depends on plugin)
  −
* user can bookmark current set(current query terms)
  −
* bookmarked sets have prefered plugin to browse
      
== Benefit to Sugar ==
 
== Benefit to Sugar ==

Navigation menu