5,705
edits
Changes
Jump to navigation
Jump to search
Line 237:
Line 237: − + − + − + − + − + − + − + − + − + − + − +
→Decoupling of Sucrose
** in ideal, it should have only dbus 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)
* '''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 the wide range of platforms
** 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
* '''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
And of course deployers can form any sets from these components
Core Bridge World
Core Bridge World
+------------+ +------------+
+------------+ +------------+
| Sugar-0.82 |---+ +---| Activity A |
| Sugar-0.82 |---+ +---| Activity A |
+------------+ | +---------------------------+ | +------------+
+------------+ | +---------------------------+ | +------------+
+------------+ | | sugar-port | | +------------+
+------------+ | | sugar-port | | +------------+
| ... |---+---| do not fail on 0.82 |---+---| ... |
| ... |--dbus--| do not fail on 0.82 |---+---| ... |
+------------+ | | but uses all 777 features | | +------------+
+------------+ | | but uses all 777 features | | +------------+
+------------+ | +---------------------------+ | +------------+
+------------+ | +---------------------------+ | +------------+
| Sugar-777 |---+ +---| Activity Z |
| Sugar-777 |---+ +---| Activity Z |
+------------+ +------------+
+------------+ +------------+
* Owner: ?
* Owner: ?