Learn to use XForms, DB2 pureXML, and Ruby together to create Web applications. Discover the individual strengths of each technology and learn how to integrate them collectively. In Part 3 of the four-part series, you will develop a form for nurses to go back and edit patient data, and you'll also learn what you need to do in Ruby to make this happen.
Comments
mark.t replied ago:
Sorry to say this but syntax is ugly. How do you code big apps with Ruby? The use of modules as opposed to applying design patterns is wrong.
killerweb replied ago:
Take it from someone who builds software for life sciences, that might as well have been a recipe application. If the author only knew how complicated patient records are, he would have not shown that as an example. Plus no way in hell would you use a DL framework where the strictness of data is needed. DLs have their place in the world, but it's not in the medical industry.
Mark Thomas replied ago:
@killerweb:
It *was* a recipe application. It was a recipe on how to string together XForms, the XML DB, and Rails. No matter what the subject, these kind of things are intentionally oversimplified. Your reaction seems to be a bit knee-jerk. You seem to be scared that *gasp* someone might actually decide to build software for "life sciences" using Rails, threatening your static-language-building medical software business.
killerweb replied ago:
Yes Mark I'm scared someone will try to sell "none-static-language-building" as a selling point and put me out of business, geez. As far as the "oversimplified" example is concerned, if that looks over oversimplified from a technology standpoint, I would feel sorry for someone that tries to build one more complicated based on what's shown. That is as complicated as it gets from a technology choice even with the DL used.
Voters For This Link (5)
Voters Against This Link (3)