[jbosstools-issues] [JBoss JIRA] (JBIDE-14897) livereload auto config is not as intuitive as it could be

[Max Rydahl Andersen (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-14897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen reassigned JBIDE-14897:
-------------------------------------------

    Assignee: Xavier Coulon  (was: Max Rydahl Andersen)


+1 looks good for b2
                
> livereload auto config is not as intuitive as it could be
> ---------------------------------------------------------
>
>                 Key: JBIDE-14897
>                 URL: https://issues.jboss.org/browse/JBIDE-14897
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: livereload
>            Reporter: Max Rydahl Andersen
>            Assignee: Xavier Coulon
>              Labels: new_and_noteworthy, respin-a
>             Fix For: 4.1.0.Beta2
>
>
> On beta2 with no livereload servers:
> "Open With > Web Browser via Live Reload Proxy" automatically creates a livereload server (great) but then it is not with the proxy enabled thus the action is not doing what it is told.
> Doing it with a server opened with remote access set it pops up with a dialog warning me about it. This seems excessive.
> Maybe should just do this:
> if no livereload server => tell the user that a LiveReload server should be created and ask him if he wants injection [default on] + remote connections [default off]. On pressing "ok" server is created, proxy is enabled and page is opened using the http:// protocol, on "Cancel", Livereload server is not created and nothing happens.
> if got livereload server and proxy is enabled => show page using http:// protocol
> if got livereload and proxy is *not* enabled -> ask user if he wants injection [default on] + remote connections [default off]. On pressing "ok" server is created and page is opened using the http:// protocol, on "cancel" nothing happens.

--
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