catmat wrote:
Tim Churches wrote:
Detecting whether clobbering will take place, or whether the use of teh browser navigation is innocuous, takes quite a lot of logic code for each app page. Building robust Web apps is, we've found, a lot more complex than building robust GUI apps.this app is a lot simpler, so it only needs one page for demographic insert/update ( and by initiating
Tim C
a blank demographic form with a unused sequence number, then checking the number is in
the identity table, you can deal with the back button).
The clinical update is only on one page (albeit, messily complex) , so the hacky solution there was to
popup a browser window without navigation buttons and only exit points being the submit button
and window frame close button. What's done in this window isn't picked up by the window opener,
the demographics. There is only one back state and that's from the non-updating printable summary page,
and once the form is submitted , the window is closed to prevent any backing up.
This is done by making it's post-submit page a page with the only content of javascript "window.close()".
Yup, all of that sounds like a reasonable strategy.
I thought oscar was being unnecessarily complex by using popups, but I can see why now.
Yes, but my response on trying is was "Ewww, what are all these popup up windows doing, cluttering up my screen? Particularly when they are not modal, so are easily lost behind other windows if you are simultaneously using other apps. Not ideal, but on the other hand, OSCAR is being used in practice, successfully, so it shows that purism is not everything and some compromises are useful.
Tim C
_______________________________________________ Gnumed-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnumed-devel
