Orthogonality and predictability are needed, I guess.
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Scott Russell wrote:
Ok, I added my vote to the bug report.
The suggestions you, Eric and Jeff suggested are good workarounds, and easy to
implement. In fact, I'll probably use one of those to get working in the
meantime.
But this is one of those areas where one naively uses Tapestry functionality
only to be tripped up by quirky unpredicted behaviour that runs counter to
expectations. The more I use Tapestry the more of these quirks I find, and it
is these which really slow down development time because one spends ages
debugging application problems, only to find it was caused by unexpected
framework behaviour. This is not to complain or to imply any disillusionment
(because I'm in no hurry to switch to JSF or Shale), but rather that we
should aim for a clean predictable framework free of these sorts of quirks.
regards,
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
