On Sat, 2 Aug 2008 08:25:17 +0800 Toma <[EMAIL PROTECTED]> babbled:
seems there's a few votes for keep of embryo. i'm going to just monitor the
sentiment here - i'm agnostic really - though edje needs a LOT better
"scripting" support. yes JS might be an option - python imho is just away too
big and heavy. existing efl bindings are not really useful as edje will have to
wrap and hide most things - ie you set up a timer - edje needs to know so it
can delete the timer on edje object deletion. just an example. so it's pretty
much a level playing field based on:
1. efficiency of the language - the leaner/faster, the better
2. actual language ease of use/documentation/facilities. etc.
3. aptness of the language engine to embedding as a slave to a library for
doing code logic (ie be able to function fully sandboxed without any
features/calls and all calls are explicitly exported from edje).
lua right now seems to be probably the candidate i've seen. embryo is a close
second (used to be better than lua).
> 2008/8/2 Nick Hughart <[EMAIL PROTECTED]>:
> > Carsten Haitzler (The Rasterman) wrote:
> >> On Fri, 1 Aug 2008 17:23:41 -0300 "Gustavo Sverzut Barbieri"
> >> <[EMAIL PROTECTED]> babbled:
> >>
> >>
> >>> On Fri, Aug 1, 2008 at 5:21 PM, Nick Hughart <[EMAIL PROTECTED]> wrote:
> >>>
> >>>> Toma wrote:
> >>>>
> >>>>> Does embryo have any use without edje? If not, why not wait till edje
> >>>>> is ready for release and send them out together?
> >>>>> Toma
> >>>>>
> >>>>>
> >>>> Yes it does, it just isn't really used outside of edje at this point.
> >>>>
> >>> It's another package, so it's not tied in any way. We need to do
> >>> releases and a good start and training is with these libs. When things
> >>> go to Evas, Ecore and Edje, things will get much more complicated and
> >>> lots of different interests and pov will raise.
> >>>
> >>
> >> as per my other email... i want to look at lua for edje... right now if we
> >> want to KEEP embryo support in edje - then am embryo release makes sense.
> >> if we don't - it makes no sense. so i'd like to know.. how important would
> >> keeping embryo be... *IF* we were to also add and much more heavily
> >> support lua? (or for that matter any other scripting engine?)?
> >>
>
> I can only really think of a couple things needed, and thats moving
> parts up and down. Sure you can duplicate bits and have them appear
> and what not, but if you could EASYILY move an object up and down in
> the code then that would help tremendously. That said, it would
> probably be an option in the programs{} of edje and perhaps some basic
> support for that in embryo would suffice, but as others are saying,
> might be a good idea to delay that to a 'embryo/edje 2.0' kind of
> release.
> Another thing people are often inquiring about is creating whole parts
> on the fly with embryo. I think thats more of a misconception of
> embryo and edje together, since embryo is used to control edje parts,
> not create edje parts (at least thats how I understand it)...
>
> So my 2c goes in the 'Keep Embryo as it is' jar.
>
> Toma
>
> > Well this is the only issue afaik stopping embryo from going out. Do
> > you want the community to vote on this or are you going to make the
> > decision? If it's up for vote then I'd vote to ship it as is since
> > embryo seems powerful enough for simple theme animations and that's what
> > edje is being marketed as at this point. With the next release of edje
> > if we want the more powerful scripting and extra bindings to make it
> > more like flash/silverlight/etc then it will definitely be seen as
> > worthy of another major release and I'm sure people wouldn't mind the
> > break all that much. I think there would be enough time between the
> > release of this iteration and the next that we could let developers know
> > that the switch is coming and they could prepare. I think lua would fit
> > better with the more flash like edje then with the current version
> > anyway so I vote to kick it out the door so we can get started on the
> > transformation. Maybe the limitations of the current edje will bring in
> > devs to help with this as well, who knows :) (I realize this is not a
> > smoking gun so don't go crazy on me.)
> >
> > That's just my 2c.
> >>
> >>
> >
> >
> > -------------------------------------------------------------------------
> > 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
> >
>
> -------------------------------------------------------------------------
> 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
>
--
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) [EMAIL PROTECTED]
-------------------------------------------------------------------------
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
