Node CSS

Nice module idea, I'll take a look at this tomorrow.

Reviewing the code there are minor code formatting tweaks that could be made, e.g.:

• Unnecessary $Id$ comments, e.g. nodecss.install.
• Unnecessary empty lines after long comments, e.g. in nodecss_uninstall()
• Unnecessary empty lines before closing parentheses, e.g. in nodecss_uninstall()
• Missing blank line at the end of the file, e.g. nodecss.install.
• Some lines not intended enough, e.g. a few lines in nodecss_schema().
• Some todo comments for functionality that appears to already be implemented, e.g. nodecss_uninstall().
• Some translated strings have unnecessary whitespace.
• Not all comments are wrapped correctly at 80 characters.
• Comment sentences should have a period at the end.
• Words should be spelled with American English, e.g. 'color' vs 'colour'.
• A few other minor things.
• The CSS output from css.tpl.php doesn't follow the coding standards.

A few other suggestions:

• You might want to add some validation code to the settings page to ensure that the requested files are present, to avoid needless 404 errors.
• It would be useful to add a README.txt file to provide some (limited) instructions on what the module can do and how to use it.

Take a look at the attached patch, it cleans up most of the coding standards issues.

Good stuff, getting very close. A few items:

• The README.txt file doesn't need the CVS-style comment at the top, instead should list the project name and should give an explanation of what the module is for along with the configuration instructions.
• Remove the unnecessary blank line at the top of nodecss_theme().
• Rather than using several variables to control the template path in nodecss_theme(), you should just define it relative to your module's path and then let users use normal normal template engine's functionality to change it as needed.
• A small thing - you could change nodecss_node_save_css() to have one main if() check around nodecss_node_enabled($node) and nest the rest of the logic inside that.
• In nodecss_node_css() you might want to do a check to see if $css_vars is empty before going through the effort of theming it, i.e. if it is empty just return an empty string or NULL.
• Given you're writing the module for D7, you might consider giving it a more general name and then for a future "v2" write it to work with all entities rather than just nodes. Making this change now would be easier than later, so you don't potentially end up with a project "nodecss" when what you really want is e.g. "entitycss".
• Another small thing - you don't need to list files in nodecss.info if they don't have classes that you wish to lazy-load, though it doesn't really hurt anything.
• From a performance perspective,

I think this is very good with the improvements, takes a different approach than the current CSS module and only has small issues remaining (besides a v2-worthy expansion of functionality). I'd like to see a response from @xalan regarding plans for the module's future vs naming convention (see my comment #5 above) but otherwise this is good & worth approving.

Any further progress on this?

No activity in several months. Reopen and set the status to "needs review" if you are still pursuing this application.