What would you ask us on a coffee break? Just wanted to all forum users know that we are going to host a special live “Coffee Break” session on Wednesday, February 27th 2019 at 2pm CET.
This is opportunity to ask any Vaadin related questions and discuss live with a Vaadin expert.
Join here: https://pages.vaadin.com/vaadin-coffee-break
https://www.youtube.com/watch?v=MMhA8GNF3xo
See you!
https://www.youtube.com/watch?v=Dj9nd1_ZYsA
[Leif]
(https://twitter.com/leifastrand) has been in product development for many years and has seen many things that can go wrong. As a product architect at Vaadin, he is now helping everyone else to prevent the mistakes that he has been part of making previously. He is helping out in everything around product development, like fixing challenging bugs, designing new features, and helping everyone else to develop the products.
The web as a platform is evolving quickly; there’s no way around it. So things change all the time, like five years ago AngularJS was barely starting, but now it’s not the most popular thing anymore. React has overtaken it, and Vue is getting up there. So things keep changing all the time.
You can still use Vaadin 6 if you want, we don’t provide any security updates for free for it, but it works. It should work in all browsers, it works on relatively modern servers and so on. So if you have an application that just works, you can keep using it.
If you want to benefit from all the new things and make applications that look modern, that use the latest features from modern web browsers, then yes you need to make updates. Some of those updates require you to change more things because assumptions have changed, so it’s really up to you.
We are giving quite good coverage there because when we released Vaadin 10, we said that it is getting support for five years to come. Looking at how quickly things evolve that’s a long time still.
The plan that we have now is to add new things incrementally, we have one big thing upcoming which is to change from Polymer 2 to Polymer 3, and from the old deprecated Bower dependency management to NPM instead. That is going to be a significant change behind the scenes, but we try hard to make it smooth for users also. So we have now built a quite solid foundation to build upon it.
You can never know because things might change, but hopefully, this is a foundation that you can keep building on top of it.
One version that many are going to pick is 14, which is again a long-term support version, which means that we are going to support it for free for five years. Also with this version and all other versions, we provide non-free support for longer, but five years is what we give to everyone anywhere for free. Vaadin 14 has a scheduled release on June 2019.
The heatmap feature in Charts is only about putting colors in a coordinate system, and it doesn’t directly have anything to do with earth maps.
You can set the image (the floor map) as a chart background and then preferably adjust the x-axis and y-axis sizes to match the pixel dimensions of the image.
With older versions of Charts, there’s a setPlotBackgroundImage method for doing that.
In newer version (6+), you instead use CSS to set the background image for .highcharts-plot-background.
We wanted to get Vaadin 10 out as quickly as possible, and we had to do lots of compromises, one of them that, yes, portlet support did not get implemented.
Another thing that we didn’t get done was CDI support for instance. CDI support became available in Vaadin 12, so a couple of releases afterward.
Portlet support is still pending right now. We have a pile of customers for that, which probably means that by Vaadin 14 (beginning of June 2019), we could have portlet support. Plans might change, but 14 or maybe 15 is what it looks like right now.
It’s case by case. Portlet support got sponsored, but generally, now and then customers have some specific feature that they can see on our list, but it’s not on our top priority. But then they are eager to get it, so they sponsor the development of it.
There is always a sponsoring option for any feature that makes sense as a whole.
We had a bug in beta 1, and the Select component got included in two out of three places, and unfortunately the last critical place was missing. It is included in beta 2, which was out a week ago. So please update to beta 2, and you should have the Select component available there.
UI.setTheme so it should not be too complicated.Because of the way we use specific browser features, like style encapsulation and CSS properties, it comes with a side effect that themes are pre-loaded in a way that makes it difficult to change it on the fly.
When you use the Lumo theme, you can configure many things by setting different CSS variables, that can be done just by adding and removing CSS, and get the theme changed on the fly.
Example, in your Vaadin application, apply a CSS style on the <body> element like:
--lumo-base-color: blue;
--lumo-font-size-m: 20px;
It gets updated on the fly. So just changing a couple of variables make quite significant changes. Again, this only work if the new theme is based on the Lumo theme. Enhancing this is still on the backlog, and it does not have a specific priority at the moment.
There is an add-on for [injecting CSS variables]
(https://vaadin.com/directory/component/cssvariablesetter) that you can use to achieve those changes programmatically from Java code.
Tree is on our list of components that you could use in Vaadin 8, but it’s not available in Vaadin 10 or newer yet. We hope to get it there, but since there is some workaround through using a TreeGrid with only one column, it’s not our highest priority.
There were plans to have it in version 13 or 14, and I can say for sure that 13 won’t happen because it’s already on beta, 14 also looks quite unlikely, because we prioritized to get the NPM support over getting more components.
We have a ticket about updating documentation related to what features are going to be available in H1 2019.
Starting Vaadin 13, you can use a compact preset for Lumo, instead of you doing it yourself, we have made some thoughts into exactly the ratios between different things.
@HtmlImport("frontend://bower_components/vaadin-lumo-styles/presets/compact.html")
@Theme(Lumo.class)
You can copy the [compact theme]
(https://github.com/vaadin/vaadin-lumo-styles/blob/master/presets/compact.html) to your existing project or an older version of Lumo.
itemClickListener event and selectListener event in Grid? – JonteitemClick event.select event but no click event happens.The source code of the [Full Stack App with Spring]
(https://vaadin.com/start/latest/full-stack-spring) under the [Vaadin starters packs]
(https://vaadin.com/start/latest) shows how to use it.
You can make few if-conditions to adjust the component dimensions, locations, and appearances based on screen size and available space.
It’s on the roadmap for Vaadin 14, right now there is no easy way to get it, but the information is available in the HTTP Header.