Le Saturday 02 August 2008 21:23:30 Carsten Haitzler, vous avez écrit : > On Sat, 2 Aug 2008 20:58:05 +0200 (CEST) Vincent Torri > <[EMAIL PROTECTED]> > > babbled: > > On Sun, 3 Aug 2008, Carsten Haitzler (The Rasterman) wrote: > > > On Sat, 2 Aug 2008 13:03:41 +0200 Andreas Volz <[EMAIL PROTECTED]> > > > > > > babbled: > > >> I vote to use LUA for scripting too. I've embedded it into several > > >> commercial products in the past. It was each time a really good > > >> choose. It's easy to understand, small and I think most important has > > >> a really big community. > > > > > > i respect the idea of looking at javascript for example - but it's > > > quite a sring of reports of using lua - in just the way it'd be used in > > > edje that make me go "this looks just like the right thing". the > > > question is ... do we keep embryo? do we keep it and mark it as "here > > > for compatiblity, BUT will be removed in a future release, so please > > > port your scripts to lua. thanks" and then wait a while, and then > > > remove... or ... can we remove now and just cause the pain? how much is > > > embryo really used? > > > > First ask the people who use embryo in their commercial product. Indt, > > Cedric, raoul, Gustavo. And especially, ask the designer who helps raoul > > for calaos. I really think that his opinion is a good one. > > indeed. i am asking! :)
Here is my feedback about Edje. We used a lot of embryo code in the calaos project. Most of the time it is just to set/get some simple vars for more control on "states" of an object. This is ok, works great, and embryo is designed to do that. About the swith to another scripting language, i will just say 2 things. This is ok for me, i will do the conversion in my edj (perhaps i don't have anything to do, because embryo and lua syntax are close). It would not be a lot of work for me. Lua would be a good choice, it's a very small VM, and it will run smoothly on embedded devices. But, I think there are more important issues with edje at this time. Writing edc using macros are a real pain and a waste of time. Macros are hard to write, hard to debug, hard to maintain and unreadable. We need a better way to write generic object (edje script only?). Edje is also missing some more complex objects like lists. For now, any lists have to be done in the C side, it "freezes" a bit the theming capabilities. Having the possibilitie to extend edje by exporting a smart-object (list or any super-cool-smart-object) with its properties and capabilities to edje would be awsome. For example, in the application code, you tell edje to load a LIST smart-object with some properties, and then edje can use it like a standard parts in the edc. In the part definition, you can change the properties of the LIST, like enable/disable kinetic scrolling, horizontal/vertical scrolling, ... Such a feature could really help designers to be more productive in writing edc, and give them much more power. As I said, for now writing edc is a painfull task. -- Raoul Hecky Calaos ------------------------------------------------------------------------- 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
