Hi Ian, As I said before: we build web apps because we are web developers. That doesn't mean that web oriented is better than desktop oriented, it depends on the kind of tool you are building.
For an editor, maybe desktop is ok. But if you want an editor on the cloud, is ok too (http://phpanywhere.net/). For shared repositores, I think web-based ans with web services (SOAP or REST) is mandatory. I don't think this discussion about web based vs desktop is in the right direction, I prefer to pay atention to our tool chain, and see what approach is best for each link, e.g.: we could have a perfectly integrated ecosystem with the best of both approaches: archetype editor: desktop based (GUI) template editor: desktop based artefact repository: web based EHR backend: desktop based EHR frontend: web based I think our (GUI) template editor will be opensourced soon. I'll let you know. -- Kind regards, Ing. Pablo Pazos Guti?rrez LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez Blog: http://informatica-medica.blogspot.com/ Twitter: http://twitter.com/ppazos > From: Ian.McNicoll at oceaninformatics.com > Date: Sun, 11 Sep 2011 09:38:05 +0100 > Subject: Re: openEHR Transition: Web-based tools? > To: lavanian at vsnl.net; openehr-technical at openehr.org > > Hi Dr Lavinian, > > That was what I had in mind, absolutely integrate with repositories > via web-services. > I could be persuaded by a full web-based tool if someone could > convince that me that difficulties of developing a complex UI are > offset by other advantages, that it can operate off-line, that it can > quickly implement no-cost, multiple temporary working areas, fully > integrate with my other desktop applications and not get mangled by > browser updates. > > I am not at all convinced by the deployment/update argument for > web-based tools. It really is not at all difficult to manage packaged > downloadable installs, including slip-streamed updates with > notifications. I have done this myself with as one developer, 3000 > users and a decent install program Perhaps the java environment is > harder but my consumer experience of Eclipse and other java apps is > not one of horrible complexity. > > Whilst seamless automatic updating of a web-app is generally helpful, > there are situations where such updating conflicts with user wishes, > so you end up having to replicate an upgrade only on-demand facility > as per Google mail, or 'revert to older version'. > > But for me the UI issue is critical. I know that javascript and HTML5 > developments are improving things all the time but web-based apps are > still always more clunky and prone to weirdnesses that you simply do > not see with desktop apps. As Seref says this is not the place to > document actual UI requirements but I think it is fair to position an > archetype/template tool with the UI demands of an Eclipse/VS type > application, and as THomas says, no-one is using web apps for this > kind of scenario. > > Pablo - is your web-based template tool visible anywhere? Perhaps you > could persuade me that I ma wrong :-) > > Ian > > > Dr Ian McNicoll > office +44 (0)1536 414 994 > fax +44 (0)1536 516317 > mobile +44 (0)775 209 7859 > skype ianmcnicoll > ian.mcnicoll at oceaninformatics.com > > Clinical Modelling Consultant, Ocean Informatics, UK > openEHR Clinical Knowledge Editor www.openehr.org/knowledge > Honorary Senior Research Associate, CHIME, UCL > BCS Primary Health Care www.phcsg.org > > > > > On 11 September 2011 02:25, Dr Lavanian <lavanian at vsnl.net> wrote: > > Hi all, > > Both approaches have their pros and cons. I would suggest a hybrid approach. > > Have a desktop app with a local Db that updates itself from a web based > > repository, as per need. This way you could have the security and speed of a > > desktop app with the 'updatability' of a web model. > > > > With warm regards, > > > > Dr D Lavanian > > MBBS,MD > > CEO and MD > > HCIT Consultant > > www.hcitconsultant.com > > > > Visit www.medhelp247.com for a life saving medical service > > > > Certified HL7 Specialist > > Executive Member - IAMI > > Co-Chair, Memberships - HL7 India > > Member- American Medical Informatics Association > > Member HIMSS > > Senior Consultant and Domain Expert - Healthcare Informatics and TeleHealth > > Former Vice President - Healthcare Products, Bilcare Ltd > > Former Vice President - Software Division, AxSys Healthtech Ltd > > Former Co-convener Sub committee on Standards , Governmental Task force for > > Telemedicine > > Former Vice President - Telemedicine (Technical), Apollo Hospitals Group > > Former Deputy Director Medical Services, Indian Air Force > > Office: +91 20 32345045 > > Mobile: +91-9970921266 > > > > ----- Original Message ----- > > From: pablo pazos > > To: openehr technical > > Sent: Saturday, September 10, 2011 11:01 PM > > Subject: RE: openEHR Transition: Web-based tools? > > Hi Ian, > > > > We develop web based systems because we are web developers. In my case I > > have started my programming skills on web based systems, and now I have > > learned a lot of tools, frameworks and web standards and I have very little > > experience on desktop based tools. > > > > Said that, I think desktop based tools have the same value and usability as > > the web based ones. There are tools that by nature have to be web based, but > > other tools like the template editor is ok on desktop. > > > > I have the dream that one day I open just one program (a web browser) and > > get free access to all the archetypes and templates available in the cloud > > (multiple CKMs), and may create, edit and share those artefacts also online. > > Sometimes I think about something like an openEHR facebook, where archetypes > > are people, templates are groups, and all are related by slots (friend > > relationships). This is just a dream... > > > > -- > > Kind regards, > > Ing. Pablo Pazos Guti?rrez > > LinkedIn: http://uy.linkedin.com/in/pablopazosgutierrez > > Blog: http://informatica-medica.blogspot.com/ > > Twitter: http://twitter.com/ppazos > > > >> From: Ian.McNicoll at oceaninformatics.com > >> Date: Fri, 9 Sep 2011 16:10:10 +0100 > >> Subject: openEHR Transition: Web-based tools? > >> To: openehr-technical at openehr.org > >> > >> Hi all, > >> > >> One of the suggestions in the White Paper which appears to have > >> universal support is a move to support much more open-source tools > >> development. Clearly some tooling must be web-based e.g repository > >> management and associated formal and informal discussion e.g. CKM and > >> any new community repository. > >> > >> However, I am much less clear on why we might need web-based primary > >> authoring tools for archetypes and templates. Diego, Pablo and Sam are > >> all keen on this approach but I remain unconvinced that this is really > >> a key requirement, given that archetype authoring is in essence a > >> solitary activity much like any other code development. By all means > >> build in much better integration with repositories and other > >> mechanisms to allow joint working, but even with modern javascript > >> libraries and Flex-style components, HTML-based tooling just feels > >> like it adds a layer of development complexity and probably some > >> usability-clunkiness which is not offset by the benefits. > >> > >> Maybe I am just an old-timer but having waited for may years to get > >> the kind of development environment that Visual Studio, Eclipse and > >> equivalents bring, and that I think is equally required for archetype > >> development, I am loathe for us to get slowed-down by insisting on a > >> 'web-based'. > >> > >> What do others think? > >> > >> Ian > >> > >> Dr Ian McNicoll > >> office +44 (0)1536 414 994 > >> fax +44 (0)1536 516317 > >> mobile +44 (0)775 209 7859 > >> skype ianmcnicoll > >> ian.mcnicoll at oceaninformatics.com > >> > >> Clinical Modelling Consultant, Ocean Informatics, UK > >> openEHR Clinical Knowledge Editor www.openehr.org/knowledge > >> Honorary Senior Research Associate, CHIME, UCL > >> BCS Primary Health Care www.phcsg.org > > > > ________________________________ > > > > _______________________________________________ > > openEHR-technical mailing list > > openEHR-technical at openehr.org > > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > > > _______________________________________________ > > openEHR-technical mailing list > > openEHR-technical at openehr.org > > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110911/f53a7f89/attachment.html>
