The proposal for improvement of the EditWizards that we originally
drafted at Kennisnet (the one that ended up at the VPRO) consisted of
the following functional improvements:

1. enable to declaratively implement single-field validations in the
wizard xml. Things like '>100' or before '12:00'.

2. enable to declaratively implement cross-field validations. Like
conditionally make certain fields mandatory depending on the value of
some other field.

3. enable table-constraints validation so that useful error messages can
be shown on unique key violations. 

4. better handling of errors coming from underneath the bridge

5. being able to mix relations to multiple nodes posrelwise. We need
this to mix links and attachments in articles. This functionality is
already implemented by us but not reusable enough.

6. checkboxes and radiobuttons (already implemented)

7. being able to use any java Collection to fill EditWizard listboxes.

8. creating more hooks for java custom code

9. creating hooks for pre- and postscreen triggers

10. enabling embedded links within textfields to urls and images and
still create an insrel (WIAB has somehting like this).

11. being able to generate searchscreens

hi developers,

I noticed that many people are thinking about making new MMBase wizards.

The current implementation seems to be to difficult to use, unstable, 
not flexible, it needs a lot of resources, etc.. The last days i spoke 
with some people that are already having nice ideas about engineer new 
MMBase wizards. And I would like to plan a meeting, or start a 
discussion on this list about how we think about new MMBase wizards. The

foundation asked the VPRO if their want to join some organization in 
improving the current wizards, but we don't like this idea because the 
current wizards are not a good starting point and are becoming more 
complex, and less usable.
Instead, we are thinking about starting over again, keeping in mind the 
lessons learned, and create simple wizards. Simple to configure the 
wizards, and simple in the sense of using common technologies and don't 
stack to many technologies that are making the current wizards very
complex.

I already know some people that would like to join a team to create new 
wizards, please let me know how you think about this. I really hope that

we can join forces to create good wizards.

Rob Vermeulen




-----------------------Disclaimer-------------------------
Dit bericht (met bijlagen) is met grote zorgvuldigheid samengesteld. Voor mogelijke 
onjuistheid en/of onvolledigheid van de hierin verstrekte informatie kan Kennisnet 
geen aansprakelijkheid aanvaarden, evenmin kunnen aan de inhoud van dit bericht (met 
bijlagen) rechten worden ontleend. De inhoud van dit bericht (met bijlagen) kan 
vertrouwelijke informatie bevatten en is uitsluitend bestemd voor de geadresseerde van 
dit bericht. Indien u niet de beoogde ontvanger van dit bericht bent, verzoekt 
Kennisnet u dit bericht te verwijderen, eventuele bijlagen niet te openen en wijst 
Kennisnet u op de onrechtmatigheid van het gebruiken, kopi�ren of verspreiden van de 
inhoud van dit bericht (met bijlagen).

This message (with attachments) is given in good faith. Kennisnet cannot assume any 
responsibility for the accuracy or reliability of the information contained in this 
message (with attachments), nor shall the information be construed as constituting any 
obligation on the part of Kennisnet. The information contained in this message (with 
attachments) may be confidential or privileged and is only intended for the use of the 
named addressee. If you are not the intended recipient, you are requested by Kennisnet 
to delete this message (with attachments) without opening it and you are notified by 
Kennisnet that any disclosure, copying or distribution of the information contained in 
this message (with attachments) is strictly prohibited and unlawful.
----------------------------------------------------------


Reply via email to