[JBoss JIRA] (JBIDE-16337) Support debugging of Cordova applications via Weinre and/or WebView debugging support
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16337?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-16337:
------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.)
> Support debugging of Cordova applications via Weinre and/or WebView debugging support
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-16337
> URL: https://issues.jboss.org/browse/JBIDE-16337
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Final
> Reporter: Vineet Reynolds
> Priority: Minor
>
> Currently, to debug Cordova app running on an emulator or a device (not CordovaSim), one needs to use Weinre (with no JS breakpoint capabilities) or use Safari/Chrome remote debugging (that supports debugging of WebViews with JS breakpoints).
> It would be nice to have this integrated via a "Debug As" menu, so that end-users dont have to
> * setup and run Weinre, or
> * add the webview-debug Cordova plugin to debug Chrome WebViews on Android 4.4
> All debugging strategies are listed here: https://github.com/phonegap/phonegap/wiki/Debugging-in-PhoneGap in case additional techniques can be considered.
> I'm assigning this a priority of minor, since this could be done manually, but bump up if appropriate.
--
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
12 years, 2 months
[JBoss JIRA] (JBIDE-16333) Report 32/64-bit Eclipse/Java
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16333?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-16333:
------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.)
> Report 32/64-bit Eclipse/Java
> -----------------------------
>
> Key: JBIDE-16333
> URL: https://issues.jboss.org/browse/JBIDE-16333
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: usage
> Affects Versions: 4.1.1.Final
> Reporter: Andre Dietisheim
> Fix For: 4.2.x
>
>
> On Mac there are limitations to use VPE (see mail thread started by Burr Sutter on 18/12/2013 "Eclipse on Mac OS X Mavericks") :
> {quote}
> Yes, that's our limitation on mac currently:
> a) you want VPE => you have to use 32bit eclipse => you have to use java 1.6
> b) you don't need VPE => you can use 64bit eclipse => you can use java 1.7
> {quote}
--
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
12 years, 2 months
[JBoss JIRA] (JBIDE-16330) Deployment to Android emulator ignores saved run configuration
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16330?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-16330:
------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.)
> Deployment to Android emulator ignores saved run configuration
> --------------------------------------------------------------
>
> Key: JBIDE-16330
> URL: https://issues.jboss.org/browse/JBIDE-16330
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Final
> Reporter: Vineet Reynolds
>
> The deployment to an emulator is always performed on a currently running AVD even if the runtime config for the project specifies a different AVD.
> Ignore/reject if this is by design. But from the point of view of the user, it would be better to ensure consistency - when a user wants to run his project on a specific AVD, he needs to create a runtime config, but the moment a different AVD is running, this config is ignored.
--
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
12 years, 2 months
[JBoss JIRA] (JBIDE-16312) Support importing of Hybrid Mobile projects into workspace
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16312?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-16312:
------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.)
> Support importing of Hybrid Mobile projects into workspace
> ----------------------------------------------------------
>
> Key: JBIDE-16312
> URL: https://issues.jboss.org/browse/JBIDE-16312
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Final
> Reporter: Vineet Reynolds
>
> Currently, to import a Hybrid Mobile project, I need to import it as a plain Eclipse project, while ensuring that the original Eclipse project file (.project) is present that contains the desired project natures.
> If the .project file is disallowed in version control, then this becomes a bit tricky since the .project file needs to be recreated.
> It would be better to allow support for importing an existing directory into the workspace as a Hybrid Mobile project (like importing existing android project, existing maven projects etc.) via the Eclipse Import menu.
--
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
12 years, 2 months
[JBoss JIRA] (JBIDE-16305) Document the Hybrid Mobile project artifacts that should be placed under version control
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16305?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-16305:
------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.)
> Document the Hybrid Mobile project artifacts that should be placed under version control
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-16305
> URL: https://issues.jboss.org/browse/JBIDE-16305
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.CR1
> Reporter: Vineet Reynolds
>
> I noticed the project directory containing a {{.cordova}} directory with a config.json file. Also, the Eclipse {{.project}} file contains a reference to the {[HybridAppNature}}.
> I'm not sure if both of these files should be placed under version control. Only the {{www}} directory seemed obvious enough to place under SCM. It would be great if we could get this documented so that end-users are aware of how to share Hybrid Mobile projects.
--
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
12 years, 2 months
[JBoss JIRA] (JBIDE-16347) New Tabs wizard for JQM 1.4
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16347?page=com.atlassian.jira.plugi... ]
Michelle Murray updated JBIDE-16347:
------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.)
> New Tabs wizard for JQM 1.4
> ---------------------------
>
> Key: JBIDE-16347
> URL: https://issues.jboss.org/browse/JBIDE-16347
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jsp/jsf/xml/html source editing
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha2
>
>
> Tabs widget can be implemented as navbar
> {code}
> <div data-role="tabs" id="tabs">
> <div data-role="navbar">
> <ul>
> <li><a href="#one" data-ajax="false">one</a></li>
> <li><a href="#two" data-ajax="false">two</a></li>
> </ul>
> </div>
> <div id="one" class="ui-body-d ui-content">
> </div>
> <div id="two">
> </div>
> </div>
> {code}
> or as listview
> {code}
> <div data-role="tabs">
> <ul data-role="listview" data-inset="true" class="tablist-left">
> <li><a href="#one" data-ajax="false">one</a></li>
> <li><a href="#two" data-ajax="false">two</a></li>
> <li><a href="ajax-content.html" data-ajax="false">three</a></li>
> </ul>
> <div id="one" class="ui-body-d tablist-content">
> </div>
> <div id="two" class="ui-body-d tablist-content">
> </div>
> </div>
> {code}
--
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
12 years, 2 months