Should totally join forces with live_css. http://drupal.org/project/live_css

the main difference between your module and the live_css module is that the css change on the page happens automatically which is why I will stick with it - instead of having to click save each time. This sort of tool is extremely useful and with more developers concentrating on one module might really push the bar for this development.

nice work!

Comments

eme’s picture

eme commented

But live css, I think, is a system in which you edit "inline", and not with your favorite editor. And it does not replace Firebug (or equivalent).

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Fixed

ok , i did not realize that you where using your own text editor in the screencast i thought that was hooked into the browser. I still do not see how this could replace Firebug though, although you are changing the stylesheet i dont see how this module becomes an inspector for your browser.

This is potentially where combining the"pros" of both modules into one could create a better module. This two modules are extremely similar and from i can see the main difference is that with css watch you can use your own text editor whereas live_css you use the hooked in editor. live_css is actually more similar then css watch to firebug because it mimics the live editing of firebug , so as you are typing changes happen.

It is a very cool module and i would probably use it if live_css did not exist.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.