Hello Gerd
Am 03.02.2008 um 04:45 schrieb [EMAIL PROTECTED]:
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
You're refering to lenya 2.0(.1) - right?
It might depend a bit on your needs.
I think it makes sense to use the new usecase-framework.
If your gui cform pages need to behave like a document, you could set
up your usecase using the usecasedocument module.
That way your form pages will have
- the styling of a normal page (envelope, menus etc.)
- a workflow
- metadata
- can be "translated" by creating a language version via the authoring
gui (as long as the necessary i18 is present in your form/template)
The contactform module gives an example how the usecasedocument module
can be used.
Two functions can be used to write custom flowscript: customLoopFlow()
and customSubmitFlow(). See modules-core/usecase/usecases.js.
See the cforms module for more hints.
I had to override the sitemap of the usecasedocument module to get
cforms fully working:
I added the i18n catalogue of the cocoon cform framework to the i18n
transformer and uncommented the xhtml2xhtml transformation
(It interfered with the dojo scripts in the header section).
This approach helped me to get cforms working, but I'm not shure if it
is best practice.
Bests,
Jürgen Ragaller
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
