if I click on the column header of an XPage’s view panel the entire page is reloaded to resort the view. Question is: is there a way to tell this function to do a partial refresh of the view data only rather than a full refresh?
Subject: Not sure but the docs say no…
“When users toggle categories, the application XPage is submitted to the server, and the XPage reloads.”
I assume this would hold true for clicking column headers to sort.
Depending on your needs, you could try this since Dojo is built in to 8.5:
http://archive.dojotoolkit.org/nightly/dojotoolkit/dojox/data/demos/demo_DataDemoTable.html
I haven’t found the Dojo documentation very easy to figure out but if you can find examples it’s not too bad to use.
It seems like all the built-in controls are very server oriented, not much Web 2.0 yet (except for the Ajax enablement parts).
Ken
Subject: I’ll have to try this…
…but only after I figured out how to bring dojo into Xpages code. Problem is, I’ve got a good idea of how to omplement dojo attributes into standard html or into classic Domino web apps. But where would I enter my dojo attributes in an XPage’s source code?
Obviously there already IS some dojo stuff being mixed into the resulting code after an XPages has been rendered. Problem is you don’t see it in the XPage’s code…
Guess this question could make it into a new topic in this forum 
Thanks anyway for the suggestion!
Subject: It’s pretty simple.
You can mix regular XML/HTML markup in the source code directly. Look at the results of a page in your browser so you can see what’s loaded already, then add the the various dojo.require statements, etc.
I think having a clear idea in your mind what parts of the Xpage are server generated jsp code (anything with a xsp:control tag and most / all? of what you drag and drop onto the design pane) vs. what’s XML run through an XSLT translation into HTML then out to your browser.
You can simply mix in whatever native HTML markup in the Source pane with the xsp: tags, etc. I’ve been finding for lots of Web 2.0 type stuff you really need to be hand coding those elements, possibly in conjunction with the resultant Dojo code that some of the xsp: tags create. I’ve been using some dojo.query methods with client side script to access the various page elements that are created by Panel, Computed Fields, Labels, etc. all of which are xsp: tags in source.
I’ve suggested that someone document the lifecycle of various common web actions i.e. create a new Domino Document and save it. That way we could see where / when the server-side elements get created, rendered, etc.
Also, it would be useful to have good documentation on all the xsp: tags and what their properties are at the server AND client side so we can tweak them on the fly with client side code to improve the user experience and save on server hits.
Think of Domino 8.5 as sort of a Web 1.5 environment.
I’ll try to post some sample code for you tonight.
Ken
Subject: Thanks for your input…
I’ll have a closer look into the topic asap.
Since most XPage controls are AJAX enabled already I somehow had expected that resortable columns would have been another ideal playground for that technology; most probably nobody thought of that. Too bad.
I totally agree with you that documentation on those and related topics is not at all adequate at least if this is the first that someone gets in touch with those technologies.