Dear Lenya Team, I've to develop a webbased info-system for a laboratory. The main datasource will be a database with medical information (tests, results etc.). But there's also a need to manage "typical" cms-content for example user-documentation about the system itself, howtos, faqs ... As I'm developing with Lenya for about 1 1/2 years, like its features very much and used it already for a similar situation (website with db-based customer service area on Lenya 1.2.4) I want to use it again for this project.
For all the DB-related things (the forms to edit the records and the data-views) I've created a module. For the GUI I think that CocoonForms and its binding framework is a good choice. But at the moment I see three ways to implement these record-editing-views and I'm not sure what will be the best. So I hope that you can give me some hints, pros and cons on that: 1) the new usecase-framework with custom flowscripts 2) usecase implementation as in 1.2.4 3) no usecase The editing will be like this: - read rec from DB and initialize form - validate form using the CocoonForms validation features - additional processing on the rec handled by the rec-representing bean - return to form with (error)message or - update DB and go (back) to some view Best regards, Gerd --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
