cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patrick Mueller <pmue...@gmail.com>
Subject Re: Regarding integration of Weinre to eclipse framework.
Date Tue, 30 Oct 2012 12:08:43 GMT
On Sat, Oct 27, 2012 at 12:19 AM, Karthik <ekarthiksetty@gmail.com> wrote:

> I am planning to develop a tool for eclipse community where in people would
> use eclipse for debugging the remote browsers DOM's, css etc.
>

cool


> I am now thinking to integrate cordova to eclipse, so thought of discussing
> this on this list.
>

I think you mean weinre instead of cordova (given the previous message you
sent to me).   weinre is a sub-project of the Apache Cordova project.

I'll give you one warning now.  As Web Inspector was written for WebKit, it
will likely never run (the client, UI code) in a browser other than a
WebKit-based one.  If you're going to try to integrate this in Eclipse,
you'll probably want to use the SWT Browser widget, but, again, this will
only work to display the weinre UI if that browser widget is using a
WebKit-based native browser widget.


> Does cordova expose any apis, which I could use and develop this tool?
> Do you have any picture which explains the server-agents (client, target) .
> (Like the command sent and response received)?
>

There aren't really any APIs for weinre itself.  weinre is really just a
tool, where I bolted the Web Inspector front-end onto enough code to get it
to do what it does.  There is an API of sorts available, where you can send
messages back and forth, defined by Web Inspector.  And weinre adds it's
own little API bits to that as well.  Look for the idl files.


https://github.com/apache/incubator-cordova-weinre/tree/master/weinre.server/interfaces

The Web Inspector .idl files will be here, after you've done a build:

    weinre.build/vendor/webkit/WebCore/inspector

Although I don't really have a way of using these APIs today, outside of
the tool, it's not out of the question to provide one.


> If possible can you please provide me more tips on how to build this tool.
>

There should be documentation in the project files on how to do a build -
start with the base README and it should point to additional resources.
 Several folks have figured this out, so this seems like a good first task
- there will be much searching around the code for what you are trying to
do.  If there's anything we need to clean up with regard to the build docs,
please open a bug.  There's a link to create a weinre bug on the main
weinre page:

    http://people.apache.org/~pmuellr/weinre/

-- 
Patrick Mueller
http://muellerware.org

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message