Hi Peter, Web developers can easily tackle those problems, see below:
> But web based apps bring their own set of problems that desktop apps > don't have. Ian has been talking about poor usability. > > * How do you do keyboard shortcuts in a web application? How do you > set keyboard focus to the appropriate widget to maximise ease of use? > Both of those can be achieved in a web app, but it's extremely > difficult. > Just use HTML: http://en.wikipedia.org/wiki/Access_key > * How do you recover gracefully when the user's session times out? > Imagine you're in the middle of working on an archetype, you spend 20 > minutes talking to a colleague or answering emails, and your web > session times out. All of your work is gone. There are ways to handle > this gracefully, but they are are horribly difficult to program. This > problem simply doesn't exist with desktop apps. > One way to maintain a session open is to send heartbeats using AJAX: http://en.wikipedia.org/wiki/Ajax_%28programming%29 > * How do you design your application so that it performs well without > putting half of your business logic into Javascript that is riddled > with hacks for handling old browsers? > For performance and rich user interaction we have to use AJAX. For compatibility, use standards: http://www.w3.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110911/c173aafd/attachment.html>
