I would say this about covers most of the necessary information.
data {
item: "e/theme/name" "BlingBling";
item: "e/theme/version" "16.999.043";
item: "e/theme/license" "3-Clause BSD";
item: "e/theme/author" "Carsten Rasterman Haitzler & the E17 Team";
}
The 'about' block in the About_Theme could simply state all these
things again or just totally leave out the 'about' textblock all
together.
Im wondering if 'item: "theme/usage" "e17"' would be useful aswell, as
its difficult to tell by simply looking at an edje what the file is
meant to theme, unless the author has made it bleeding obvious.
Toma
2008/6/30 Toma <[EMAIL PROTECTED]>:
> Hmm good call. There are a few more levels you could take aswell, eg.
> License, Author... its just a matter of whats really needed. But
> thanks for edje and eet, its all details that can be stored in the
> files, and we should really take advantage of that.
> Toma
>
> 2008/6/30 Nick Hughart <[EMAIL PROTECTED]>:
>> I'd even go a bit further and possibly add something like a minimum E
>> version required for the theme. There may even be other details that could
>> be useful. Question is, will anyone else think it's a good idea :)
>
> Hmm good call. There are a few more levels you could take aswell, eg.
> License, Author... its just a matter of whats really needed. But
> thanks for edje and eet, its all details that can be stored in the
> files, and we should really take advantage of that.
> Toma
>
>>
>> Toma wrote:
>>>
>>> Hey all!
>>> I think it would be really great to have a theme name and version
>>> locked in an edj for purpose of identification. Until now the theme
>>> name and version is stored in the filename which is a very flakey and
>>> sometimes misleading way to store this. I think it would be a good
>>> idea to start using what EWL does but extend it slightly and include
>>> the themes Name and Version in the actual edje data{} itself. Heres an
>>> example.
>>>
>>> data {
>>> item: "e/theme/name" "ThemeName";
>>> item: "e/theme/version" "2.0";
>>> }
>>> collections{}
>>>
>>> That way the themes details can be parsed and possibly implemented
>>> into the E theme selector itself. What should be discussed is the
>>> naming. Is "e/theme/name" ok? I know in ewl its "/theme/name" but Im
>>> not sure if that could/should be carried over to E.
>>>
>>> -------------------------------------------------------------------------
>>> Check out the new SourceForge.net Marketplace.
>>> It's the best place to buy or sell services for
>>> just about anything Open Source.
>>> http://sourceforge.net/services/buy/index.php
>>> _______________________________________________
>>> enlightenment-devel mailing list
>>> enlightenment-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
>>>
>>
>>
>
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
