hal/doc TODO,1.41,1.42

[David Zeuthen]

Update of /cvs/hal/hal/doc
In directory gabe:/tmp/cvs-serv30228/doc

Modified Files:
	TODO 
Log Message:
2005-03-15  David Zeuthen  <david at fubar.dk>

	* doc/TODO (CVSID): Add a few items



Index: TODO
===================================================================
RCS file: /cvs/hal/hal/doc/TODO,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -d -r1.41 -r1.42
--- TODO	7 Mar 2005 19:38:09 -0000	1.41
+++ TODO	15 Mar 2005 21:10:06 -0000	1.42
@@ -8,9 +8,9 @@
 
 Ongoing items that always need work
 -----------------------------------
- - valgrind once in a while to fix memory leaks / memory corruption
+ - Valgrind once in a while to fix memory leaks / memory corruption
 
- - keeping the spec in sync with the code
+ - Keeping the spec in sync with the code
 
  - Extend test suite coverage
 
@@ -28,6 +28,9 @@
 
  - Fix storage policy properties now that we have string lists
 
+ - Make the helpers (probers, addons) use a direct connection to hald
+   instead of routing it through the system message bus
+
 Medium items
 ------------
 
@@ -44,6 +47,11 @@
  - Finish volume_id so it's safe to use on IDE drives; e.g. make it detect
    various IDE RAID signatures
 
+ - Port server code to new glib/gobject D-BUS bindings when they're cooked
+   and ready
+   - We get introspection for free
+   - GNOME projects etc. would use D-BUS glib bindings instead of libhal
+
  - Method invocations - have some way to specify that that a hal device
    object exports the org.freedesktop.Hal.Device.Foo.Bar interface -
    suggest to use a property info.interfaces (strlist) with what interfaces
@@ -55,6 +63,8 @@
    say libhal_device_property_set_persistent (udi, "some.property.name") -
    should be a privileged operation
 
+ - Persistent device objects
+
  - Move all privilege checking to D-BUS configuration files - the one shipped
    with hal wouldn't allow much but distributors are free to change this as
    the like (for Fedora we would rely on SELinux probably, Debian would perhaps