7 ms·
here's the even better example app https://github.com/paulmillr/ostio https://github.com/paulmillr/ostio http://ost.io http://ost.io backbone + coffee + chapl
by paulmillr 14y ago
here's the even better example app
https://github.com/paulmillr/ostio https://github.com/paulmillr/ostio
http://ost.io http://ost.io
backbone + coffee + chaplin + brunch + rest api + nested models / views + collectionviews + controllers (+session controller with GitHub auth) + actually a real-world application
- ch 14y agoArgh! That really messes with the back-button. Otherwise its quite pretty.
- drivebyacct2 14y agoNo matter how much I try, I can't understand what brunch is trying to do or why it's necessary enough to even create.
- paulmillr 14y agoThat's simple: brunch is a project builder. You put vendor styles / scripts in `vendor`, then you edit your `app` files. No matter what language you want to write, brunch will compile it on `brunch watch` or `brunch build`. Of course you can make some sophisticated makefiles and connect sophisticated file watchers there (brunch fastly rebuilds project on every small change), but why do this when there's brunch which just works?
- soulclap 14y agomaybe that's my problem with backbone and all these frameworks without a lot of conventions. i am not really good at javascript and can't figure out which approach is the bestestest. i am working on it, though. got no choice.