... and many thanks to Igor for fixing those two checklist label issues!
Bob Harner
On Nov 8, 2011 1:47 AM, "Josh Canfield" wrote:
> > That would be really cool, but is it possible to do?
> It's harder than making Loop generic because you actually need the
> type information within the class.
>
> That would be really cool, but is it possible to do?
It's harder than making Loop generic because you actually need the
type information within the class.
Looking at it, it might be better to grab the generic info from the
parameter binding itself. That is available at runtime, but not
currently
That would be really cool, but is it possible to do?
On Mon, Nov 7, 2011 at 12:36 PM, Josh Canfield wrote:
>>> 3) This component takes an "encoder" parameter but does not support a>>
>>> ValueEncoder configured to be provided automatically by Tapestry.
> It would be nice to migrate all of the co
>> 3) This component takes an "encoder" parameter but does not support a>>
>> ValueEncoder configured to be provided automatically by Tapestry.
It would be nice to migrate all of the collection based components to
a generic form.
With the generic information you could also pick the right value en
On Mon, Nov 7, 2011 at 4:12 AM, Igor Drobiazko wrote:
> hi,
>
> On Sun, Nov 6, 2011 at 5:24 PM, Bob Harner wrote:
>
>> Hi everybody,
>>
>> I've been meaning to bring this up for a while now. The new-for-5.3
>> Checklist component has -- for me -- a couple of minor annoyances:
>>
>> 1) The label f
hi,
On Sun, Nov 6, 2011 at 5:24 PM, Bob Harner wrote:
> Hi everybody,
>
> I've been meaning to bring this up for a while now. The new-for-5.3
> Checklist component has -- for me -- a couple of minor annoyances:
>
> 1) The label for each checkbox is positioned *before* (that is, to the
> left of)
I'll take care of it.
On Sun, Nov 6, 2011 at 5:24 PM, Bob Harner wrote:
> Hi everybody,
>
> I've been meaning to bring this up for a while now. The new-for-5.3
> Checklist component has -- for me -- a couple of minor annoyances:
>
> 1) The label for each checkbox is positioned *before* (that is,
Hi everybody,
I've been meaning to bring this up for a while now. The new-for-5.3
Checklist component has -- for me -- a couple of minor annoyances:
1) The label for each checkbox is positioned *before* (that is, to the
left of) the checkbox. I think it is much more common to want the
label *afte
