It sounds to me like you've got a solution before you've undergone a design process… with that in mind I'd suggest two simple things:
1. take a step back and ask yourself what problems you're aiming to solve and take a stab at how you think you'll achieve them. 2. 3 months is a *lot* of software… have you prototyped anything? how far along towards your goal can you get in 1 week, 3 weeks? Having said all of that, David Goodlad (a Melbourne rubyist) had a prototype of a really interesting scheduling app, perhaps he would be interested in licensing it to you? Good luck! -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" 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/rails-oceania?hl=en.
