I've never actually implemented a timesheet-app. I merely start one on every new, "faster" technology I'm trying to learn. (And even though it's the noddiest useful app I can think of, time always runs out before I've finished!)
Remember too: I'm not too worried about how long my first app is going to take; I wanted to know how quickly I'd be able to churn out the later ones (especially compared to "hand"-coding them). I'm actually slightly disappointed by Wouter's 3 week estimate, but given that he's starting at 2 days for a (presumably working) "prototype" I guess he's being conservative (and allowing for my extra security requirements and my poor javascript)! Thanks for all your recommendations and comments (and feel free to keep 'em coming) - it's turning into exactly the type of thread I (and hopefully others) like to read when evaluating a new technology. Mike. _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=3798#3798 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
