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 :)
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
