For a recent project I needed functionality like the editwizards integrated
[snip]
If we would spend more time to make this solution more generic I think configuring "editwizards" would come down to writing some include tags with parameters like the examples above. The code I've written so far to make this possible is just one JavaScript include file and some Java methods. This makes it easy to extend and to add your own flavor to the end result.
I would like to share my experience with this project and idea's for making it more generic. So count me in for any meeting on this subject.
I would like to add to that hat maybe some of the functionality Jaco described above could even be integrated in a flexible editor. My intention for making my_editors was like Jaco described: provide building blocks with which you can easily build your own editors but somehow i never succeeded in that.
Another thing i would like to add is an mm:edit tag that makes editing in/above the page possible. The following code is something i've been experimenting with and displays a link or button to an editor in the template.
<mm:edit editor="editor.jsp">
<mm:node number="an_article">
<mm:field name="title" />
<mm:field name="body" />
<mm:related path="posrel,urls" fields="urls.url">
<mm:field name="urls.url" />
</mm:related>
</mm:node>
</mm:edit>All the field tags register themselves with the edit tag and thus providing it with a view of the subcloud the edit tag has in its body. The edit tag then creates an url with parameters containing the fields, nodes and paths it has found. With that you can open an editor that makes you able to edit the fields that were contained in the body of the edit tag.
I've got a demo that works (as far as i've tested) with all the nodeprovider tags. Currently i'm working on the editor on top of this.
Great advantage of an edit tag like this is that you don't have to write an editor cause the edit tag 'reads' your cloud and provides you with an editor for the (sub)cloud you encapsulated in the edit tags body.
---Andr�
Rob Vermeulen wrote: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
-- ------------------------------------------------------------------>><<-- Andr� van Toly http://www.toly.nl 06-27233562
