wow

[Andre Garzia]

Guys,

I think this will never happen and I can explain why:

1 - There are hundreds of other Free Open Source languages in the terms of
the GPL and they were not included in WebKit.
2 - LiveCode has a single vendor. Its not a standard. It has no other
implementation.
3 - LiveCode stacks are binary and the web is moving away from binary apps
to js based apps even though NaCL exists on Chrome.

Having a stack available with a protocol such as stack:// can be done today
on all systems. You just register your application as the handler for the
given protocol and then it just works.

I have mine set so that x-livecode-stack:// opens in the IDE (or at least I
had it in snow leopard, I don't think this change came thru in Lion)

WebKit is not a unified thing. There is more than one WebKit out there,
many ways to build it, many different javascript engines and build systems.
The project will not incorportate a new scripting engine that is not backed
by multiple vendors and is not a standard.

If you want to see LiveCode stacks in a browser, join the open source
effort for HTML5 deployment it can be done quick and dirty with emscripten
or at a more elegant and useful level soon thru asm.js and others.

Cheers
andre

On Tue, Feb 26, 2013 at 9:03 PM, Monte Goulding <monte at sweattechnologies.com
> wrote:

> Yes it's a huge idea. I'm not sure about the licensing implications for
> WebKit. It's currently LGPL so could potentially be integrated in closed
> source apps. Adding LC source would force it to be GPL I think so WebKit
> might need to be forked for this. The idea definitely highlights what
> becomes possible once it's open source.
>
> On 27/02/2013, at 10:07 AM, Malte Brill wrote:
>
> > @Larry Tesler. Hi Larry --Carl from the "original" Apple Cocoa project
> here :)...glad to hear you are contributing here as well.
> > @Everyone, just wanted to seed the idea that LC could, in theory, now be
> integrated into WebToolkit under the GPL license. Perhaps right next to
> /trunk/Source/JavaScriptCore:) One idea is to use a different protocol,
> like stack:// that could then launch stacks available on the Internet.
> Parameters can still be passed using similar URI and
> GET/POST/PUT/DELETE/CONNECT/... methods.
>
> --
> M E R Goulding
> Software development services
> Bespoke application development for vertical markets
>
> mergExt - There's an external for that!
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 
http://www.andregarzia.com -- All We Do Is Code.
http://fon.nu -- minimalist url shortening service.