On Mon, Jun 29, 2009 at 4:47 PM, Piero Sartini <li...@pierosartini.de>wrote:
> > Is @Property so hard or awful? > > No, it isn't. But for me these kind of objects have temporary character. I > really don't like them to pollute my page classes. And to me, that's exactly what page classes are for. > > > Maybe its just me, but if I need a property just to iterate over a list it > feels like it could be optimized.... tapestry is reducing needed code > whereever possible. In this particular case I think its hard to understand > why > it breaks with this rule. Especially because var: is available and iterates > over the object fine: callit .toString() method if displayed. > > But accessing the properties of an object that is there fails... its just > something I would not have expected. > > Piero > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Howard M. Lewis Ship Creator of Apache Tapestry Director of Open Source Technology at Formos
