Quoting David Guest <[EMAIL PROTECTED]>:
> > > I had a bit of time over the Xmas break, and did the Ruby on Rails > tutorial (dead easy Windows tute at onlamp) and then started on the Ajax > on Rails. The upshot of all this is that we will have to rethink about > the way we handle web data and interactions and hence all medical > communications. I now know what you, Tim and Horst were referring to > earlier. Unfortunately only a few others do. I agree. I have also been looking at Rails and it's python equivalents, the breakthrough seems to be auto-generating SQL from Python/Ruby template classes. >From there stems their limitation, "portable SQL" (read: we stick only to the MySQL featureset as lowest-common-denominator), which is an unacceptable hobbling from the gnumed perspective. Currently I'm looking at going the the other way (defining the schema in postgres and then auto-generating python objects) as a way out of the current gnumed woes. Also, I have finally found a coherent exposition of the google select system: http://www.dcs.lancs.ac.uk/~grill/mgbox/ (people are running around calling this technique "Ajax" like it's God's gift, IMHO we should call it "Javascript finally doing something useful") It means a usable web-based EHR is now on the horizon, although I'm not sure we've arrived yet. Ian _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
