Hello Pierre,
I finally found the time to read your proposal. First I don't really get
why there are datatypes in the definition. Most of the stuff is present
in the old defintion files and only because they couldn't be requested
from mmbase. I don't think it is a good idea to introduce this.
Pierre van Rooden wrote:
I received the iteration process a week ago, with the newly proposed
structure, which looks promising.
The main question I have concerns the replacement of DOM with POJO. My
question is how you will solve the use of xpaths. If you plan backward
compatibility these need
Nico Klasens wrote:
I tried not to use xpaths in the wizards, but I know a lot of others
did. Before we can do the iteration to remove the data DOM we will
inquire which xpaths are now in use and how we can provide a better way
to support the functionality they implement.
The most used xpath
Op 28-jun-2005, om 14:40 heeft Pierre van Rooden het volgende
geschreven:
action type=create
relation role=posrel
!-- set field pos form the posrel relation --
field name=pos{sum(//[EMAIL PROTECTED]'posrel' and
@lastitem='true']/[EMAIL PROTECTED]'pos'])+{$pos}}/field
What are the key technologies used?
The wizards make extensive use of xslt to transform xmls into web forms.
The
client-side of the wizards uses DHTML, javascript, and CSS for client-side
functionality. Java-libraries used include DOM and the MMBase query model.
The
Pierre van Rooden wrote:
Michiel Meeuwissen wrote:
Rincewind - Edit Wizzard 2.0 Project Document
What is 'Rincewind'?
Now, really. Go read some Terry Pratchett.
boring! ;-)
Well, the methodolgy as described here can also be used in MMBase, i.e.
through inclusion in the builder xmls or
I would like to see a generic javascript library which can validate
arbitrary fields. This library can then be used in editwizards, but also
in other HTML's.
check http://jakarta.apache.org/commons/validator/
The validator framework provides server-side validation as well as the
possibiliy to
bash-2.05b$ xmllint -valid project.xml l
project.xml:72: element formalpara: validity error : Element
formalpara content does not follow the DTD, expecting (title ,
indexterm* , para), got (title para para )
/formalpara
^
just like any xml that is edited by hand it
Kees Jongenburger wrote:
just like any xml that is edited by hand it is a nightmare.
Sorry, all formalpara tags should be section tags. Silly me.
At this point I don't care any more about technique. I just care about
how easy it is to use
and if there is a non xml based way of creating
Ok, to make it a bit easier: the project proposal in pdf format.
--
Pierre van Rooden
Mediapark, C 107 tel. +31 (0)35 6772815
Anything worth doing is worth overdoing.
project.pdf
Description: Adobe PDF document
___
Developers mailing list
An editwizard editor would be nice, yes. Would also take some time to
build though.
Perhaps there is someone out there willing to sponsor development of
such an editor?
I woud love to spend some time on it (if it's swing based that is)
___
Developers
Pierre van Rooden wrote:
Ok, to make it a bit easier: the project proposal in pdf format.
To make it even easier, and 'replyable'. Here a version in ASCII.
Rincewind - Edit Wizzard 2.0 Project Document
Pierre van Rooden
This software is OSI Certified Open Source Software. OSI Certified is
Pierre van Rooden wrote:
Rincewind - Edit Wizzard 2.0 Project Document
What is 'Rincewind'?
What is the purpose of this project?
Expanding the MMBase edit wizards with functionality that makes it easier
to
extend with custom scripts (server or client-side), and adding
13 matches
Mail list logo
