Changes

Jump to navigation Jump to search
2,172 bytes removed ,  11:56, 12 July 2009
→‎Decoupling of Sucrose: move to Features/Decoupling_of_Sucrose
Line 258: Line 258:  
** etc.
 
** etc.
 
* Owner/Coordinator: Aleksey
 
* Owner/Coordinator: Aleksey
  −
==== Decoupling of Sucrose ====
  −
The major idea is to have tough core(with stable release cycle) <=> dbus-API/sugar-toolkit-API(in ideal only dbus) <=> unlimited count of activities that uses core functionality and do not follow 6 months release cycle(which could be overmuch for activity).
  −
  −
It could looks like:
  −
* '''core''' - glucose, six months(or so) release cycle, w/o any activities, only API
  −
** in ideal, it should have only dbus API
  −
* '''bridge''' - [[Development_Team/sugar-port|sugar-port]] for example, between all(in ideal) already deployed sugars and activities i.e. it provides backwards compatibility(so the same activity code will work on all sugars) and at the same time provides features from newest sugar(so the same activity code will use last sugar's features)
  −
** we could write this level in vala to provide core functionality for wide range of programming languages
  −
* '''world''' - the rest of sugar world i.e. fructose/honey (but now there are no differences between them) that use core directly, if all deployed sugars have the same API for desired functionality(for example in case of preselected mime type, ObjectsChooser has different API for 0.82-0.86), or use bridge otherwise.<br>imho another point to have activities outside of core release cycle - activities have more shorter release cycle then core has
  −
  −
And of course deployers can form any sets from these components
  −
  −
    Core                      Bridge                        World       
  −
+------------+                                            +------------+
  −
| Sugar-0.82 |---+                                    +---| Activity A |
  −
+------------+  |    +---------------------------+  |  +------------+
  −
+------------+  |    | sugar-port                |  |  +------------+
  −
|    ...    |--dbus--| do not fail on 0.82      |---+---|    ...    |
  −
+------------+  |    | but uses all 777 features |  |  +------------+
  −
+------------+  |    +---------------------------+  |  +------------+
  −
| Sugar-777  |---+                                    +---| Activity Z |
  −
+------------+                                            +------------+
  −
  −
* Owner/Coordinator: ?
      
==== Version support for datastore ====
 
==== Version support for datastore ====

Navigation menu