Libgconf-bridge
From Openmoko
(Difference between revisions)
(Describe usage of libgconf-bridge) |
(catchg) |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 10: | Line 10: | ||
== Architectural Details == | == Architectural Details == | ||
| − | * In case an application 'hangs' in a state we want to be able to reset the state of the application. | + | * In case an application 'hangs' in a state we want to be able to reset the state of the application. <br> This can be be done through the context menu in mainmenu. |
| − | + | ||
== Implementation Recommendations == | == Implementation Recommendations == | ||
| Line 17: | Line 16: | ||
== Unresolved Issues == | == Unresolved Issues == | ||
| − | * How robust is gconf in case of | + | * How robust is gconf in case of (disk) memory shortage or sudden power loss situations? |
== Questions and Answers == | == Questions and Answers == | ||
(None) | (None) | ||
| + | |||
| + | [[Category:Middleware]] | ||
Latest revision as of 09:37, 19 July 2009
Contents |
[edit] Overview
libgconf-bridge is a utility library for binding GObject properties to GConf keys. It is intended to save the application programmer from having to implement property synchronisation manually.
[edit] Use
- We want to save the state of a program and restore it at the next start
[edit] Constraints
(None)
[edit] Architectural Details
- In case an application 'hangs' in a state we want to be able to reset the state of the application.
This can be be done through the context menu in mainmenu.
[edit] Implementation Recommendations
(None)
[edit] Unresolved Issues
- How robust is gconf in case of (disk) memory shortage or sudden power loss situations?
[edit] Questions and Answers
(None)
