> >I am going to start a wiki page to capture this, but from initial >investigation this is what I think these are important criteria for a >client/user portal technology: > >- runs in modern browsers without user having to install any plug-ins >- allows for communicating with server over RESTful >- allows for implementing responsive, rich user interface >- is skinable: administrators can change color schemes/logos etc. >- allows writing and executing unit test - preferably without having >running server >- offers no-compilation/minimum compilation deployment during development >(unlike with Tapestry/Java - I want to change something and see it in my >browser after refreshing a matter of seconds not minutes) > >I am quite sure at the moment that having chosen technology to be usable >outside of the browser is less important than any of the above. >But is there anything else I am forgetting about? >D. >
This looks like a good list to me. An additional dimension to this will be the usability consideration. The chosen technology has to allow for a decomposition of the current user portal. Elements will have to be grouped together in a different, more user centric way. Some functions will be presented in a full-screen mode (similar to using a browser for the current user portal), but some otther parts need to exist in a corner of the screen and provide simple status updates. Examples are presence, message waiting, etc. Being able to create widgets is another dimension, where these widgets can run outside of a browser - e.g. directly on the Vista desktop. --martin _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
