- #INSTALL FIREBUG PLUGIN INSTALL#
- #INSTALL FIREBUG PLUGIN UPDATE#
- #INSTALL FIREBUG PLUGIN FULL#
- #INSTALL FIREBUG PLUGIN DOWNLOAD#
XRefresh monitor communicates with the browser extension using TCP/IP. I'm editing files directly on my server via ssh, is it possible to use XRefresh over the network? For Safari there is a similar project to XRefresh called LiveReload. Support for IE will be dropped in the future. You should be able to see soft refresh icons when modifying code.js. Here is a minimal example page using this technique. Soft Refresh JS is disabled by default, you need to enable it in XRefresh menu (under context menu on XRefresh tab button).
#INSTALL FIREBUG PLUGIN FULL#
If you don't understand these consequences it is better to not enable this feature and go with full refresh.
#INSTALL FIREBUG PLUGIN UPDATE#
So it is not able to remove deleted functions, it will not update anonymous functions bound to elements or for example it will not call the jQuery onReady function again. Remember, the updated script is just evaluated as-is in the context of the main window (because it is added as a new script tag). It works similar to Soft Refresh of CSS, but there is a catch. XRefresh is also able to replace externally linked JS file with updated version without reloading whole page. You should be able to see soft refresh icons when modifying style.css. This is disabled by default, you need to enable it in XRefresh menu (under context menu on XRefresh tab button). With this feature you can get a similar experience as Firebug on-the-fly CSS editing (without the pain of syncing changes back to original source). The page stays in the same state and does not blink during refresh. I call it "soft refresh" and it is handy in dynamic AJAX-style applications. XRefresh is able to replace an externally linked CSS file with an updated version without reloading the whole page. With XRefresh you don't need to switch between windows. One display is fully dedicated to your browser window showing the page you are currently editing. Why is dual monitor setup great for web development? LiveReload has more features, it is maintained and also provides support for multiple browsers. Recently Andrey and other guys from LiveReload put a lot of effort into making a better tool for refresh-driven development. The main issue probably is ever changing Firebug and Firefox versions and time it took me to maintain the compatibility. I started XRefresh back in 2007 and it worked really well for me and other folks, but it has some issues. No, XRefresh was superseded by LiveReload. You may also specify the path to your config file via -config parameter. You are encouraged to modify paths section to map to your working project directories.īy default the config file is searched for first in the current directory and then in your home directory. When it is first run, a default config file will be created in ~/.xrefresh-server.yml: Having problems running it? Maybe it's because of Rub圜ocoa problems, as some people had on Leopard.
To start the server simply run xrefresh-server from command-line.
#INSTALL FIREBUG PLUGIN INSTALL#
execute sudo gem install xrefresh-server.Īfter installation, the xrefresh-server executable should be added to your system path.install Ruby Cocoa (filesystem monitoring depends on native Cocoa FSEvent API).
In Internet Explorer 7 you can find the XRefresh icon in the tools in the top right corner (the icon may be hidden in the chevron section). You need to enable Firebug for a particular site to enable XRefresh functionality. XRefresh has its own tab panel in the Firebug window. Let Firefox or Internet Explorer connect to XRefresh. Tip: You can simply drag&drop interesting folders onto configuration dialog. XRefresh will watch for your modifications. Tell XRefresh where your files are located. Launch XRefresh and check for it in the traybar.Īfter starting, the icon is gray which means that there are no browsers connected to XRefresh. It will install XRefresh traybar application and IE plugin.