From: Carsten H. (T. R. <ra...@ra...> - 2008-11-29 23:58:27
|
On Sat, 29 Nov 2008 20:45:01 -0200 "Gustavo Sverzut Barbieri" <bar...@pr...> babbled: > On Sat, Nov 29, 2008 at 8:34 PM, Leandro Santiago > <lea...@gm...> wrote: > > Hello E-guys. > > > > I do not know if it would be feasible at the moment, but I think it > > would be interesting if it were implemented "projects" support in > > edje_editor. > > > > Currently the edje_editor handles files directly edje, but I think it > > would be interesting if the "final product" was the source code files > > (.edc, pictures and files from sources) and not a binary file. > > > > Then the user manually compiled the project using the edje_cc, which > > reduces problems of incompatibility, as it is currently impossible to > > re-edit a file edje created by edje_editor. > > > > I know that today is not priority, but an editor of effective interfaces > > would be very interesting to move closer to enlightenment with new users > > willing to contribute with themes and more. > > Edje files should be decompile-able with edje_decc and AFAIK > edje_editor was fixed to generate every bit required to this work, if > not this is the way to go. also as long as you dont use lossy compression - images will suffer no quality loss when in a .edj - you can produce a "project .edj" where you dont allow lossy compression (but mark images so that later you do want to lossily compress them in a "product .edj")). so as such .edj is a sufficiently good format for all of it :) (you can add all sorts of data to a .edj you want that edje itself might not use - only edje_editor)). and thus you can have a "project" that is already directly usable. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ra...@ra... |