---------- Forwarded message ---------- From: John Kha <[EMAIL PROTECTED]> Date: Wed, Sep 24, 2008 at 17:54 Subject: Re: [E-devel] Module Type freedom. To: The Rasterman Carsten Haitzler <[EMAIL PROTECTED]>
I am working on some things that will do this, and allow easier extensions to the module configuration interface, like i said (its slow going, i've been busy with work, but its coming along. I have a basic API setup, and the code that will find and return an index of modules by type (determined by the category string) pretty much done. I still need to write the code that calls the extended module configuration interface that can be put in a module, rework the existing module configuration code to work with that, and write a fallback interface that exposes as much power as possible, but is not as user friendly. This fall back should work on any screen size, give details such as module paths, etc, and allow for loading/unloading and enabling/disabling as separate actions. i'll submit a patch when i'm done, hopefully by the end of october (sooner, if i can find time, but no guarantees) On Fri, Sep 19, 2008 at 21:30, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote: > On Fri, 5 Sep 2008 13:24:08 -0400 "John Kha" <[EMAIL PROTECTED]> babbled: > > you're right. as such the current system doesn't allow much extension of > types. > we should use the category string and build the list of types dynamically. > >> Working on the module code, I was noticing that currently there are >> five defined types for modules. There might be some reasons to allow >> for more freedom of choice in these types. For instance, if one was >> writing a specific set of modules that works with illume, it might be >> nice to put them in an Illume category. On the other hand, module >> writers might get out of hand and invent too many categories, which >> could get confusing. But since we aim to give as much power of >> configuration as possible, i think the former would be preferable, and >> we could have a "suggested" set of categories to use for certain >> things. As it is, the current Module type system puts a large number >> of modules in any given type, making the system less useful for >> finding what module one might be looking for. >> >> Also, the current default type is "shelf" which is a little silly. I >> suggest using "Miscellaneous" or something like that. >> >> I will be able to work on the code to change over to the >> module.desktop defining the type, if people think that is the way to >> go. >> -- >> John C. Kha >> United States Navy >> >> ------------------------------------------------------------------------- >> 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 >> > > > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] > > -- John C. Kha United States Navy -- John C. Kha United States Navy ------------------------------------------------------------------------- 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
