There are a lot of libraries for JavaScript and some that I've used have gone out of favor. The one that seems to be the winner is jQuery. It hides all the browser differences, so you as long as you stick to the jQuery interface to the DOM, you can blissfully ignore the quirks of IE and other browsers. There are lots and lots of packages to extend it, so that someone else has probably done whatever you need, such as talking to a MySQL database. The forums also seem pretty active. I recommend JavaScript and jQuery on the browser side.
I second Owen's recommendation of node.js on the server side. Like jQuery, it has tons of libraries. What makes node.js relatively unique is that all IO calls are non-blocking, using callbacks instead. It takes a while to get used to the new programming style, but then your server code is never unavailable because it is waiting for a disk or database operation to finish. There are good books devoted to both of these libraries. --Barry On Jul 2, 2013, at 10:01 AM, Gary Schiltz <[email protected]> wrote: > Also a very good point. Sometimes it's good to hop down from one's high horse > into the muck, and in the words of a redneck comedian whose name escapes me > now, simply "git 'er done". For every time there is a season, a time for cool > new stuff, and a time for LAMP :-) The situation may indeed call for the > latter (e.g. OpenEMR, which is PHP based). If I go with the latter, perhaps I > can bug you (and not the list) with PHP questions. > > Keeping it real, > Gary > > On Jul 2, 2013, at 10:03 AM, Robert J. Cordingley <[email protected]> > wrote: > >> In the interests of the medical clinic I wonder what packages are already >> out there that lead or support standards in EMR and for a successful >> project how one would best align one's goals with theirs? >> Robert C >> >> On 7/2/13 8:39 AM, Gary Schiltz wrote: >>> Point well taken about esoteric and cool versus pragmatic and well worn. >>> The most certain route in software, like in most undertakings, is usually >>> the familiar. The problem with the familiar is that many on the list, >>> including those of us who are ourselves well worn (at least worn), are >>> enamored with (might I go as far as to say addicted?) to the cool and >>> esoteric, whether it be software tech, complexity science, philosophy, >>> politics... So, I'm not just looking for a solution, I'm looking for a fix >>> :-) However, I was honest with my stakeholders and let them know that I'm >>> being a bit selfish, in that I'm not doing this not just for them, but for >>> me, using it as a justification for spending the time to learn some new >>> stuff. The easiest implementation would likely be a traditional two-tier >>> client server system, with the GUI and application logic done with Visual >>> Basic talking to a MySQL server. Nothing wrong with that, maybe I'll even >>> consider it when I grow! >>> up :-) >>> >>> ;; Gary >>> >>> On Jul 1, 2013, at 11:20 PM, Robert J. Cordingley >>> <[email protected]> >>> wrote: >>> >>> >>>> Then you might consider who's going to maintain it when your not available >>>> and what level of skill may be needed. Esoteric and cool is... well >>>> esoteric and cool. Pragmatic and well worn and well known might lead you >>>> to consider more mundane but well used tools especially on the server side >>>> like PHP and MySQL and perhaps WordPress and the thousands of themes and >>>> plugins. Many WP themes are responsive/mobile friendly right out of the >>>> box saving tons of work - some premium some free. >>>> >>>> Thanks >>>> Robert C >>>> > > ============================================================ > FRIAM Applied Complexity Group listserv > Meets Fridays 9a-11:30 at cafe at St. John's College > to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com
============================================================ FRIAM Applied Complexity Group listserv Meets Fridays 9a-11:30 at cafe at St. John's College to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com
