On Mon, Aug 23, 2010 at 9:25 AM, Tom Haste <[email protected]> wrote: > Exchange content is now basically outdated due to the edje changes. > Also, gradient has been knocked out, so that changes a lot of things. > Im going to run edje_convert on all the site contents, to bring all > that up to the recent API. Im guessing this will cause a wave of > problems with people using packages and old versions (which we dont > support). My question: Is it a good time to do this? If it is, ill put > out an announce on the mailing list and a disclaimer on the landing > page (if I can figure that out)
edje_convert preserve the edje data needed for old edje loader. So when you call edje_convert on an old edj file, it basically make it loadable with both old and new loader code. It should not impact old user at all (it doesn't remove gradient part in old format). Thing should be just fine for your use case as this is the intended usage. > Also, due to gradient being removed, Im planning on disapproving all > content that has a gradient in it. Maybe not now, but eventually once > the gradients have been completely removed. So if you have content on > there, please update it if it has a gradient. gradient has been completely removed from edje and evas code. Did I miss some ? Where ? Where ? Will kill that one too ! :-) -- Cedric BAIL ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
