CSS Injector Integration

Great! Looking forward to it! I didn't know exactly where to put these following ideas, but it seems like you (Dustin) are at the cutting edge of css modules for drupal, so i just thought i would get them into your mind...

CSS Freeze & CSS Diff. CSS Freeze would take a snapshot of all current css files & would then be able to revert to & back from these "frozen" states/ past revisions. CSS Diff would show the difference between any 2+ CSS Freeze snapshots.

The CSS Freeze would be possible now thanks to CSS Watch monitoring a specific list of css files. This list would be passed to css freeze. Whenever a CSS Freeze snapshot needs to be taken - these monitored css files could just be copied/ duplicated into a sub-folder (which is named as whatever you label the particular snapshot as OR by date (default)). Then whenever you want to re-enable a past CSS Freeze Snapshot, these old css files would just be copied to overwrite the current ones. CSS Diff's features are relatively implied at this point (but having the ability to quickly toggle the theme back & forth in between diff revisions would be great)

Eventually css freeze could provide importable/exportable packages of css files. Then people would be able to build huge databases of css mods (CSS Freeze Snapshots) for each specific drupal theme ( http://drupal.org/project/themes ) -> which would be a very valuable resource to share!
Thanks

CSS Freeze may be better renamed CSS Version Control System (CSS VCS), or CSS Snapshot.

A general VCS (version control systems) solution would be ideal for people designing sites off-line or on their own server, but a lot of people use shared hosts & build websites live on the internet. I know that this is not good practice, but it can be very quick to copy/ paste websites & then mod them in this way. With a VCS, wouldn't the WHOLE site need to be reverted back & forth (between versions)?

What if the changes are being made to a live site & only the css should be reverted back & forth (as to avoid losing any new content created during modifications).?

Furthermore, it would take much longer to change a site version w/ VCS rather than using the method outlined (simple css file overwrite auto-updated w/ the css watcher & css freeze)

The best feature that this would provide is importable & exportable packages of css files -> that can then be shared among the drupal community to quickly mod popular themes. It would be hard to share css files w/ a general VCS, because there would be far too many other unneeded files & there is no established drupal system for sharing theme-specific add-on css files (yet).

Idea for implementation: you could have a fixed overlay link in the upper corner that would allow you to take a snapshot w/ a modal frame pop-up for renaming it & for viewing/ controlling a directory of past snapshots. The importing / exporting would be provided easily due to the fact that CSS Watch has a list of specific css files, & the CSS VCS would be the combination of these files identified (stored in folders) by the date or a custom name. The CSS Diff will have to wait until the CSS VCS is done.