[
https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin....
]
Ilya Buziuk commented on JBDS-2866:
-----------------------------------
{quote}
One critical test case is...does it work with something like
$.getJSON("http://mobile-html5.rhcloud.com/rest/members", function(data)
.
.
And besides deviceready console.logs, I also need to see JS syntax errors that show up
when the page loads/refreshes.
{quote}
[~burrsutter], Dev tools debugger will handle Cross Domain AJAX calls and js syntax
errors. I've made a short demo video -
https://www.youtube.com/watch?v=Xsv6NSozHJQ .
Burr, I want to know your vision of one important point - where should dev tools debugger
be opened? Now I have 2 options - it could be either Chrome browser or javaFx pop-up
(javaFx WebView) !DevToolsMenu.png|thumbnail!
Each approach has pros and cons:
*Chrome Browser*
- oracle JDK 7 and 8 will be supported;
- debugger works more stable;
- more pressure on user - chrome installation is needed + need to set it as a default
system browser.
*JavaFx Web View*
- debugger support out of the box
- debugger works less stable. It freezes very often while debugging - I'm working
on that issue
- oracle JDK 8 only (No web websocket support in javaFx 7)
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