On Sun, 5 Aug 2007 00:15:59 -0500 Brian Mattern <[EMAIL PROTECTED]>
babbled:
> I gave this a quick read-through. Haven't had time yet to update
> everything, so I can't apply it yet.
>
> A few quick thoughts on the API.
> I'd prefer to see a more object oriented API.
>
> I.e. rather than having a single 'RemoteObject' that all calls go
> through, have something like:
>
> /org/enlightenment/wm
> org.enlightenment.wm.Core
> Restart()
> Exit()
> ListModules(OUT as)
>
> org.enlightenment.wm.System
> Suspend()
> Hibernate()
> Reboot()
> Shutdown()
> Logout()
> LockScreen()
>
> org.enlightenment.wm.Config
> Set(IN s, IN v)
> Get(IN s, OUT v)
> GetMultiple(IN as, OUT a{sv})
>
>
> /org/enlightenment/wm/module/<module_name>
> org.enlightenment.wm.Module
> Load()
> Unload()
> Enable()
> Disable()
>
> org.enlightenment.wm.Config
>
>
> The names are still debatable, but I prefer having the modules as
> separate objects on the bus. E could just create these for all available
> modules, and provide a means for a module to fetch its bus object
> (allowing it to register additional interfaces if desired).
>
> Additionally, we may want to look into some of the existing specs for
> things like power management, and if feasible, implement at least a
> subset of them.
hmm - actually we more likely need to look into adding dbus power management
support to the battery module (other way around).
or are you getting at other api's eg - like "please go into low power mode"
kind of api calls where e may drop its framerate or something to save power?
> For config, i'm not sure how easily we can map dbus types to config
> value types (or lookup values by property name). So, we may end up
> needing individual get/set methods for each property (as the current ipc
> is done).
>
> Anyway, thanks for the initiative here.
>
> Anyone else have ideas on how they'd like a dbus API for e to look?
personally- for now. minimal and simple. lets try keep as much config out of it
and lets solidify a small base of calls and features - and only implement what
we ABSOLUTELY MUST/SHOULD. people can add modules later to extend and add dbus
config twiddling at will- but for us in core, lets try keep the work down? :)
> Brian
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
>
--
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) [EMAIL PROTECTED]
裸好多
Tokyo, Japan (東京 日本)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
