arti schrieb:
> Hi,
>
> My intention is not to leave the behavior to users. Sorting was just an
> example. Primarily because my component should be ready-to-use.
>
> My component must define and implement some core behaviour. For
> custom/additional behaviour it can provide some hooks (like
> callback-methods)as you suggested.
>
> My question is, where should the component implement it's core behaviour
> (which is not dependent on application logic)?
>
you could enforce an extended data model interface on your table logic
if needed.
In case of a raw data table this makes sense because then you can push
the sorting and pagination down to the database itself or any data
provider, where in my opinion it actually belongs to.
I dont think it is a good idea to provide the entire sorting on
component level, because ram is somewhat limited.
