On 12/17/05, Brian Mattern <[EMAIL PROTECTED]> wrote:
With the moon module I used the EAPI function "e_module_dir_get" to find where the module was loaded from. This location (or subdir) might be a good candidate?
Something else I was wondering about was whether there is a benefit of having a convention with regards to the category used by module writers. It might aid theme writers in keeping their edc's organized and tidy, in the case they override the default module theme. IIRC I am using "main/moon" right now, but I'm thinking of changing it to something like "modules/moon".
Regards!
David
On Friday 16 December 2005 09:57, Essien Ita Essien wrote:
> About E_Gadget, have you added support for being able to load a theme from
> a name edje file yet? If not, I could send in a patch to do that... my
> current tree (checked out on Tuesday), only has support for applying a
> theme from e's default theme.
I don't think we want the module itself naming the theme it wants. It should
simply name the category / group it wants, and let e's theme system find the
correct file. For this to work, we _do_ need to specify where the default
theme should go. So, if the file currently assigned to the given category
(the current theme -- unless you've changed it with enlightenment_remote /
the non-existant themes dialog) doesn't include the theme, look for it in
~/.e/e/themes/modules/module_name.edj and
then /prefix/share/enlightenment/themes/modules/module_name.edj.
With the moon module I used the EAPI function "e_module_dir_get" to find where the module was loaded from. This location (or subdir) might be a good candidate?
Something else I was wondering about was whether there is a benefit of having a convention with regards to the category used by module writers. It might aid theme writers in keeping their edc's organized and tidy, in the case they override the default module theme. IIRC I am using "main/moon" right now, but I'm thinking of changing it to something like "modules/moon".
Regards!
David
