Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.
Technical Q&A coffee break with Leif on February 27th 2019 at 2pm CET
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
Here is the summary:
About the Expert
Leif 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.
- Worry About Backward Compatibility
- Run JavaEE and Spring Side by Side
- Use Heat Map on Any Given Map
- Portlet Support for Vaadin 10+
- Select Component in Vaadin 13
- Change Theme Dynamically
- Availability of Tree Component
- Make default theme with smaller font
- Cookies are not getting loaded
- Migration from Vaadin 7/8 to Vaadin 10+
- Select vs. click events in Grid
- Add custom CSS in a sprint-boot project
- Responsive design with java code
- Get background-color from Grid
1. Worry About Backward Compatibility
In the future is there a way not to worry about backward compatibility with Vaadin? -- Omar
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.
Old doesn't mean not working anymore
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.
New comes with a benefit
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 promise 5 years support for free
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.
We know that AngularJS was a nice experiment, and then quickly started to cause trouble for people who wanted to migrate to latest versions. So are we in the phase of AngularJS or the phase of top-notch Angular? -- A.Mahdy
Smooth incremental updates
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.
Building a foundation
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.
2. Run JavaEE and Spring Side by Side
We are doing gradual migration from JavaEE to Spring. Both are running at the same time, and more code gets shipped to Spring in each subsequent minor release update. Where usually would be a good place to start the migration? -- Melvin
- Make sure that everything works when both stacks are running side by side.
- If you have independent services for different views, then you can make the view by view approach.
- Otherwise, you would have to go with layer by layer, start with service layer and then do a UI layer or vice versa.
The migration of the backend is independent on Vaadin, and if the backend is decoupled from the front-end, then Vaadin code is indifferent in this case, and view by view migration makes more sense -- A.Mahdy
3. Use Heat Map on Any Given Map
I've seen people doing heat map on geographical maps like Google Maps, but I want to have a heat map on a floor map inside a building? -- Melvin
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
setPlotBackgroundImagemethod for doing that.
In newer version (6+), you instead use CSS to set the background image for
4. Portlet Support for Vaadin 10+
Vaadin has had support for portlet (Liferay) development since version 6. Does Vaadin 10+ support portlet development? -- Gordon
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.
Better late than never
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.
Version 14 or 15
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.
When you mention customers, how does it work to get certain features prioritized? Do they sponsor it? -- A.Mahdy
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.
5. Select Component in Vaadin 13
I am using vaadin-spring-boot-starter 13.0.0.beta1 but can't use the Select component (there is no Select component) which should be available for Vaadin 13 as announced. What am I missing? -- Marco
Available in 13.beta2+
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.
6. Change Theme Dynamically
How to change Vaadin theme dynamically? The user has a combobox filled with values (Lumo & Material), and on selection, the application should change the theme. -- Kaustubh
- In Vaadin 8, it's
UI.setThemeso it should not be too complicated.
- In Vaadin 10 and newer:
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.
Make your custom theme based on Lumo
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 that you can use to achieve those changes programmatically from Java code.
7. Availability of Tree Component
When will Tree component be available? -- Marco
We can use TreeGrid component with only one column. -- A.Mahdy
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.
Priorities for version 14
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.
Would it be a drawback to use TreeGrid with one column to act as a Tree component? -- A.Mahdy
- Keyboard navigation is slightly different.
- It requires a little bit extra code, but not that much.
- For most cases, TreeGrid with one column should be a quite good workaround.
8. Make default theme with smaller font
Why the default theme font is so Big? Remember that Vaadin is for dev business desktop app on the web. More info always is better. -- Eugenio
- When you design the overall theme, you want it to look beautiful because that's what makes people interested.
- There is a conflict between a beautiful and pleasing to the eye and being practical in applications that have lots of data.
- We encourage developers to rethink how the application presents the data, to only show the relevant things.
- We know that in many cases that is not practical.
Easy to tweak the whole theme
- As shown earlier, changing one variable in the Lumo theme can affect the whole application's look and feel.
- Create custom Lumo variations for your application.
Lumo changes apply on all built-in components, what about external add-ons? -- A.Mahdy
- It does not pick modifications unless it uses Lumo as well.
- You need to configure each add-on separately.
Compact preset mode in Vaadin 13+
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.
Not limited to version 13
You can copy the compact theme to your existing project or an older version of Lumo.
9. Cookies are not getting loaded
We have stored around 5-6 cookies for one app, and bootstrap failed to load the app. The tota size of cookies is around 4-5 kB. Any idea? -- Tadej
- 4 kB is in most cases the maximum allowed size per cookie.
- Not surprised that there are problems with an application that uses 4-5 kB of cookies.
- Vaadin uses one only cookie, that is around 100 bytes.
- Avoid storing many things in cookies.
- Store things in the database and only store the key for that entry in the cookie.
10. Migration from Vaadin 7/8 to Vaadin 10+
What about migrating apps from 7 to 12.0.+. -- David
- Moving from 7 to 10 are two steps technically:
- 7 to 8 where you change how Vaadin interacts with the data layer.
- Documentation covers what you need to do.
- You can use compatibility layer, so you don't have to update the data layer immediately, but rather step by step.
- 8 to 10 where you change the actual components.
- Documentation covers many options.
- You can continue to use version 8, and it has support for many more years.
- We are going to still add small features to version 8, but it's not our main focus.
- 7 to 8 where you change how Vaadin interacts with the data layer.
- We have the Multiplatform Runtime tool that allows you to run Vaadin 7 or 8 views, side by side with Vaadin 10+ views in the same application. (Note: it's a commercial tool).
- One other option is to start writing a fresh new application if you have a lot of legacy code and you want to get rid of it.
11. Select vs. click events in Grid
What is the difference between
itemClickListener event and
selectListener event in Grid? -- Jonte
- They are mostly the same.
- In the multi-select mode, clicking on checkboxes triggers both events.
- Clicking individual row, highlights the row and fires
- Navigating with keyboard across the rows trigger
selectevent but no click event happens.
In which event we can get the selected rows? -- A.Mahdy
- It is always guaranteed to get the selected rows inside the select event.
- There are few cases where selected rows are not immediately available in the click event.
12. Add custom CSS in a sprint-boot project
How to add custom CSS in the spring-boot project? -- Kamrul
13. Responsive design with java code
How to make a responsive design with Java code? -- maticpetek
You can make few if-conditions to adjust the component dimensions, locations, and appearances based on screen size and available space.
Can we get screen and browser information from the Java code? -- A.Mahdy
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.
14. Get background-color from Grid
How to get the applied
background-color from a Row and a Cell of Vaadin TreeGrid/Grid? -- Helmer
There is no API for that. The best approach is to keep track of modified row or cell on the server-side, instead of trying to get it from the client side.