Hi, I'm going to be attempting to write a new backend for e_dbus to use the new udisks/upower framework which is succeeding hal. Some questions I've been mulling over while I've been doing it:
Should I be migrating all the hal/udev calls to some kind of e_dbus_* call system so that it will be transparent to developers regardless of the backend being used? The idea here being that only one backend can be enabled at compile time (since no sane person would have both hal AND udisks/upower running simultaneously), thus saving code migration in the future should another hw backend be created. What should the new module be called? Since the old one is e-hal, I figured I'd call the new one e-udev, though I'm open to whatever. Should udisks and upower functionality be integrated into the same module? I'm thinking yes, though if there's a reason why they should remain separate then that's fine too. I'm assuming that we want all the same calls that the hal module currently provides. Is there any additional functionality that we need/want? I'd link the udisks/upower api, but it doesn't really exist outside of the code; I can say that they can do pretty much everything you'd imagine them to do if that helps :) Also, does anyone know a better dbus debugger/utility? So far I've been using a combination of d-feet, qdbus, and dbus-monitor/send to do stuff but I actually need to use all of them to get the functionality I want. If anyone has any comments/questions I'll be around in #edevelop and checking here regularly. -Mike (discomfitor/zmike) ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
