> Anyway, I guess it wouldn't hurt to have choice of the method > (property or parameter binding) as long as it didn't need bending > all the framework. But if someone would go on and implement this, I > believe that would be quite difficult to do so that it doesn't break > current Stripes-based code.
I think that in this case, Remi is right: keep it simple. Sometimes it's good to have more than one way to accomplish something, but in this case, I think there would be more harm than benefit. Some frameworks suffer from having too many different ways to do the same thing, and I think Stripes should avoid that route. As you said, there would be implementation issues. Also, things would come up such as: what happens if you have a property, a no-parameter event handler, and an overloaded one that accepts one parameter? Do you bind the property and call the no-parameter method, or call the one-parameter method? Then you need to add more complexity to resolve the ambiguity, and things become that much harder to maintain. Freddy ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Stripes-users mailing list Stripes-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/stripes-users
