Is there anyone who implemented ClientAPI paging in DNN with a datagrid? Trying to accomplish something as they have made over att CS (http://communityserver.org/blogs/default.aspx) look at the right hand webparts "Most Comments" and "Most Viewed" and use the paging to see the AJAX feature.

/Rob

After thinking on this a little more it reminded me of a simple control I was meaning to write that is similar.  I was considering writing a control that does the min/max capability.  Where the contents of the maximized control are not initially rendered until the user expands it...   This would probably be where I would start.  Once I finished that I would move on to a little more complicated control that does the page numbers...  in essence they are the same thing, only that the paging control has more than one "expand" button, that happens to collapse all other expand buttons when clicked.  Wheter or not I would make one control out of it or two is another question...

For me I need to decide if I should tackle the DNNMenu or knock out some of these simple controls first...  I am currently spending way too much time on the ASP.NET 2.0 Menu Navigation provider...

After spending some time on this today, looking at several AJAX implementations I’m fairly up to date what to do to make this work through ClientAPI, but unexpectedly (it easily becomes complicated as you one second tries to manipulate the DataGrid control and in the next poke around in the ClientAPI) I seem unable to find a vital feature as I’m unsure if it’s supported by the ClientAPI alone. 

I have the following question to you Jon; You have apparently thought about making hide/show working through dynamically fetching UI components. #1 Question is, how? :o)

I have made this a long time ago (Pre .NET) by rendering each required component through a common .asp page which I loaded in a hidden iframe, As this was done I searched for the node ID I was to replace within the freshly loaded iframe and performed a copy between the nodes innerHTML.

However, I’m not sure if this is allowed today depending on the .NET page v13wstat3. I remember reading here in the blogs and on the asp.net forum about the v13wstat3 protection implemented in DNN to prevent page manipulations and hijacked postbacks. (Maybe this is just made through some cookie magic and we all go free but I haven’t looked in to this so I’m not sure)

Dynamical adding and removing of some chunks of UI is required as you indicated above Jon in order to update the grid after some paging is performed. For me the question is what approach to take?

Naturally it required more time than what I hoped for just to figure the basics out but hey! :)

Cheers,
/Rob