hey there,
last friday (before codefreeze) I checked in the new lookupWidget and the getWidget to getChild rename...
the first makes every widget a natural starting point for widget-tree navigation using a path-like expression (even including construct like ../)
the latter was based on some recent discussion that indicated the higher semantical value of getChild over getWidget, and accorded better with the getParent counterpart...
this last change however has quite some impact on existing installations: current cforms users will need to run through their code to search/replace getWidget to getChild (or lookupChild in fact)
out of convenience to our users we might do slightly more though - clear documentation on the woody2cforms page
and then apply some more gentle phasing out approach of deprecation by - re-introduce the getwidget, but make it deprecated in which case we should decide if the implementation should
[ ] just work [ ] log a warning and keep on working [X] fail with some RTE
If we have decided to change the API (and I'm +1 for this one), then let's do it quick, and fail hard to ease migration of existing applications. There's nothing worse than something that used to work but no more does with no particular reason. Sometimes, the dynamic nature of JavaScript doesn't help...
We'll remove the getWidget() method completely later.
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }
