Carsten wrote:
> On Mon, 4 Aug 2008 10:50:10 +0200 "Cedric BAIL" <[EMAIL PROTECTED]> babbled:
>
>
>> On Mon, Aug 4, 2008 at 2:25 AM, The Rasterman Carsten Haitzler
>> <[EMAIL PROTECTED]> wrote:
>>
>>> On Mon, 04 Aug 2008 02:43:33 +0300 Viktor Kojouharov <[EMAIL PROTECTED]>
>>> babbled:
>>>
>>>> Rhino is java based, so that's out. Then we have SpiderMonkey, which is
>>>> currently used by gecko1.9. That's not as fast as webkit's engine. Then
>>>> there's tamarin, which is practically future proof, with its support for
>>>> ES4. However, it's not complete. I don't know of any other engines out
>>>> there.
>>>>
>>> hmmm wel then it spidermonkey or... nothing. and spidermonkey is pretty
>>> fat... it's api is pretty big... :/ quick look.. not smelling positive. :(
>>>
>> I am playing with spidermonkey since some time now and trust me you
>> want to use lua for edje. It's smaller, easier to integrate and fit
>> the need of edje. It's perhaps not a good solution for big apps, but
>> for small script it should be perfect. And in my opinion, it's a
>> matter of a few days to switch to lua in edje and we should do it
>> sooner than latter. I would really like to see this before the end of
>> august and looking at edje, sounds like a really straight forward
>> jobs.
>>
>
> man.. thank you! a man who has actually played with spidermonkey and js.. and
> real advice from the trenches! thanks muchly! confirms my thoughts that lua is
> a much better fit. i was thinking of getting lua in by end of august... i need
> to play with it first... the question is.. embryo - keep for compatibility
> (after the lua change) or throw out? i would keep it anyway while adding
> lua...
> but then.. remove or not? i am listening to those using embryo right now.
>
>
Design your stuff to be extensible, within reason and if there's reason
for it. You don't know what the future can bring, don't limit your design from
the start.. all that everyone here has done and has experience with is a drop
in an ocean.
You didn't want loadable engines for evas at first (original evas), then
you did and Jorge rewrote a large amount of stuff.. now you want loadable objs
as well - there was always good reason for these. You chose embryo first for
edje, now you want to change it to another - there was always good reason for
that.
Pick one, say LUA, and support that in the 'official' tree, drop embryo
if desired, but write the thing to allow for extensibility to support others.
If later in time someone(s), for some reason writes a js or whatnot one, and
it takes off and is used in ways none here expected then so much the better -
let the 'market' decide, don't limit things from the start.
____________________________________________________________
Click to go wireless with your computer, ultra fast speed.
http://thirdpartyoffers.juno.com/TGL2141/fc/Ioyw6i3nBfhe2oRb8nSGG6eFQLqhypeDGbalpXVZ3PrzHrhNPL2rXe/
-------------------------------------------------------------------------
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
