> Again, as if this hasn't been reiterated enough times. simplicity is > key. People like views.properties, why not keep them happy? It's like > the propertytag debate. People like the idiosyncratic way it worked, > why modify it just to enforce some arbitrary perception of correctness?
s/people/webwork developers I have had plenty of discussions with lots of people in #java about the property tag and it's pretty much universal that the current behaviour is wierd at best. (Like the <ww:property><foo:bar/></ww:property> instance: does that print or just push? That depends on the output of <foo:bar/>!). And again, I am not for changing anything, I want to add a logical and simple system, one that will fix the dreaded issue in jira about wanting <ww:property value="foo"/> to push, because doing that isn't possible at all with the current tags but would be trivial with two tags ww:value and ww:render (or push/print, or use/out or whatever name you prefer). > I really do like Maurice's approach of keeping things as simple as > possible. I likewise feel that everyone should develop an instant > knee-jerk reaction AGAINST adding more configuration options for users > to be befuddled by, and that it should be viewed as a distasteful last > resort. Remind me again who is suggesting we replace views.properties with the xml file. // Anders Hovmöller ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
