>> I've also been wondering lately if anybody has a good >> solution for organizing class files and stuff when a Shoes >> app gets too big for one file?
That's really funny! I was just sitting here building out a rails-ey project structure and putting some simple wiring in place so that I can just build everything like a rails app, but use shoes-ey views.... As I was doing that, the following occurred to me: a) The actual rails infrastructure might just work pretty much as is and maybe I should fork or patch or something from git. it seems like we'd have some really minor differences - like remote service models and subtley different view rendering. b) I'm sure _why has some conception about where this is headed, so I should probably check in first c) Someone else may already have something going in this direction? d) Rails doesn't really solve the old "unit test the GUI" problem. So there are still some issues there. I hear that rspec goes quite a ways in this direction, but I'm not quite seeing it yet. e) I'm an expoert GUI developer, but novice rails developer, and it might be smarter to pair up with a rails expert on this idea. f) I absolutely love the simplicity and approachability of Shoes and I have a tendency to overcomplicate simple things, so I'm hesitant to go too far in this direction - especially if there are alternatives in place. g) I haven't even looked at _why's alterna-rails-thingy Anyone else interested in this problem domain? Thanks, Luke Bayes http://www.asserttrue.com
