On Friday, 25 July 2008, at 01:10:45 (+1000), Carsten Haitzler wrote: > > 3. This whole mess is a very bad idea. Handling versioned > > dependencies is a much, much harder problem than you realize. And > > restricting what applications are allowed to peek at a theme's > > bits is silly. Just make the bits available to whatever > > application wants to use them, and don't try to reinvent > > dependencies. > > true - re-inventing is bad... BUT then how will you download a theme > and plonk it in ~/.e/etk/themes or whatever - and know if it works > or not?
You don't. Even *with* version numbers, there are no guarantees of compatibility. All the version numbers are is a statement by the author, made at an unknown point of time in the past, that his/her intent was to target this theme at version X.Y.Z of lib/app Foo. In order to do it right, there needs to be a numbered "API" for the theme engine that themes can be written to and claim to match. The theme engine must then say it supports between version A and version B of that API. Kind of like shared library versioning, only without the confusing numbering scheme. > you would require every theme to be packaged! :) not sure that's > really viable... :) Agreed. :-) Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <[EMAIL PROTECTED]> Linux Server/Cluster Admin, LBL.gov Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "Sometimes I give myself the creeps. Sometimes my mind plays tricks on me. It all keeps adding up; I think I'm cracking up. Am I just paranoid? Am I just stoned?" -- Green Day, "Basket Case" ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
