Dan Adams <dan <at> ifactory.com> writes:
>
> There are two situations we hit often in our applications:
> - disabling sorting for one specific column because it doesn't have a
corresponding db column
> - not allowing sorting by any of the columns because the data is sorted
explicitly
>
> In T4 with contrib:Table you could specify a list of colums like
"foo,!bar,baz" and then "bar" wouldn't be
> sorted. How have others handled this in T5?
>
> Dan Adams
> Senior Software Engineer
> Interactive Factory
> p: 617.235.5857
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe <at> tapestry.apache.org
> For additional commands, e-mail: users-help <at> tapestry.apache.org
>
>
Hello Dan!
I think you cannot do that using actual Grid parameters, but you can use the
BeanModel API to disable sorting on specific properties, maybe a good place to
make it is the setupRender phase method:
private BeanModel _model;
...
void setupRender()
{
_model.get("name").sortable(false);
}
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
