Alloy UI vs other Javascript frameworks

RE: Alloy UI vs other Javascript frameworks

2020-01-24T18:20:57Z

Have you tried this: https://portal.liferay.dev/docs/7-1/tutorials/-/knowledge_base/t/using-the-bootstrap-3-lexicon-css-compatibility-layer

RE: Alloy UI vs other Javascript frameworks

2020-01-24T17:52:31Z

Just to add to this ... I try to steer clear of using anything Liferay provides in this space. I broke that habit and used Lexicon code in particular cards. Which was nice, we had cards and a few other things when Bootsrap 3 didn't have that so it made perfect sense.

Until upgrade time.

At upgrade time what have I done to myself by using Liferay's UI code and assimilating? The same is true of BS3 to 4 ... Pain immense pain. You can't just run an upgrade in Liferay. So to move from Lexicon to Clay now in the templates that all my users are using daily? I have a terrible task facing me or the person I delegate this to. Our web content templates both need porting from Velocity to Freemarker and also need linting because I can't rely on class names being there.

I never used AUI like I was supposed to so metal or anything else is irrelevant but man Clay and Velocity removal looks like a PITA.

RE: Alloy UI vs other Javascript frameworks

2017-09-01T18:16:48Z

Well, AlloyUI is somewhat deprecated.
https://web.liferay.com/de/web/nathan.cavanaugh/blog/-/blogs/the-status-and-direction-of-the-frontend-infrastructure-in-liferay-7-dxp

So, personally, I wouldn't use it for new applications. Maybe for tiny things, since it is there out of the box and works very well.

Alloy UI vs other Javascript frameworks

2017-09-01T07:02:45Z

I have a scenario. where in we are developing applications on Liferay 6.2 , but the UI would be developed over Kendo UI - the sole reason being the developers are experienced in it. But I am eager to know the advantages that Alloy UI could provide against Kendo(or any other such framework) in case we need to switch the decision.

Thanks well in advance.