[Bese-devel] component tree

Lou Vanek vanek at acd.net
Sat Jun 10 15:03:43 UTC 2006


[bump]

...
Next question. I'm working on the make-new-callback thing now, because it doesn't behave very well in some situations (multiple forms, which have names with the same fields, on a page, and 
when you want to always run some code when a form is submitted, for use with checkboxes and multi-select inputs)... but I am running into some serious terminology confusion.

Could somebody give me a hint on the meaning of the _s and _f hidden inputs that are added to <ucw:forms, and related to those, what exactly is the role of the make-new-action call in <ucw:form?

Also, is there something I could read to get some more clue on what the 'component tree' is? I actually thought it was just a stack... but some comments in the ucw sources are telling me it is 
an actual *tree*. How does it work, where is it stored, and when exactly are components copied/re-created?

Thanks,
Marijn




More information about the bese-devel mailing list