Wednesday, 17 October 2007
Lotus Quickr - it sooooooooooooo rocks
partners exploring Lotus Quickr; both the Domino and Java flavours ( aka
The more I see of it, the more I like it - I need to do more, and get
into the depths, especially the J2EE deployment, which is based on
WebSphere Portal and Web Content Management.
All in all, a very good investment ......
Thanks for your comment. To be honest, it really depends on your requirements. As you rightly say, Quickr can be seen as a "black box" solution, where the underlying deployment choices become less relevant.
Therefore, your current, and potential future, requirements may help answer the question one way or the other.
The other thing that I'd add is that, from a purely personal perspective, the Java deployment of Quickr is potentially easier to theme and re-theme because it's using standard constructs such as Cascading Style Sheets (CSS) and HTML/JSP tags. In addition, it's based on the same re-usable component model as WebSphere Portal and Web Content Management use e.g. using authoring and presentation templates to separate content from process / presentation.
I guess, on the flip side, the Domino deployment would be easy to re-theme if you have a background in Domino design and build.
Does this help ?
It sounds however that the differences are more on the infrastructure and customisation side?
Subscribe to Posts [Atom]