mauricemach
commented
13 years ago That's very true. CCSS was actually born of a discussion on the pull request to add stylus support to it. Now in CoffeeKup I have concerns, especially about file size in the client side, and I think maybe these things should be available as plugins. But in zappa it's another story, it lives on the server so we don't have these constraints. One concern to me is namespace, but we can use configuration, or check if the modules are installed, and only provide the stylus and ccss functions if you're going to use them.
I'm about to publish a 0.2.0beta, and in the next iteration after it I'm definitely going to add this. I'll also check you guys' forks to see what else we can incorporate to the final 0.2.0.
By the way, very nice avatar! :)
DAddYE
Zappa uses CoffeKup as default template engine. They fit into each other very well. It's a good idea that templates use the same language as server-sive (and client-side, too), dropping out another layer of abstraction such as some specific template syntax (or at least making it more transparent). How about writing css the same way? There are a lot of fans of Stylus (http://learnboost.github.com/stylus/), and it's really cool. But I'd like to propose to integrate zappa with other cool, but less known, library https://github.com/aeosynth/ccss. It makes possible to write styles in CoffeeScript, so you will gain the same benefits the CoffeeKup gives. I already implemented it in my fork of zappa and can post the changesets.