Re: [webkit-dev] JavaScriptCore Debugger - Non-Browser

2012-02-14 Thread Sergiy Temnikov
Hi,

could you please elaborate a bit more on this? Are there any definite plans and 
timelines already defined? What is the new direction for the JS debugger 
evolution?
Thanks in advance,

-Sergiy Temnikov
Wakanda Server architect


Message: 5
Date: Mon, 13 Feb 2012 11:46:10 -0800
From: Oliver Hunt oli...@apple.com
To: Maciej Stachowiak m...@apple.com
Cc: WebKit Development webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] JavaScriptCore Debugger - Non-Browser
Implementation
Message-ID: d67ef71c-9f30-4cc3-b9fd-a8c95391f...@apple.com
Content-Type: text/plain; CHARSET=US-ASCII

We actually want to kill the current debugging mechanisms as they're somewhat 
archaic in their current form (they require substantial [and fragile] work on 
the debugger side, and have a significant runtime cost).  I'd be hesistant to 
start building anything new on top of what's currently there, but we do want to 
improve the dev support in JSC itself so we wouldn't say no to any patches in 
that direction.

--Oliver





Sergiy Temnikov
Architecte Logiciel

4D SAS
60, rue d'Alsace
92110 Clichy
France

Standard : +33 1 40 87 92 00
Email :sergiy.temni...@4d.com
Web :  www.4D.com


___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


Re: [webkit-dev] JavaScriptCore Debugger - Non-Browser Implementation

2012-02-14 Thread Sergiy Temnikov
Hi,

 The APIs exist, so it should be possible to make one, but no one has done so 
 at this time, so far as I know.

We did implement a remote debugger in JSC in Wakanda Server. It will be 
open-sourced very soon.
For a quick demo please take a look at this video:
http://www.wakanda.org/blog?page=2

-Sergiy Temnikov
Wakanda Server architect



Message: 4
Date: Mon, 13 Feb 2012 11:39:52 -0800
From: Maciej Stachowiak m...@apple.com
To: Matt Veenstra matts_li...@tribalmedia.com
Cc: WebKit Development webkit-dev@lists.webkit.org
Subject: Re: [webkit-dev] JavaScriptCore Debugger - Non-Browser
Implementation
Message-ID: f2261cff-e25e-41cd-8f71-c001c4db6...@apple.com
Content-Type: text/plain; CHARSET=US-ASCII


On Feb 7, 2012, at 10:18 PM, Matt Veenstra wrote:

 Hello,

 I am looking for a tool to help debug JavaScript code for
 JavaScriptCore when NOT using a browser?  I did a bit of research and
 did not find anything that seems to attach and debug at a code level
 and ignore the DOM.

 Is there something simple I missed?  Drosera seemed to exist in the past.

 Is this the proper list for this question?

I don't believe there is a pre-made tool for debugging JavaScript code in JSC 
outside of WebKit. The APIs exist, so it should be possible to make one, but no 
one has done so at this time, so far as I know.

Regards,
Maciej




Sergiy Temnikov
Architecte Logiciel

4D SAS
60, rue d'Alsace
92110 Clichy
France

Standard : +33 1 40 87 92 00
Email :sergiy.temni...@4d.com
Web :  www.4D.com


___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


Re: [webkit-dev] Remote debugger

2011-02-22 Thread Sergiy Temnikov
OK, cool! Thanks a lot. Nice to see a functioning browser to browser debugging. 
Do you know if the Web Inspector protocol specification is stable and finalized 
now?
Thanks!

-Sergiy


De : Joseph Pecoraro [mailto:pecor...@apple.com]
Envoyé : vendredi 18 février 2011 19:31
À : Sergiy Temnikov
Cc : webkit-dev@lists.webkit.org; Pavel Feldman; loi...@chromium.org; 
pmue...@yahoo.com
Objet : Re: [webkit-dev] Remote debugger

Hello Sergiy,

I've got a bunch of links for different areas where work has been done.

Some information on the protocol and is outlined in the following links. I 
don't think they are up to date; I think things have improved and evolved since 
then. Pavel and Ilya may be able to comment more on the protocol since there 
has been quite a bit of work recently splitting it up into different domains to 
turn on/off debugging different domains or feature sets. But I think the 
protocol has been stable for a while. I think they even had some discussion 
with the Firebug team when they talked about a debugging protocol, but I can't 
seem to find where that discussion took place.
http://webkit.org/b/43732 Web Inspector: Remote debugging meta-bug
https://docs.google.com/document/edit?id=1d_N-OIb3UztuC-_g0piXsIIdp89HnMcDk-uSQ8uamW4hl=enauthkey=CIf48O4Jpli=1#https://docs.google.com/document/edit?id=1d_N-OIb3UztuC-_g0piXsIIdp89HnMcDk-uSQ8uamW4hl=enauthkey=CIf48O4Jpli=1

Here is a screencast, previously posted to this list, of it working in Chromium:
https://lists.webkit.org/pipermail/webkit-dev/2010-August/013797.html
http://screencast.com/t/YTI2OTY4YTEt

There has been some work on an internal WebKit solution based on Web Sockets:
http://webkit.org/b/43988 Web Inspector: Remote Web Inspector support for 
QtWebKit [Already Landed]
http://webkit.org/b/51364 Web Inspector: Remote Web Inspector - Cross 
Platform InspectorServer [Open - Issues to be Worked Out]

External to WebKit, Patrick Mueller has been working on weinre. Patrick is on 
this list and might comment more:
http://pmuellr.github.com/weinre/index.html (https://github.com/pmuellr/weinre)
http://muellerware.org/papers/weinre/manual.html

- Joe

On Feb 18, 2011, at 7:04 AM, Sergiy Temnikov wrote:



Hello,

I'm working on a remote JavaScript debugger for a server which uses webkit to 
execute JavaScript code. The debugger is shaping up nicely and is already very 
much functional. We chose Crossfire as the debugging protocol and developed our 
own UI debugger client. However, being Crossfire-compatible, should allow us in 
the (hopefully near) future to debug the server-side JavaScript using Firefox 
with Firebug and Crossfire plug-ins. I was wondering if there are any plans in 
the webkit community to create a native remote JavaScript debugger as part of 
the webkit build. If there are such plans then what would be the debugging 
protocol of choice? Webkit is already available on mobile devices but because 
of the screen size limitations it is not always reasonable to debug the 
Javascript directly on a device. Instead, it would be nice to debug the 
device's  JavaScript from a regular PC over the network.
If any of you are already working on a similar subject then please share your 
thoughts and comments regarding your particular implementation, which protocol 
you use and how you see remote debugging appearing in webkit.

Regards,

-Sergiy Temnikov



3fa2fb.png

Sergiy Temnikov

Architecte Logiciel


Email :

sergiy.temni...@4d.commailto:sergiy.temni...@4d.com

Web :

www.4D.comhttp://www.4D.com


4D SAS

60, rue d'Alsace

92110 Clichy - France


Standard :

+33 1 40 87 92 00














___
webkit-dev mailing list
webkit-dev@lists.webkit.orgmailto:webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


Re: [webkit-dev] Remote debugger

2011-02-22 Thread Sergiy Temnikov
Hello,

I have not been on the calls but I have posted about my remote debugger work on 
the FireBug working group message board. It is true that Crossfire is smaller 
than the Web Inspector protocol but it has all I need for the remote debugging 
of a faceless server that runs JavaScript.
In fact the two protocols are quite close to each other, at least the part 
related to the source code inspection and tracing. I might even support both 
seeing that it does not require too much work to reformat messages from one 
protocol to another. I wish the two protocols were unified and compatible :-)

-Sergiy



[cid:f9ed10.png@1aafdebe.4b9b52d9]
Sergiy Temnikov
Architecte Logiciel
Email : sergiy.temni...@4d.commailto:sergiy.temni...@4d.com
Web :   www.4D.comhttp://www.4D.com

4D SAS
60, rue d'Alsace
92110 Clichy - France
Standard :  +33 1 40 87 92 00


De : Patrick Mueller [mailto:pmue...@gmail.com]
Envoyé : vendredi 18 février 2011 20:08
À : Joseph Pecoraro
Cc : Sergiy Temnikov; webkit-dev@lists.webkit.org; Pavel Feldman; 
loi...@chromium.org
Objet : Re: [webkit-dev] Remote debugger

Hello Sergiy,

Have you been on any of the FireBug working group calls?  Wondering if John J 
Barton and Michael Collins (like me, they also work at IBM) are familiar with 
your work.  I join the calls occasionally, just to keep up to speed with 
CrossFire, and don't remember hearing from you - but I also don't pay a whole 
lot of attention during those calls :-)

My understanding is that CrossFire really only supports JS breakpoints at the 
moment - if you look at the protocol that Web Inspector uses, you'll see it's 
quite a bit larger.

In addition to everything Joe mentioned, there's a guy who has Web Inspector 
hooked up to node.js for doing source-level debugging with node with the WI 
front-end.  https://github.com/dannycoates/node-inspector - I keep meaning to 
get in touch with that guy, but haven't yet.
On Fri, Feb 18, 2011 at 13:31, Joseph Pecoraro 
pecor...@apple.commailto:pecor...@apple.com wrote:


On Feb 18, 2011, at 7:04 AM, Sergiy Temnikov wrote:




inline: f9ed10.png___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


[webkit-dev] Remote debugger

2011-02-18 Thread Sergiy Temnikov
Hello,

I'm working on a remote JavaScript debugger for a server which uses webkit to 
execute JavaScript code. The debugger is shaping up nicely and is already very 
much functional. We chose Crossfire as the debugging protocol and developed our 
own UI debugger client. However, being Crossfire-compatible, should allow us in 
the (hopefully near) future to debug the server-side JavaScript using Firefox 
with Firebug and Crossfire plug-ins. I was wondering if there are any plans in 
the webkit community to create a native remote JavaScript debugger as part of 
the webkit build. If there are such plans then what would be the debugging 
protocol of choice? Webkit is already available on mobile devices but because 
of the screen size limitations it is not always reasonable to debug the 
Javascript directly on a device. Instead, it would be nice to debug the 
device's  JavaScript from a regular PC over the network.
If any of you are already working on a similar subject then please share your 
thoughts and comments regarding your particular implementation, which protocol 
you use and how you see remote debugging appearing in webkit.

Regards,

-Sergiy Temnikov

[cid:3fa2fb.png@5736e59a.47840135]
Sergiy Temnikov
Architecte Logiciel
Email : sergiy.temni...@4d.commailto:sergiy.temni...@4d.com
Web :   www.4D.comhttp://www.4D.com

4D SAS
60, rue d'Alsace
92110 Clichy - France
Standard :  +33 1 40 87 92 00




inline: 3fa2fb.png___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev


[webkit-dev] WebKit on the server side

2009-11-17 Thread Sergiy Temnikov
Hi,

We are working on a new application server that uses WebKit for server-side 
JavaScript execution (and remote JavaScript debugging too). However, we can not 
use WebKit as is because we  can not link with any of the GUI libraries and 
WebKit does. Instead, we compile just the JavaScriptCore part for JS execution. 
So my question is, are there any plans in the future to refactor or redesign 
WebKit to be more suitable for server environment? Would this, in your opinion, 
interest the WebKit community?
For example, the first thing we had to deal with is the JS debugger. Debugger 
interface is defined in JavaScriptCore but its implementation lives in WebCore. 
Most of the debugger's implementation is abstract except for the part which 
sends event notifications to pages and frames objects which are GUI dependent 
and so can not be used in a faceless server application. So we basically copied 
the source of the existing debugger, commented out GUI related calls and added 
some stuff to transform it into a debugger which can be controlled remotely 
over the network. I would be happy to contribute to the WebKit project to add a 
layer of abstraction to the existing debugger implementation to cut its 
dependence on GUI and move it to JavaScriptCore from WebCore's inspector.
Another example would be the XMLHttpRequest class implementation which exists 
in WebCore. In many indirect ways it depends on GUI even though it should not. 
As such, we can not simply expose it in our JavaScript environment on a 
faceless server. There are many other classes like it.
All in all, so far it has been great fun to make the WebKit code run on the 
server side. I just wanted to raise awareness of the needs of server-side 
developers.

-Sergiy Temnikov,
Wakanda Server Architect
Wakanda Software

___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev