diff options
author | Brian Tarricone <brian@tarricone.org> | 2007-10-04 18:58:53 +0000 |
---|---|---|
committer | Brian Tarricone <brian@tarricone.org> | 2007-10-04 18:58:53 +0000 |
commit | a8af11993145074bfa579f39efa357da3dcb9e2f (patch) | |
tree | dbceb96fa7624fd51cbc1b9fbc9c3c08edd3b074 | |
parent | d4c6e594200fea84e7bde4b903e9bc79b923fa2c (diff) | |
download | xfconf-a8af11993145074bfa579f39efa357da3dcb9e2f.tar.gz |
update todo, spearate items into '1.0' items and 'future' items
(Old svn revision: 26764)
-rw-r--r-- | TODO | 24 |
1 files changed, 19 insertions, 5 deletions
@@ -1,11 +1,25 @@ +-> for version 1.0 + * add kiosk/locking mechanism (mostly done) * XfconfBackend needs to do validation on channel and property names -* transaction support (?) -* unit tests +* unit tests (mostly done) * MCS settings migration code -* figure out how to let libxfconf know about the XfconfBackendError enum -- - maybe just rename to XfconfError and move to common/ + - special backend to read config entries + - script/c code for users who want to migrate all their settings to + xfconf and ditch MCS entirely * expire channels from memory if they aren't accessed for a while * add a GetAllChannels() method to enable a gconf-editor type app - +* implement the PropertyChanged signal + - should fire whenever SetProperty() is called and a value is set. + + optimise by checking previous value; don't fire signal if the value + hasn't really changed. will this slow down the daemon too much? + - file system monitoring. if a backend file changes, the daemon needs to + re-read the file, but must save the old property tree so it can figure out + what has changed so it can send appropriate PropertyChanged signals * separate XSETTINGS daemon that reads values from xfconfd + + +-> for future: + +* transaction support +* network support - allow remote displays and such |