For the many benefits of EDJE. I think a major downfall is having to rebuild a theme per every EFL update. Something seems very wrong with that approach.
If one does not have to per se rebuild an EFL app per EFL release. Why should one have to rebuild a theme? If an app is using say standard stuff, that is not likely to change. Then rebuilding an app against newer would provide little if any benefit or difference. Design wise I thought themes were separate from code so seems really bad that themes must be rebuilt per every EFL release. That adds an entirely new level of complexity to theming. Which IMHO is already pretty complex. Things I can do easily in say gtk, qt, or others, like changing base colors of things. Takes considerable time using EDJE. This is not meant as an insult. But more request for consideration to make some things easier to modify. Example This gtkrc file is all I need to modify gtk theme colors to match my eminence theme colors. Inheriting another theme https://github.com/Obsidian-StudiosInc/eminence/blob/master/src/gtkrc-2.0 Doing the same with EDJE is very complex. One must rebuild the default theme and/or make one of their own. Both I have done and am doing presently with eminence. More importantly, I will vary rarely if ever have to touch that gtkrc file again. I surely will not have to do anything with any theme for a gtk update. Also has legacy compliance. That gtkrc-2.0 file works for 3.0 stuff with no additional modifications. -- William L. Thomson Jr.
pgps1haKMYiIr.pgp
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
