Just wanted to get some feedback about a new feature we've released.
Not sure how many of you know about Sasson's "file watcher". for those who don't - you can watch a list of files (entered in theme settings form under "Development"), everytime a file is modified - your browser will automatically refresh itself so you get instant feedback on the changes you just did in the files. cool.
The news are that on the latest release, the file watcher works (for stylesheets - CSS/SCSS/SASS) without refreshing your page (!).
That means two things - a. it's faster and b. if your on a dynamic page (e.g. ajax form opened in a popup) it won't disturb your development with a refresh, only update the styles.
Try it, and please share your experience.
I hope this will be a better place to post this. I've first tried the forums and got 0 response.
Comments
I honestly thought this will
I honestly thought this will blow your mind...
devel module perhaps?
This would be a very useful functionality on its own, alas, it's bundled into a base theme.
Perhaps the devel module would be a better place for this.
I agree, it would be more
I agree, it would be more useful separated into it's own module, making it available to drupal users not wanting to be tied to sasson just to use it.
Since it doesn;t support the latest sass/compass version, a native compiler is much more useful to me personally. LiveReload is a good local solution to use with a native compiler for instant page reloads.. but I'd be interested in looking further into how page reloads are done on css changes in sasson.
Not that have anything
Not that have anything against this living in a separate module (too), but for me it does makes sense to put it in a base theme, or a theming toolkit as I like to think of it.
This feature can't be 'theme agnostic' because that means it will refresh your page when a watched file is modified even if you're on a section of the site that uses a different theme (e.g. administration theme). that means that if this goes in a module you'll have to make the user select a theme from a list and then check if the relevant theme is in use at the moment, before doing your refreshing/updating, to me it just seem logical to put it right in the toolkit.