[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-333) NeedInfo: How does LiveReload work?
[
https://issues.jboss.org/browse/TOOLSDOC-333?page=com.atlassian.jira.plug...
]
Michelle Murray commented on TOOLSDOC-333:
------------------------------------------
Thanks [~xcoulon], great explanation. I had seen the video from JBoss Tools blog but never
with the sound.
I've got another question about the proxy server configuration. This aspect looks
great - far better than having to install the LiveReload browser extension. I like that we
can simplify things for users by keeping it all in the IDE with minimal
installing/configuration. About proxy and web browsers ... so a user selects a file and
clicks 'Show With' > 'Web Browser via LiveReload Proxy' and then the
IDE browser preference is used in deciding which type of browser window to open.
* With the browser extension, users were limited to chrome and firefox because of using
file URLs. Is this restriction lifted with the proxy server because it is using HTTP? So
if a user's IDE browser preference was 'system default' and their system
default was 'Safari' then LiveReload would now work?
* I typically have my IDE browser preference set to 'internal web browser' but
LiveReload doesn't seem to work with this browser. Why is that?
NeedInfo: How does LiveReload work?
-----------------------------------
Key: TOOLSDOC-333
URL: https://issues.jboss.org/browse/TOOLSDOC-333
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Task
Security Level: Public(Everyone can see)
Components: User Guide
Affects Versions: 4.1.0
Reporter: Michelle Murray
Assignee: Michelle Murray
I am trying to document LiveReload Tools (integration of LiveReload in JBDS) and I have
some questions about how it works.
Users need a LiveReload server within the IDE and the LiveReload browser extension
installed in Chrome or Firefox. Why are both needed? How is the work process distributed
between the two? Which is responsible for which tasks?
I ask because I could imagine the browser extension just looking for changes in file time
stamps and consequently reloading pages. It clearly isn't as simple as that but I
don't see how the LiveReload server fits in.
Just read an email from Max to Burr, which separated functions into server-side and
client-side. So does LiveReload work something like this: "The LiveReload server
handles the server-side of the LiveReload action, such as sending request to refresh web
pages. The browser extension handles the client-side of the LiveReload action, such as
refreshing pages."
--
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