Re: Vote: Tapestry 5.3 beta
François Facon: +1 (non-binding) we start the migration of our corporate mobile solution to 5.3. Regards 2011/8/19 Taha Hafeez : > Taha Hafeez: +1 (non-binding) > > We are already in the process of migrating one of our applications to 5.3+ > > On Fri, Aug 19, 2011 at 12:55 AM, Thiago H. de Paula Figueiredo > wrote: >> Thiago H. de Paula Figueiredo: +! (binding) >> >> -- >> Thiago H. de Paula Figueiredo >> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and >> instructor >> Owner, Ars Machina Tecnologia da Informação Ltda. >> Consultor, desenvolvedor e instrutor em Java, Tapestry e Hibernate >> http://www.arsmachina.com.br >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: dev-h...@tapestry.apache.org >> >> > > > > -- > Regards > > Taha Hafeez Siddiqi (tawus) > http://tawus.wordpress.com > > - > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Vote: Tapestry 5.3 beta
Igor Drobiazko: +1 (binding) On Thu, Aug 18, 2011 at 7:04 PM, Howard Lewis Ship wrote: > It seems like we're ready to switch to a beta release. -- Best regards, Igor Drobiazko http://tapestry5.de
Re: Vote: Tapestry 5.3 beta
Ulrich Stärk: +1 (binding) On 18.08.2011 19:04, Howard Lewis Ship wrote: > It seems like we're ready to switch to a beta release. This would > indicate that we should shift focus from major disruptive changes > towards filling in gaps and fixing bugs (and documenting) with the > goal being a final release. > > Three day vote, lazy consensus. > > Howard M. Lewis Ship: +1 (binding) > > > I really think we'll have a short beta/rc! > - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Vote: Tapestry 5.3 beta
Bob Harner: +1 (non-binding) On Aug 19, 2011 5:49 AM, "Ulrich Stärk" wrote: > Ulrich Stärk: +1 (binding) > > On 18.08.2011 19:04, Howard Lewis Ship wrote: >> It seems like we're ready to switch to a beta release. This would >> indicate that we should shift focus from major disruptive changes >> towards filling in gaps and fixing bugs (and documenting) with the >> goal being a final release. >> >> Three day vote, lazy consensus. >> >> Howard M. Lewis Ship: +1 (binding) >> >> >> I really think we'll have a short beta/rc! >> > > - > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org >
Re: Vote: Tapestry 5.3 beta
Ben Dotte: +1 (non-binding) On Fri, Aug 19, 2011 at 6:01 AM, Bob Harner wrote: > Bob Harner: +1 (non-binding) > On Aug 19, 2011 5:49 AM, "Ulrich Stärk" wrote: > > Ulrich Stärk: +1 (binding) > > > > On 18.08.2011 19:04, Howard Lewis Ship wrote: > >> It seems like we're ready to switch to a beta release. This would > >> indicate that we should shift focus from major disruptive changes > >> towards filling in gaps and fixing bugs (and documenting) with the > >> goal being a final release. > >> > >> Three day vote, lazy consensus. > >> > >> Howard M. Lewis Ship: +1 (binding) > >> > >> > >> I really think we'll have a short beta/rc! > >> > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: dev-h...@tapestry.apache.org > > >
Palette and Checklist don't use contributed value encoder?
Does anyone know why half of the built-in Tapestry 5 components that take an "encoder" parameter are NOT set up to be able to use a "contributed" ValueEncoder (that is, one configured with contributeValueEncoderSource() in AppModule class)? The following components nicely allow the "encoder" parameter to be optional: Grid, GridRows, Loop, Select, Upload: But the following make you provide the encoder parameter (even if you have a ValueEncoder configured in your AppModule for the appropriate type): AjaxFormLoop, Palette, Checklist, Hidden, RadioGroup Maybe there's some subtle reason for this? - To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
Re: Palette and Checklist don't use contributed value encoder?
On Aug 19, 2011, at 8/198:56 PM , Bob Harner wrote:
> Does anyone know why half of the built-in Tapestry 5 components that
> take an "encoder" parameter are NOT set up to be able to use a
> "contributed" ValueEncoder (that is, one configured with
> contributeValueEncoderSource() in AppModule class)?
>
> The following components nicely allow the "encoder" parameter to be optional:
>
>Grid, GridRows, Loop, Select, Upload:
>
> But the following make you provide the encoder parameter (even if you
> have a ValueEncoder configured in your AppModule for the appropriate
> type):
>
>AjaxFormLoop, Palette, Checklist, Hidden, RadioGroup
>
Not entirely following... at least in trunk:
From AjaxFormLoop:
ValueEncoder defaultEncoder()
{
return defaultProvider.defaultValueEncoder("value", resources);
}
Hidden:
ValueEncoder defaultEncoder()
{
return defaultProvider.defaultValueEncoder("value", resources);
}
RadioGroup:
final ValueEncoder defaultEncoder()
{
return defaultProvider.defaultValueEncoder("value", resources);
}
And, for the record, Grid (to demonstrate the fact that Grid is default the
same way):
ValueEncoder defaultEncoder()
{
return defaultsProvider.defaultValueEncoder("row", resources);
}
But it does appear that Palette and Checklist are not proving a default
encoder, and the why behind that I don't know.
Robert
> Maybe there's some subtle reason for this?
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: dev-h...@tapestry.apache.org
>
-
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
