Hello,
just two sad thoughts on GridView's custom paging support, the first one
rather general and second one rather specific.
First one: I really miss the DataGrid custom paging support with
AllowCustomPaging and VirtualCount. The new declarative model with
ObjectDataSource is much worse! - the amount of "words" you have to type is
comparable (few methods in C# vs declarative binding with ObjectDataSource),
however the static typing is completely gone! The remark is a general one:
we all see the direction of declarative programming, XAML etc. but mentally
I feel like we almost back to the old VB6 era whre you have to write a
statement and pray it will not explode in runtime. This is what
ObjectDataSource (and XAML) is - you set a bunch of strings and pray, after
several runtime bangs it will finally hopefully work but where is this great
strong typing? All gone forever! Someone once told me that in fact the
compiler COULD check the type of an underlying object but neither it does it
now nor it will probably do it in future. You type "RetrievePage" into
"SelectMethod" and everyting seems ok but then it bangs in runtime because
you've typed "RetrivePage" or "RetrievePAge". After dozen of
ObjectDataSources I am fed up with them!
Second one: ObjectDataSource is usable, paging and sorting both work
(after some painful runtime crashes of course) but how do you specify the
default sort order? Not inside the "SelectMethod" but outside of it so that
the first call passes it to the "SelectMethod"? I have no idea and would
welcome someone who gives me a helpful hand. The first bind to the method
specified as "SelectMethod" is too late for defining the default sort order,
the sort order passed to this method is already set to string.Empty. Taking
the clarity of the business layer into account I do not like the obvious
solution to set the default sort oder inside the "SelectMethod" - what if
there are several clients that would like to have different default sort
orders?
Thanks in advance,
Wiktor Zychla
|
Similar Threads
