M5 HTML / Vaadin Integration Options
Meeting on March 27, 2011
(Espen, Tobias, Christopher)
Layers/Components
- Login
- Shell
- Header
- Shell Apps
- Apps
Integration Options
- All Vaadin - One Giant Vaadin Application
- CSSLayout Component as parent
- Benefit: Ability to completely style app - and have any transitions. (I think :Test)
- CustomLayout Component as parent
- CustomComponent as parent
- Normal Layout component as parent
- CSSLayout Component as parent
- Mixed
- HTML as Parent
- Load in Vaadin dynamically / embed
- Shell could be HTML
- Shell could be Vaadin
- Load in Vaadin dynamically / embed
- Vaadin as Parent
- Load in HTML as Shell
- Load in HTML into sub components
- HTML as Parent
What are apps?
- Is each one
- a Custom Vaadin Component
- A Custom Vaadin Component with connection to More Java / Magnolia
- a Vaadin Application
- An App is not necessarily a window - but can contain a window. Right?
Questions
- Can CSSLayout be used for root of document.
- Benefits to HTML as parent with dynamically loaded Vaadin?
- Benefits of Vaadin as parent (own the document)
- Drag and Drop
- With CSSLayout or with CustomComponent: could we have every component sitting in a dynamically transitional DIV? Test.
References
- CustomLayout https://vaadin.com/book/-/page/layout.customlayout.html
- CssLayout
- http://www.scriblink.com/
Actions
Tobias - Revive the Vaadin Magnolia Project - He'll show it to us
Espen - Build Shell as straight vanilla Vaadin