Options for SmartVISU other than jQuery Mobile?

[bmxp]

We should consider to think about future options for SmartVISU:

jQuery Mobile seems to be deprecated pretty much. The last stable version will not be compatible with jQuery > 2.1.
There is however a release candidate for version 1.5 which is said to be compatible with jQuery 3.0 but we did not make any efforts to port SmartVISU to jQM 1.5 and jQ 3.

Switching to a framework like React, Angular, etc. could probably shy away users that are used to Twig and HTML. We need to keep the entry level low.

So please collect your ideas and post them for discussion here.

[wvhn]

Well, ideas are nice. But what is needed here is ability and willingness to contribute to the migration or even to lead the migration process.

[wvhn]

I have tested jQm 1.5-rc1 in smartVISU. Generally, it works after some changes, BUT

• ui-classes in CSS have been changed massively and there is no theme roller for jQm1.5
• widgets don't get initialized via the initSelector automatically. They need to be registered individually on mobileinit
• icon handling in tabs has been changed again
• ...
  All in all a switch to v1.5 would cause some braking changes for the users. And there is no support any more :(
  So jQm1.5 is not an option.

[Tom-Bom-badil]

To be honest, I still don't get the point of switching the framework at the time being.

[x] Yes, it's deprecated.
[x] Yes, it's running fine.
[x] Yes, it will most likely run fine for some further years.

Btw, in our company we just kicked all the React, Angular etc developments in favourite of Blazor - after a loooong, hard evaluation.

/tom

--
The grass is always greener on the other side.
The 'good idea in between' is a like dagger to any project.
After a piece software is developed, the programmers always know how to do it 'better' again. [period]

[bmxp]

@Tom-Bom-badil It's not to switch now but to have a look at the future. SmartVISU is now a teenager but JQm is currently not developed any more. This might open up security holes which are not going to be fixed.

@wvhn thank you for your testing towards jQm 1.5. Too bad it is not an option.

All in all you are right: there are not enough contributors to even think about a change.