On Tue, Feb 17, 2009 at 10:15 AM, Erik Kay <[email protected]> wrote:
> On Tue, Feb 17, 2009 at 8:06 AM, Marc-Antoine Ruel <[email protected]> > wrote: > > I guess it's not doable ATM anyway but does the debugger really needs > > to run in the browser? > > I think the debugger's dependency is already gone (or very close to > it). It's still used in the telnet interface, but nobody's really > using that at the moment. If it really causes a problem being there, > then I'd say to go ahead and remove it. However, if it's not causing > problems, then I'd say that it should be left in. We've got some long > standing ideas for how to use this to simplify browser automation, > specifically for testing, but perhaps for user scripting as well. > Nothing active is happening on this front though. > > Erik > I agree... also, I believe the folks working on the dev tools intend to preserve the telnet interface to the debugger. They want to use it as a means to enable an Eclipse plugin that is being developed. That probably doesn't require V8 in the browser though. I really like the idea of exposing V8 in the browser for automation. What are the reasons to not like V8 in the browser? -Darin --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
