Horst Herb wrote: > After toying around during sleepless nights between call-outs I think I have > found the future platform for an EHR system: > > http://rubyonrails.org/
Kuangie came to the same conclusion, I believe. > > It solves so many problems we had in the past: > - far less complexity in code > - much faster development > - reduces complexity of database interaction by at least one order of > magnitude > - feature rich Ajax UI elements (server-side autocompletion text boxes, > drag'n'droppable lists, in-place editing, image manipulation ...) Yup. However, those whose opinions I trust tell me that if you want to use one of these new Web app frameworks, then either Turbogears (see http://www.turbogears.org/ ) or Django (see http://www.djangoproject.com/ ) are better choices that RoR, not just because both are written in and programmed in Python, but because both allow more flexibility with respect to back-end schemas etc. Guido van Rossum, the Python Benign Dictator for Life, has given Django his personal thumbs up, but both are good. For the present we are sticking with a homegrown Python Web framework - Albatross (see http://www.object-craft.com.au/projects/albatross/ ) which is somewhat lower level than any of the above frameworks but is specifically designed for highly-stateful Web apps and allows complete flexibility. But the more recent frameworks are definitely worth using - we plan some things with Django in 2007. Tim C _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
