Matthew --- this is really interesting work. Where can I have a look at your Spidermonkey stuff? Think its a very compelling route.
On Wed, Oct 26, 2011 at 9:53 AM, Matthew Schulkind <[email protected]> wrote: > I've now run just about all of my code (including phonegap) under V8 (using > chrome for the developer tools), WebKit, and now SpiderMonkey with no > changes other than adding the missing bits where appropriate (like > setTimeout/Interval and XHR for SpiderMonkey). > > What problems would you think would exist? > > On Wed, Oct 26, 2011 at 12:46 PM, Matt Kane <[email protected]> wrote: > >> I meant in general, rather than specific to the ObjC<->JS bridge. >> >> On 26 Oct 2011, at 17:36, Matthew Schulkind wrote: >> >> > I was using only UIWebView and had the previously mentioned problems. Now >> I >> > ripped out UIWebView completely and I'm only using SpiderMonkey and >> having >> > none of the previously mentioned problems. >> > >> > On Wed, Oct 26, 2011 at 4:14 AM, Matt Kane <[email protected]> wrote: >> > >> >> You're using Webkit + Spidermonkey? Isn't that just asking for massive >> >> compatibility headaches? >> >> >> >> On 25 Oct 2011, at 23:29, Matthew Schulkind wrote: >> >> >> >>> I have had tons of problems with UIWebView in general, so much so that >> >> I've >> >>> just about finished abandoning it. I've been working on a set of native >> >> UI >> >>> components for Callback (that sounds weird...), so I luckily don't need >> >> the >> >>> HTML display of UIWebView, so I'm currently 90% of the way to >> integrating >> >>> SpiderMonkey with phonegap, which totally gets rid of any exec() type >> >>> problems because you get to use a real ObjC<->Javascript interface. >> >> >> >> >> >> >
