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.
3. 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
4. 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
5. ...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
6. 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
7. 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