Hi all, I have seen a very nice thing in the js framework este ( https://github.com/Steida/este). What he does there, he basically has a file watcher and whenever his style changes, it is compiled with stylus, whenever his coffee script changes, it gets translated to js, whenever his js changes, tests are run.
I have started implementing this by copying pserve.py into my project and enhancing its file monitor with a possibility to have a callback, which is called every second. In this callback I (conditionally) compile my styles, and run unit tests. It's working nicely, but I have doubts whether this is the best way to go about it - meaning extending pserve. I somehow feel, that maybe this is not the right task for pserve, and I should do it the other way round - implement my own file monitor, which will control the restarting of my pyramid app, and compiling files and running tests. I will be greatful for any opinions. (I know about fanstatic and pyramid_fanstatic. Good for resource inclusion, but not what I seek for the less/stylus-->css.) Cheers, Petr -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
