On Tue, Feb 5, 2013 at 1:25 PM, Mickael Istria <mistria@redhat.com> wrote:
On 02/05/2013 11:07 AM, Yahor Radtsevich wrote:
On Tue, Feb 5, 2013 at 10:44 AM, Mickael Istria <mistria@redhat.com> wrote:
Hi Yahor et al.
I have some ideas/questions regarding integration of those tools in
BrowserSim and JBT/JBDS.
* Since most of them at actually HTML code, could the pop-up open in a
dedicated view inside JBT/JBDS? Would it make sense in term of usability?
Now BrowserSim opens as a separate process.
I understand that, and I think it's good to have it in a separate process.
What I had in mind is that the tab that contain the "debugger"
(Firefox-Lite, Weinre, Ripple..) probably has an URL and opens in a browser.
So if it's an URL, this could be opened inside an Eclipse view or editor
when launching BrowserSim. Don't you think it will improve usability and
consistency of the tools we provide?
* I remember a presentation at EclipseCon which highlighted usage of
BrowserFunction to make a nice interaction between web content -displayed in
SWT Browser- and Eclipse. See
http://eclipsecon.org/2010/sessions/?page=sessions&id=1418 and
http://www.slideshare.net/bokowski/embedding-web-uis-in-your-eclipse-application
. Do you have any plan to leverage this for a better integration of Ripple
and co in JBT/JBDS ?
Actually BrowserSim is an SWT-based application. SWT Browser widget
and BrowserFunction are already widely used in it.
We can integrate BrowserSim/Ripple windows in any Eclipse view, but
unfortunately it will lead to lots of Eclipse crashes and poor user
experience.
Indeed, it would be a complex and risky integration. I'm not trying to push
a feature here ;) That was just an idea I wanted to share in order to make
HTML debugging possible from inside Eclipse rather that in
yet-another-window.
Now I get your idea. Yes, this would be great!
Sadly, there are some limitations:
* Firebug Lite and Ripple require to be in the same process with
BrowserSim, because they communicate with BrowserSim as child/parent
browser windows.
Ok, I did not know about the linkage of those 2 windows through
child/parent browser window. It makes sense. What would be very fun
then would be to have browsers allowing to have child/parent windows
in different process with a protocol to communicate between them.