I will definitely outline the short-commings a bit. But I am rather positive that we will be able to sort this things out one or the other way.
There were some blogposts last August about why we have chosen Vaadin: - http://philipp-baerfuss-magnolia.blogspot.com/2010_08_01_archive.html The short-commings are rather important if you want to build snappy UIs, but they are not necessary mission critical in general: - resizing of dialog flickers - tree reloads completely - expanding nodes - deleting an item - adding a single item - tree column resizing follows a wired algorithm - not keeping the separator in the position where you drop it - long processing can block the ui - events are process synchronously on the server - have to spwan a thread - client has to poll or user something like comet Cheers - Philipp On 16.02.2011, at 11:41, Oliver Geisser wrote: > Hi, > > besides being interested in Magnolia I'm also interested in Vaadin as > a GUI technology independent of Magnolia. > Vaadin imperfections > describe what we are missing/ improvements needed > discuss how we approach this with Vaadin > this should be solved till June > > So maybe it is possible for you to write a little blog post about the > experience > with Vaadin and possible workarounds for shortcommings? > > Greetings > Olli > > -- > og > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
