mjvesa / comod-vaadin Goto Github PK

The behaviour of elements strongly depends on which base class they were extended from. The renderer should have some suppot for this. Maybe not complete support for everything, but either supprot vertical laout and others, or just Div and add documentation for it.

Right now there is nothing really done for the Lit templates when it comes to managing the imports. Imports should simply be obtained from a hardcoded list and added to the template file.

The elements for table are listed in the link below. Add those and also a predefined table or few with interesting configuration.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element#table_content

The new CSS utility classes can be found here https://vaadin.com/docs/latest/ds/foundation/utility-classes Those should be supported with their own custom editor that is aware of their existence.

VDOM can make things faster by not re-rendering the entire design as is done now. VDOM is necessary, as the entire design is dynamic. To handle nested components, a special Web Component
could be created that takes the CSS and ATIR inside the nested components. It could be possible to attach a separate VDOM there as well, as for each further nested component. This scheme would allow having faster partial updates and also style encapsulation trough the use of Shadow DOM.

Since we are using the Elemen API, all HTML elements can be supported. So add them to the palette.