Planned as one of the top features of LiveReload 3.
I have a main style.scss file and a bunch of 'module' files in module/*.scss. There are then @import'd into the main stylesheet. The modules folder is excluded from compilation as I do not want a .css file for each module.
If I make a change to a module, I have to save both the module and the main file to force a recompile and a browser refresh. That's getting increasingly frustrating.
It would be great to be able to say 'dont create a .css file for <file>, but do recompile <file>'10 votes
Adam and others, while the feature described in the subject line (“more complicated rules”) is coming, the described use case should already work with LiveReload 2.
Please upgrade to the latest version from http://go.livereload.com/mac and, if it still does not work, please contact support and provide a test case to reproduce it.
In firebug or chrome dev tools click on css detail line "#content .message style.css:47" and open corresponding style.css with selected IDE on line 472 votes
Sometimes I made stupid syntax error than made LESS compilation fail. Would be cool to get some kind of no obtrusive alert (like growl).9 votes
where dev custom compile settings are overridden to output uncommented, compressed code for production use - to save going in and tweaking and untweaking dev settings.5 votes
Working on this. Not sure if it will get released as LiveReload 2.4 or 3.0 alpha; stay tuned.
To achieve the same request as 'shortkey to activate/deactivate reload' but I'd like it in the set-up of each site, or even a 'toggle' with the JS include.
I predominately use LiveReload for Less compiling. So I can't just disable as my Less files won't compile but I don't have control of when/if a browser should refresh.
I might have a preview open in CODA and 3 other browsers. CODA auto refreshes anyway so I get a double page reload! Usually writing JS is when I don't want everything refreshing all the time.
Great App BTW :D6 votes
It would be nice to have some sort of messaging when a reload is successful, not just unsuccessful, just for reassurance.29 votes
Planned for LiveReload 3.
Seeing that "Apply" button on every dialog always throws me off, as I'm used to only seeing an "Apply" button when I have made a change.4 votes
Imagine how cool it would be to make changes in your WordPress / Drupal / Joomla admin page and have your site reloaded automatically? If you're used to tweaking your posts, or theme colors, or whatever, I'm sure you can appreciate that.47 votes
Still looking for a feasible technical implementation, and for the best UI. Which frameworks would you like to be supported?
Give us a preference pane for the Green "Status" screen, with option on what to report, how detailed, sound, clearing after ... etc.5 votes
Sometimes I work on files called by ajax function. I don't need to reload the pages where livereload is activated.
It will be useful to set a shortkey to quickly activate/deactivate livereload.4 votes
I like this idea, but I’m not sure whether a shortcut is the best UI/UX for that. Ideas welcome.
Planned for LiveReload 3 (or maybe even 2.4/2.5, if those see the light of day.)
Which are the top 3 features you would like to access from the command line?
Is a command-line version enough on Linux? Let me know in the comments!
I need some of the features of sass 3.2 (alpha) but live reload seems to be independent of the versions on my system and use it's on internal version. The ability to choose or at least specify the system version on compile would be handy :)15 votes
Multiple compiler versions support is planned, but for now: all beta builds ship with Sass 3.2 alpha, so just get one from http://go.livereload.com/beta
So here's my problem preventing me from using LiveReload on Windows. My name is Adrian Cearnău and that ă that is a part of my Windows profile name (and therefore profile folder name) gets LiveReload confused (I think). Here's a log file of what happens when I try to run it:
2012-07-26 14:03:39 LiveReload 0.0.4 launched
throw e; // process.nextTick error, or 'error' event on first tick
Error: Cannot find module 'C:\Users\Adrian Cearnďż˝u\AppData\Local\LiveReload\App\Resources\backend\bin\livereload-backend.js'
at Function._resolveFilename (module.js:334:11)
at Function._load (module.js:279:25)
at Array.0 (module.js:470:10)
at EventEmitter._tickCallback (node.js:192:40)4 votes
Definitely going to fix.
The little grey box is not readable, not easy to close, and far too small for the medium length of an error message.17 votes
Planned for LiveReload 3.
Let me specify 2 folders, one 'source' and one 'output'. Then, compile all files in src/ into their same spot in output/
So, if I have
This gets compiled into
Isn't this how most sane people structure their code? Doing this now is a huge pain, since I have to set output directories for every sub-directory I have6 votes
A flexible rules system is planned for LiveReload 3, so that you can add a rule like src/js//.coffee → public/js/**.js, and that covers any matching files. Sounds good?
- Don't see your idea?