The road of Magnolia International's development team choosing Vaadin as client technology for the new Version 5 of their CMS. Presented on september 17th 2010 at the unconference.
The road of Magnolia International's development team choosing Vaadin as client technology for the new Version 5 of their CMS. Presented on september 17th 2010 at the unconference.
Daniel Lipp at Magnolia CMSWell, today there's ton's of client technologies. We already had done an evaluation before where we ended up deciding for GWT/ExtGWT. When we started using it we come across a few problems that made use rethink. Find more details here: http://philipp-baerfuss-magnolia.blogspot.com/2010/08/why-vaadin-odyssey.html
Eclipse RAP was never on the list. I actually have some experience and I personally think it's a great tooling - in case you need both: Desktop & Web-Client. As we were only looking for a web-client I don't think this would have been the best choice. In addition it has quite a steep learning curve if you did not Eclipse RCP before...
Sorry for the late response, Dan1 year ago
Are you sure you want to
Daniel Lipp at Magnolia CMSWe had favored a GWT-based approach before we came across Vaadin. Vaadin solved the problems we had with GWT (long compilation times, lots of boilerplate code for the remoting, heavyweight unit-tests...). As it is based on GWT we did not have to restart evaluation from scratch. RAP could have been a good fit as well (I got some deeper insights about a year ago and hence I know it has quite a few things in common with Vaadin) - especially if we had come from a RCP background.2 years ago
Mgnl 5
-
Why Vaadin
from Flickr by Marco Belluci
1
Magnolia is a registered trademark used by permission
Version 1.0
Architecture diagramm
2
Magnolia is a registered trademark used by permission
Version 1.0
Our road to Vaadin
• First evaluation of GUI technology resulted in GWT (ExtGWT)
• Started with ExtGWT
• Met obstacles
• Rethought our choice
• Came across Vaadin
• Took a closer look
• Did a PoC
from Flickr by Wolfgang Staudt
3
Magnolia is a registered trademark used by permission
Version 1.0
Pro Vaadin...
• Apache License
• Well documented
• Many Add-ons
• Out-of-the-box theming
• Close to Swing development
4
Magnolia is a registered trademark used by permission
Version 1.0
...Pro Vaadin
• Remoting handled by Framework
• Testing with pure JUnit
• Can integrate any GWT-components
• Rare GWT-compiles
• Easy to write additional modules
5
Magnolia is a registered trademark used by permission
Version 1.0
First experiences
• Flat learning curve - easy to get
started
• Community works well
• Easy to integrate pure GWT
• Serverside eventhandling is not a
problem
• Some Client-Components are rather
slow
• TreeTable is not yet where we need it
6
Magnolia is a registered trademark used by permission
Version 1.0
Conclusion
• Vaadin works very well for our needs
• Efficient way to program Web-Apps
• Problems we came across are minor issues
• Collaboration with the Vaadin-guys works great
• -> We’re convinced we made the right decision
7
Magnolia is a registered trademark used by permission
Version 1.0
Lutz Hühnken
Eclipse RAP was never on the list. I actually have some experience and I personally think it's a great tooling - in case you need both: Desktop & Web-Client. As we were only looking for a web-client I don't think this would have been the best choice. In addition it has quite a steep learning curve if you did not Eclipse RCP before...
Sorry for the late response,
Dan 1 year ago