In a project I am currently working on, I created a server side wrapper for the vaadin-overlay.
I am using this server side wrapper to create, for example, a ColorPicker or an IconPicker, with Java-Code only.
I am even using it to display some kind of complex tooltip.
However, the vaadin-overlay is documented as being a "Web Component meant for internal use in Vaadin components".
In my opinion, this component is very useful and it would make sense to have a "public" version of it, including a wrapper for flow.
This would allow developers creating custom pickers and similar using java code only.
I would like to hear your opinion on that topic.
In a project I am currently working on, I created a server side wrapper for the vaadin-overlay. I am using this server side wrapper to create, for example, a
ColorPicker
or anIconPicker
, with Java-Code only. I am even using it to display some kind of complex tooltip. However, thevaadin-overlay
is documented as being a "Web Component meant for internal use in Vaadin components". In my opinion, this component is very useful and it would make sense to have a "public" version of it, including a wrapper forflow
. This would allow developers creating custom pickers and similar using java code only. I would like to hear your opinion on that topic.