On 14 February 2013 01:01, Mohammad Nour El-Din <nour.moham...@gmail.com>wrote:
> > 1- Having these domain model classes: > - Tasks > - Timesheets > - Employee > - Team/Group (Collection of Eomployees) > > Only listing these ones as an example and for the sake of simplicity, and > then build the application in a way that Admins can go and start to lay out > tasks and assign tasks to individual employees/groups, employees then can > see/access these tasks and fill in entries in a time sheet bases on these > tasks > > Maybe I am wrong, I am still learning the Isis way, but a truly feel the > way I explain it more fitting Isis than traditional time/task tracking > systems > > Thoughts ? Hi Nour, Don't get me wrong... there'd definitely be value in building this application. As Minto says, there are custom applications out there already in this domain that set a bar to hit. But it'd be a great exercise to build this app in Isis anyway, for thee reasons: * it'll drive out new concrete requirements for Isis. We're seeing this from the app Jeroen and I are building (wicket viewer enhancements & styyling, jdo, pubsub etc); similarly Adam's porting of the ddd sample is identifying some gaps, eg the rendering of aggregated objects * it'll be a good example to others of how to build a larger scale application * it may provide some reusable code (domain entities, domain services etc) for others to use The best thing to do is just to start a new github repo, run the archetype, and get coding. It won't take long to get a first version of your app running. As others are doing here, get it deployed on Heroku or GAE and invite others to contribute. Cheers Dan
