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 PROTECTE
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
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
Hey,
I am planning to reorganize the header files of evas, which is a big fat
mess. Then I remembered a discussion on the ML about data types in evas
and ecore, and their respective performance.
So I'm wondering if, before reorganising the header files, it would be a
good idea to extract fr
Build log for Enlightenment DR 0.17 on 2008-06-29 07:10:21 -0700
Build logs are available at http://download.enlightenment.org/tests/logs
Packages that failed to build:
edvi http://download.enlightenment.org/tests/logs/edvi.log
enna http://download.enlightenment.org/tests/logs/enna.log
epdf htt