[
https://issues.jboss.org/browse/JBIDE-13984?page=com.atlassian.jira.plugi...
]
Xavier Coulon commented on JBIDE-13984:
---------------------------------------
As far as LiveReload is concerned, this is actually a feature I'd like to implement.
Ideally, when LiveReload is enabled, the mobile devices should connect to a proxy port
(that the livereload server will provide - see JBIDE-13950), and then, the <script>
tag would be automatically injected.
To me, the trick is where to put this QR Code and how to plug the appropriate Eclipse
command behind, so that the generated QR Code matches the proxy URL if it is enabled or
not (this should be doable with command enablement property testers in the plugin.xml).
Also, in which module do we put this QR Code generator so that it works for OpenShift,
Cordova, LiveReload and the default server mode ?
Make it easy to try out a url on a physical mobile device
---------------------------------------------------------
Key: JBIDE-13984
URL:
https://issues.jboss.org/browse/JBIDE-13984
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Max Rydahl Andersen
It is tedious to type in url's, especially ones with just ip numbers on mobile
devices thus we should provide a way to make this easy.
Usecases:
* You are developing on your machine and want to test on your own physical phone
* You are presenting at a conference and want your audience to visit your website
running in cloud or on the local network
Suggestions:
Provide a way to show the QR code for a URL in the following locations:
* Browser and CordovaSim
* Provide "Show In > QR Coded URL" for an app/module
* Command that will take what is in clipboard/typed in and show the QR code
In some cases there might be more than multiple possible urls to use - i.e. you are setup
to use
http://localhost:8080 but that is not going to help anyone trying to connect thus
should make it easy to adjust the host part so you can type in the real host.
--
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