[
https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin....
]
Ilya Buziuk commented on JBDS-2866:
-----------------------------------
{quote}
we might as well drop the FireBug Lite once this is in place
{quote}
Definitely. There will be no "Firebug Lite" menu item for JavaFx WebView
engine
{quote}
especially if it stays open during LiveReload refreshes
{quote}
Yesterday I fixed LiveReload and TouchEvent for javaFx WebView. Now everything works
just fine
{quote}
Do the line numbers match up between the debugger and if using Eclipse as the JS
editor?
{quote}
Yes, they do
{quote}
As far as Chrome vs JavaFX goes...
{quote}
Yes, I also like Chrome. The problem is - how should we open it? AFAIK the only solution
is org.eclipse.swt.program.Program.launch(url). However, this will work only if Chrome is
the default system browser. Yesterday on 1-o-1 [~maxandersen] made a very interesting
proposal - show pop-up with an appropriate text message and url for debugging. I think
it's pretty nice solution. So, I have implemented it and made a demo video. Demo also
covers collaboration with LiveReload -
http://www.youtube.com/watch?v=C8dMNWWfK3A&feature=youtu.be
CordovaSim Debugger
-------------------
Key: JBDS-2866
URL:
https://issues.jboss.org/browse/JBDS-2866
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: browsersim, requirements
Reporter: Burr Sutter
Assignee: Ilya Buziuk
Attachments: DevToolsMenu.png
The current FireBug Lite in CordovaSim has the following limitations:
1) When using LiveReload, the window closes with every reload
2) Various "page load" events with console.log statements are not visible in
FireBug Lite console, like having console.log() in your deviceready
http://screencast.com/t/RRGhV9PV
Note: I forgot to add the Console Cordova plugin, not sure if that is necessary but the
window closes, so not sure how I would see the message
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira