It's update time!But with Vaadin 24 Polymertemplate is deprecat

Directory App Layout Add-on
1

It's update time!!!

But with Vaadin 24 Polymertemplate is deprecated and was removed.(com.vaadin.flow.component.polymertemplate.Id) is not included anymore.

How can I achieve making App Layout run again?


@jon martin solaas - have u got an idea?

Anybody else?


Edit:

Forked > Worked for an hour > gave up -> I don't get that polymer/lit template stuff - there is too much to do for my little knowledge about those templates :/

I know theres a coverter. Used it, but still there are many polymer things in the project which lead to the project not being able to be built.

Pls assist if possible.

2

Have you tried adding the following dependency?

https://mvnrepository.com/artifact/com.vaadin/flow-polymer-template

3

Nope, i'll try thx!!!

4

Hi Johannes,

I tried to update as suggested. But unfortunately there where some internal breaking changes, which are very hard to work into. Most prominent: RouteData & RouteAliasData (both Flow classes) do not have the url anymore. Your class "RouteSimilarity" is using it to compare some urls. But as Flow does not have those url attributes anymore, the comparison is not working anymore. I have no idea how to solve it.

I know you are doing that for free in the past and I'm very thankful about it. But we need to update to vaadin 24 and especially Spring Boot 3.x.x soon and I need to make the layout work again. I can not achieve this by myself, so I either way need you to kindly look into it, or to use another app layout, which supports vaadin 24, but which will be lot of work to implement.

My changes until now:

  • Updated to Vaadin 24.5.3
  • Updated to Spring Boot 3.3.5
  • Removed Iron Icons (deprecated)
  • Replaced javax with jakarta (jakarta.servlet-api 6.1.0)
  • Updated maven plugins
  • Using flow-polymer-template dependency
  • Updated Label -> NativeLabel
  • js files: @vaadin/vaadin-icons -> @vaadin/icons

May you please assist? Most help will be, of cource to make the layout work again, but I'm absolutely fine for now, if you update the pom to vaadin 24.5.3 locally on your side and then look into RouteSimilarity class to check out the missing url attribute and how to handle it.

Best, Simon

5

Hi Johannes, have you any suggestion, or is this app effectevely deprecated?

Wish you a happy new year!

Best, Simon

6

Hi Simon!

I also wish you a happy new year, I hope you are doing great :).

The app is not deprecated. However, it is currently not compatible with the latest Vaadin version due to limited input from both myself and the community.

At the moment, I'm focused on another side project, but I do hope to find time soon to work on an update. Unfortunately, I can't provide an exact timeline for this.

As this project is a hobby I work on in my free time. If anyone else wants to help out, that would be fantastic!

7

Hi Johannes,

I have a version, that might be ok running with (at least should be running), but I can not test it, as I don't have a vaadin subscription and therefore the build is stopped.

I'm not sure, whether building the final application code (my app code + app-layout) is even possible without the subscription, what makes the app-layout effecively being a vaadin pro component.

Rewriting the layout LitTemplate might be impossible, as it realy builds on to of Polymer.


[INFO] Flow Polymer Template is not part of Vaadin Core. You need a Prime Subscription, Enterprise Subscription, Ultimate Subscription, or similar.

Go to https://vaadin.com/pricing for information about upgrading your subscription or contact sales@vaadin.com to discuss your options in person.


So someone needs to pack it, who has a subscription to test, but nevertheless, as I understand the dependency thing, even though it might be packed, one can not use it without subscription?

The code is in my github:

https://github.com/simonspdb/vaadin-app-layout


@Johannes could you please comment on that, please, so I can make sure, me and you are not wasting time? Your comment would be great to clarify things for me and others. So then I can focus on a more native vaadin layout solution, which unfortunately does not have those great features.


Btw. does anybody know, why vaadin did not invest some time in a propper app layout with some modern features? "Because you are not paying for a vaadin subscription" is not a valid answer ;)


Best, Simon

8

Hi Simon,

I must admit that I hadn’t realized until your comment that PolymerTemplate has been re-released as a Pro feature. I find this decision a bit surprising, especially considering it was previously available for free. I would have thought that not much of the implementation would have changed with the new release. But it is what it is.

If this project would continue to rely on PolymerTemplate, it seems like the addon would be limited to Pro users. Personally, I’m not fond of this idea, as I’d prefer to keep it accessible to everyone. Correct me if I'm wrong, I think running isn't the problem, but building for production might also require a pro subscription.

Given the situation, I think the project—specifically the templates (https://github.com/appreciated/vaadin-app-layout/tree/master/app-layout-addon/src/main/resources/META-INF/resources/frontend/com/github/appreciated/app-layout) will need to be ported to LitElement. This might be achievable using @flowingcode/fc-applayout, though it will require quite a bit of research and time on my part (or somebody willing to invest some time here).

9

Hi, thanks for your comment.

Best, Simon

10

Hello Johannes,

just want to inform you about our decision regarding the AppLayout.

We are now developing our new version of the default vaadin app layout with the vaadin side bar (but don't plan to make an abstraction out of it for the whole community).

We now have a dev version of vaadin 24 alongside with spring boot 3.4.1 and java 22 which is running well.

Honestly, we pretty much stuck with the Notifications for the Notification Bell, as we never intended to leave your app layout and now need to reimplement/reinvent some parts of it.

That said, again thank you very very much for your work. We were very happy about the layout and the work you put into it!

Best, Simon