+v8-dev
On Tue, Jan 19, 2010 at 2:22 PM, vridosh <vrid...@gmail.com> wrote:
> Hi Peter
>
> Thank you for your response, but probably I was unclear in my
> question. I'm not very interesting in test_shell future - I'm forced
> to use it as a reference implementation simply because for now I have
> no alternatives (except, probably, the whole Chromium code).
>
> What I'm most curious about - is it possible or not to use DevTools JS
> debugger in single-process environment (like WebKit's WebInspector JS
> debugger)? I used to be sure it is not possible at all because of V8
> architecture, but now I see at least some features work. I'm reading
> V8 code now, but may be someone could give me a quick answer whether
> this solution viable or not?
>
> Thanks again for your answer.
>
> Regards,
> Vadim Ridosh
>
> On Jan 19, 2:22 am, Peter Kasting <pkast...@google.com> wrote:
>> On Mon, Jan 18, 2010 at 9:16 AM, vridosh <vrid...@gmail.com> wrote:
>> > As far as I
>> > understand, that's why Debugger tab was not available in test_shell in
>> > early Chromium builds.
>>
>> Probably the real reason is because test_shell isn't meant to be a reference
>> implementation of everything and we never bothered to spend any time on it.
>>
>> So, the main question is - is it possible at all to make DevTools JS
>>
>> > debugger in test_shell to work correctly?
>>
>> AFAIK test_shell is obsolete and is going to die when we implement
>> DumpRenderTree atop the WebKit API. Darin or Dimitri or someone can correct
>> me if I'm wrong.
>>
>> I would definitely not depend on or look at test_shell for any serious
>> project.
>>
>> PK
>
> --
> Chromium Developers mailing list: chromium-dev@googlegroups.com
> View archives, change email options, or unsubscribe:
> http://groups.google.com/group/chromium-dev
>
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
