at is described above. I'm not sure that's
really a problem because you can just just the context parm instead.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/PageLink-page-Parameter-tp4822711p4830269.html
Sent from the Tapestry - User mailing list archiv
So I wrote a link component this morning and put it here.
https://github.com/trsvax/tapestry-trsvax
It's a bit rough but it's interesting to play with. First changing the
page parameter to accept a component seems much better, in fact I
think I'm going to drop support for string. I'm also thinkin
I like it also but I believe this is already (for the most part) the
case by default if you leave off the context. Try
public class About
{
@InjectPage
private Contact contactPage;
@InjectPage
private About aboutPage;
private String value;
+1
On 21/09/2011, at 7:56 AM, Thiago H. de Paula Figueiredo wrote:
> On Tue, 20 Sep 2011 11:14:03 -0300, Reinhold Gruber
> wrote:
>
>> Hi,
>
> Hi!
>
>> I would found it rather usefull if if the page Parameter of PageLink
>> would also accept a page-class or an injected and configured page
>>
On Tue, 20 Sep 2011 11:14:03 -0300, Reinhold Gruber
wrote:
Hi,
Hi!
I would found it rather usefull if if the page Parameter of PageLink
would also accept a page-class or an injected and configured page
instance (so that the activation context could be calculated from
onPassivate()).
I l
Hi,
I would found it rather usefull if if the page Parameter of PageLink
would also accept a page-class or an injected and configured page
instance (so that the activation context could be calculated from
onPassivate()).
Regards,
Reinhold
