Changes between Version 8 and Version 9 of SHR_Architecture

Timestamp:

03/15/10 19:08:18 (3 years ago)

Author:

Heinervdm

Comment:

Update

SHR_Architecture

@@ -1 +1 @@
 = How has SHR been built? =
-
-'''NOTE: This page is outdated! '''
 
 == Overview ==
 Please refer to the attached picture explaining how we built this architecture.
 
-There's a central daemon called '''ophonekitd''' which handles events. It's
+There's a central daemon called '''phonefsod''' which handles events. It's
 using '''libframeworkd-glib''' which is mainly a glib wrapper for dbus calls
 to frameworkd.
-There's a '''libframeworkd-phonegui''' package which describes primitives of
-what we consider "screens" having to be shown to the user.
+There's a '''libphone-ui''' package which describes primitives of
+what we consider "views" having to be shown to the user.
 
-These screens are called either by ophonekitd on events (e.g. incoming
+These screens are called either by phonefsod on events (e.g. incoming
 calls) or by the user when he initiates things (e.g. dialer,
 contacts...).
 
-There can be as many libraries implementing libframeworkd-phonegui as
+phoneuid caches those views to speed up those applications.
+
+There can be as many libraries implementing libphone-ui as
 you can think about. The one SHR is based on right now is
-libframeworkd-phonegui-efl. It's an implementation of the
-libframeworkd-phonegui headers, and it uses
+libphone-ui-shr. It's an implementation of the
+libphone-ui headers, and it uses
 libframeworkd-glib.
 
-[[Image(lf.png)]]
+[[Image(architecture.png)]]