> For debate: should step #3 apply to scalar properties > (boolean, int, double, etc.) or just to object > properties?
For consistency if nothing else, also apply this to scalars. > For debate: Tapestry can now automate the process of > checking for required parameters ... that is, it can > enforce that a binding exists and that the binding's > value is non-null ... or should this check stay in > component code? I would _LOVE_ for Tapestry to automatically apply the required parameter check at render time rather than page loading time. We have had to stop using required="yes" on all our 'reusable' components despite our usage of those components ensuring that they do in fact have the required bindings. If Tapestry were to check these things at render time (and render time only), we could put the required setting back, and gain a whole lot more confidence in our code. Do it, do it do it! In all seriousness, anything that can be done to make initial development of components easier is a great idea - if it means that in order to get more performance out of an app you've gotta do a little more coding, so be it - as long as there are controls/hooks that allow optimisation. > So ... the final question is: when? 2.0.2, 2.0.3 ... or > should this wait for the 2.1 series? 2.1. Even though there aren't any other changes planned, I'd love to see the magnitude of the version increment reflect the magnitude of the change, and this is not a 0.0.1 change! Richard _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
