> It always sounds easier after you succeeded for the first time. ;)
That's true - and I think I just had one of these nice moments when you begin
to understand the way sth works :-)
> > But I don't get how to loop over the IDs. Something like "@Inject Block
> > mywidget" is ok - and I may return the block to the delegate... but how
> > to retrieve the needed block by id? (At the moment it looks like I have
> > to
> > @Inject every widget and then return them by a switch statement? ...)
>
> That's exactly what I've been thinking. I don't know if there's a better
> way to do that. That's the not nice part of the "static structure, dynamic
> behaviour" philosophy.
Thank you so much.. it works! :-)
I will write down a short howto in the wiki tomorrow. (is the wiki open to
everyone?)
But you are right... the code really looks not that nice compared to the
elegance tapestry is providing in other areas. Maybe that's the reason why I
was under the impression that there has to be another way.
Think about the nice ioc functionality of dropping in new components - we
loose this for that page. But it would make a lot of sense to bundle new
widgets in jar files....
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
