On Mon, 3 Nov 2008 14:39:05 +0100 (CET) Dave Andreoli <[EMAIL PROTECTED]> babbled:
> > 1. config everyone cal look at > > OR > > 2. "opening service". e.g. a dbus call- u send an array (list) of file > > paths > > and say "open them please" - e will open them for you. this way you > > also > > recycle the exec method and child process tracking etc. if the target > > file is a > > directory - it opens a directory window, etc. > > > > is #2 perhaps not better? > > The #2 is powerfull but will work only if E is running, and this is bad > for applications, that should work also outside E. > > I prefer the #1, put the config where everyone can look...what about > the defaults.list file ? ;) (it's not yet a fdo standard, but it's a > simple and clear way to store the info) technically - any app/desktop/wm could provide the same dbus service... a stand-alone app could too. the problem with #1 is that if e decides to change config, format, versioning, keys, break it etc. every app is stuck catching up. putting it into a lib and formalising it sets the config in stone as u cant go change it as u are going to break format/api. a very limited config is possible, but i think it's a bit premature to go formalising this - for e it is i think. also this means the config now can't use e's normal config schemes. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
