Many htnaks for your answers, though they don't give me a lot of hope ! ;-)
Jean-Baptiste Quenot :
Then why is it required ?* David Verdin:
1- In "action" widgets, what is exactly the "action-command"
attribute?
AFAICT its value is not meaningful.
Why does it allow you to add or remove row of a repeater widget when used in a "repeater-action" tag ?
I read this already. I didn't understand it. For example, I tried to include a javascript code inside the <on-action> tag of an <fd:action> widget. It is supposed to make the form being reloaded when you click. It doesn't. I couldn't find any explication for this.
2- More generally, how can I make a script happen on some events on
widgets ? For example, in a simple HTML form, I use the "onClick"
attribute of a button to make a javascript to happen. I don't get how
to do the same with Cforms widgets.
It is documented in the following pages:
http://cocoon.apache.org/2.1/userdocs/forms/widget_submit.html http://cocoon.apache.org/2.1/userdocs/forms/widget_field.html http://cocoon.apache.org/2.1/userdocs/forms/xslt.html
Sure, but if I use JX to update my form, I have also to update the binding file. If not, the values typed in the new widget I would insert inside my form wouldn't be included in the final XML document.3- Is everything in the cocoon framework compatible ? Is it possible
to make the binding framework work alongside JXtemplategenerator ? If I
use repeaters, what happens to the binding file when I add a row ?
The binding occurs before or after displaying a form, thus it has no correlation with displaying the form template. The form template is for user interaction, whereas binding is used to load from or save to an XML document.
Well. I'm not sure. In the API, it seems difficult to find what a method do exactly.4- Where can I find the list of cocoon javascript functions and
objects ? Is it the API ? If so, is there something else, because most
of the time, the API is poorly documented ?
Exactly, you have to read the API documentation.
I'll try, but hope I won't let my sanity in the process...
Well. I hoped it would be possible to avoid implementing Java classes.I feel that Cocoon has a very big potential, but it seems impossible
for me to make it work properly.
Cocoon is open-source: do not hesitate to take a look inside to the forms stylesheets, the java classes, and so on. Everything can be customized and adapted to taste.
I think that what Cocoon documentation misses is a strait document explaining what every function, class, or stylesheet do. And also a map to explain what interactions are done between these functions. Which functions are cocoon specific and which are generic. Also, I think that each line of the samples could be commented, to explain what these lines are supposed to do. It would avoid long hours of search in the cocoon tree jungle.
I'd like a pony for christmas also Santa, please.
OK, well... Hope I can achieve something then.
Cheers,
Desparated David
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
