(→Tools) |
(→Upcoming Features) |
||
| Line 37: | Line 37: | ||
== Upcoming Features == | == Upcoming Features == | ||
| - | + | <!-- | |
MeeGo Bugzilla lists the following features for MeeGo 1.2. The below proposal are all accepted and are on their way to MeeGo 1.2 release. | MeeGo Bugzilla lists the following features for MeeGo 1.2. The below proposal are all accepted and are on their way to MeeGo 1.2 release. | ||
| Line 59: | Line 59: | ||
** Proposal 1: Maemo6 NGF (non-graphic feedback) | ** Proposal 1: Maemo6 NGF (non-graphic feedback) | ||
*** ''The device has functionality to alert user of a call, alarms and notification (SMS, email, chat, system update) events. Events may or may not have a graphical part and it may have different behavior depending on the system state. Example of this is receiving an SMS message when there is no other activity and SMS message during a call. NGF provides a unified API for apps to request logical events. The actions (e.g,. play/show LED+audio+vibra) are combined in NGF and consistent look&feel is provided''. | *** ''The device has functionality to alert user of a call, alarms and notification (SMS, email, chat, system update) events. Events may or may not have a graphical part and it may have different behavior depending on the system state. Example of this is receiving an SMS message when there is no other activity and SMS message during a call. NGF provides a unified API for apps to request logical events. The actions (e.g,. play/show LED+audio+vibra) are combined in NGF and consistent look&feel is provided''. | ||
| - | + | --> | |
* PIM Storage in Evolution Data Server (EDS) and email via Camel, SyncEvolution as sync engine | * PIM Storage in Evolution Data Server (EDS) and email via Camel, SyncEvolution as sync engine | ||
** architecture decision to move towards EDS and Camel [http://lists.meego.com/pipermail/meego-dev/2011-March/481890.html announced] | ** architecture decision to move towards EDS and Camel [http://lists.meego.com/pipermail/meego-dev/2011-March/481890.html announced] | ||
Contents |
MeeGo architecture team is responsible for defining and managing the MeeGo architecture. MeeGo architecture consists of Core OS layer and number of UX verticals on top the Core OS layer. The architecture team decides which component to use for the functionality needed in MeeGo with the objective of consistency inside the Core OS and to the applications that run above it.
Architecture tools