Quote from: lossendae at Jul 22, 2011, 05:31 PM
I use LESS but in a totally different way:
I don’t try to integrate it with MOdX.
I think that LESS is really nice, but since MODx has no predefined blocks, it is not really needed on production website.
So i use it outside of MODx in development and use the cache.css file in production.
The onl missing feature imo is to allow CSS comments in the cache file. It could be useful.
My whole point was to allow LESS into my current workflow; I edit the CSS files on a server via FTP (not locally) as I build them. That way you can see changes in real time on the MODX site as you build it (yes, over time I’ve taken to building my sites/templates from the ground up in MODX itself... it just seems to go much faster for me). This method allows me to replace those CSS files with LESS files on the server, still see all my changes in real time, and when I’m done, I’m done, plus, I can come back to it down the road and make edits easily—all without moving around a bunch of files. The LESS file, for all practical purposes,
is your main working file (no need to even think about the compilation going on really—except to make sure that you clear the MODX page’s cache when you’re done editing); That gets around your commenting issue (maybe) since you have all of your comments in the working LESS file.
That’s just my workflow... everyone’s is probably a little bit different (maybe my code here can help someone, maybe it can’t—can’t hurt to share!). Either way, BIG kudos to MODX for allowing you to do just about anything in any way you want!