GNUmed web clients

For threads on this see

• July 2010 choice of web frameworks
• July 2010 GNUmed web interface - technologies
• March 2010 GNUmed web interface.

Blog posting:

• http://gnumed.blogspot.com/2010/07/gnumed-web-client-demo-available.html

An original proof of concept was written by Syan Tan…

• download it here

Syan provides the following notes:

here it is at the moment .
The main things I found were:
  - configure the publisher handler from mod_python to a directory in apache2 configuration file.
  - start the ball rolling in login.html by calling the python script with
    <a script>.py/<a function name>?<function paramters, named
    exactly to match the function parameter names>
  - then do a function in <a script> of the form <a function>(request, param1, paranm2 ...)

request will be a request object , normally only useful as below. 

What's more useful is to import mod_python.session and 
use the default Session(request) constructor, and then use a session
object to load and store values between pages.

The function is expected to return a string which is a html page.
You can write html pages as templates with %s parameters to fill
in with dynamic output, using StringIO as an intermediate,
and then return the resulting string.

Any further navigation within hrefs and redirect html pages , just
need to refer to a function name within the original named python
script. I haven't tried navigating down below the script name
using ../  to call another script file, but it would probably work.