Am I missing something here? I'm currently working on a system that allows the user to edit unlimited numbers of documents all shown at the same time on the same screen something akin to a spreadsheet. Obviously this is something Domino doesn't do (i'm using R5, but I suspect it's no different in R6).
The solution I came up with was a Ls Agent. the user clicked a link that just opens the agent. The agent can tell this is a GET request so renders the page for you in full html. When you "submit", the browser merely POSTs back all the name/value pairs to the same agent. The agent then validates the data.
if it's not looking god, then the agent merely redraws the screen again filling in the values you posted into the INPUT fields and an appropriate error message. So the user gets back all the info they typed in previously, including the error messages and nothing has been saved to any documents.
if the submit was valid, then the agent merely creates a document (or in my case many!) and pushes all the (relevant) fields onto the document.
Now admittedly, this is a serious amount a code. And it's taken me a while to write it. but in the proces, I've written quite a good framework of functions that can be placed in a script library and you merely call them from another agent. Each agent then only needs to do the html and call common functions for the value of the input fields (who are blank for a GET or filled in with anything POSTed).
And my agent does more in that the agent actually runs with a parent unid as a url parameter and displays back the details of the children documents as a spreadsheet and on submit it updates them accordingly cutting down on needless saves.
Personally, I write a hell of a lot of html as the Domino html sucks, so I love writing web agents. This has to be the slickest way I've seen to allow you to edit 20+ documents at the same on the same web page with only one post to a domino server - and I can't see any reason why it can't be used to solve the accessibility issues you have...?
Am I missing something here? I'm currently working on a system that allows the user to edit unlimited numbers of documents all shown at the same time on the same screen something akin to a spreadsheet. Obviously this is something Domino doesn't do (i'm using R5, but I suspect it's no different in R6).
The solution I came up with was a Ls Agent. the user clicked a link that just opens the agent. The agent can tell this is a GET request so renders the page for you in full html. When you "submit", the browser merely POSTs back all the name/value pairs to the same agent. The agent then validates the data.
if it's not looking god, then the agent merely redraws the screen again filling in the values you posted into the INPUT fields and an appropriate error message. So the user gets back all the info they typed in previously, including the error messages and nothing has been saved to any documents.
if the submit was valid, then the agent merely creates a document (or in my case many!) and pushes all the (relevant) fields onto the document.
Now admittedly, this is a serious amount a code. And it's taken me a while to write it. but in the proces, I've written quite a good framework of functions that can be placed in a script library and you merely call them from another agent. Each agent then only needs to do the html and call common functions for the value of the input fields (who are blank for a GET or filled in with anything POSTed).
And my agent does more in that the agent actually runs with a parent unid as a url parameter and displays back the details of the children documents as a spreadsheet and on submit it updates them accordingly cutting down on needless saves.
Personally, I write a hell of a lot of html as the Domino html sucks, so I love writing web agents. This has to be the slickest way I've seen to allow you to edit 20+ documents at the same on the same web page with only one post to a domino server - and I can't see any reason why it can't be used to solve the accessibility issues you have...?