Migrating Web Apps - any interest?

[jusjoken]

Originally Posted by tvmaster2

Using the old, mobile web app (Phoenix Remote) on an Android device, what causes this failure when you attempt to call up tv guide listings?

Attachment 17891

Attachment 17892

Do you get the same error if you go direct to the mobile web app..,not using the apk?

http://yoursageserverip:8080/sagem/m/menu.jsp

Let me know.

K

[tvmaster2]

Originally Posted by jusjoken

Do you get the same error if you go direct to the mobile web app..,not using the apk?

http://yoursageserverip:8080/sagem/m/menu.jsp

Let me know.

K

Using 8080 in a browser works fine, just the Android Phoenix Remote apk gets the Java error, or whatever it is…

[jusjoken]

Originally Posted by tvmaster2

Using 8080 in a browser works fine, just the Android Phoenix Remote apk gets the Java error, or whatever it is…

Interesting...as I believe its the same web page. I will dig into the code more.

K

[tvmaster2]

Forgot, ‘Search Airings’ and ‘Search Recordings’ also returns this error, seen in the attached photo. Otherwise, the app works perfectly.

[jusjoken]

Originally Posted by tvmaster2

Forgot, ‘Search Airings’ and ‘Search Recordings’ also returns this error, seen in the attached photo. Otherwise, the app works perfectly.

So why do you choose to use the APK app rather than direct to the URL in a browser on the same device if the present the same web pages and the apk wrapper is erroring ?

K

[tvmaster2]

Originally Posted by jusjoken

So why do you choose to use the APK app rather than direct to the URL in a browser on the same device if the present the same web pages and the apk wrapper is erroring ?

K

Because on a small, cell phone screen, that’s what the apk was designed for. Easier to read, get around, manipulate, etc. On a eight inch or larger screen, I use 8080 and a browser.

[jusjoken]

Originally Posted by tvmaster2

Because on a small, cell phone screen, that’s what the apk was designed for. Easier to read, get around, manipulate, etc. On a eight inch or larger screen, I use 8080 and a browser.

So I think we are talking about 2 different things.

There are 3 different web apps built on sage (perhaps more).

Web - or neilms web server - accessed from

http://server:port/sage/home

Mobile - accessed from

http://server:port/sagem/menu.jsp

APK from stuckless - added phoenix functions AND it WRAPS/links to the Mobile app above.

If you use the APK and go to the screens you have copied for me, the APK is actually going internally to the Mobile Web app at

"http://server:port/sagem/menu.jsp"

and displaying the resulting page inside the android APK app.

I believe when you say the 8080 and a browser, you are refering to the Web app at

"http://server:port/sage/home"

So, to test...if you went to a browser on your android phone and went to..

http://server:port/sagem/menu.jsp

...replacing server with your server IP and port with 8080 or whatever port you use.. I believe you will see the same mobile web pages you are seeing within the android APK.

Please confirm.

Thanks
K

[tvmaster2]

Originally Posted by jusjoken

So, to test...if you went to a browser on your android phone and went to..

http://server:port/sagem/menu.jsp

...replacing server with your server IP and port with 8080 or whatever port you use.. I believe you will see the same mobile web pages you are seeing within the android APK.

Please confirm.

Thanks
K

Yes, that works, but as you can see, the readability due to opposing font/text sizes - anything related to the drop-down menus, is basically unreadable without zooming. But all the info is there, listings and search included.

[jusjoken]

Originally Posted by tvmaster2

If I’m not mistaken, all your mentioning are http browser options? Have you ever used the ‘Phoenix Remote”? I believe that’s what you’re referencing as Stuckless creation, correct? That’s my favourite Android method, at least on a cell phone.

Yes, the stuckless option I mentioned is the APK you are using. Any yes, I have it installed and am testing it and seeing if I need/want to do any updates to it.

Although there are added functions within the APK, the Mobile Web view is just linking internally to the Mobile Web App.

I guess it really does not matter, I was just trying to see if it behaved any different in the current (old) jetty version in those 2 formats.

I have the Mobile Web App working now within the APK and directly with the new Jetty 9 plugin with Java 8. I have more to do of course but good to see it work.

K

[jusjoken]

Oh and ‘Search Airings’ and ‘Search Recordings’ also work with the new Jetty 9 and Java 8.

K

[tvmaster2]

Originally Posted by jusjoken

Oh and ‘Search Airings’ and ‘Search Recordings’ also work with the new Jetty 9 and Java 8.

K

Jetty 8 and 9 installed on which platform, Windows 10? The benefit of the Phoenix Remote isn’t necessarily any different functionality, it’s merely a fore more friendly and functional user-interface for smaller, portrait screen sizes.

[jusjoken]

Originally Posted by tvmaster2

Jetty 8 and 9 installed on which platform, Windows 10? The benefit of the Phoenix Remote isn’t necessarily any different functionality, it’s merely a fore more friendly and functional user-interface for smaller, portrait screen sizes.

I am referring to the development work I am doing for the UNRELEASED new Jetty plugin that uses Jetty 9 and Java 8+

I have so far only tested it on Windows 10 but will test unraid as well and will test Jave 9, 11 and 16 likely.

There is a lot more work to do before this is released but it is progressing well and will allow more web programming with better interfaces etc. in the future.

K

[jusjoken]

As info for everyone following this... the following screen grabs are taken from my Android Note 20 using chrome and the Mobile Web App and using the Phoenix Remote. The server is running on Windows 10 using the in development Jetty 9 plugin using Java 8.

Using Chrome - Mobile Web App - main menu


Using Chrome - Mobile Web App - lineup



Using Phoenix Remote - Mobile -main menu


Using Phoenix Remote - Mobile - lineup


K

[tvmaster2]

looks good.

[jusjoken]

I have spent a lot of time on this and am still making good progress but so everyone does not loose hope here is an update...

• Jetty Starter - updated to Jetty 9.4.44 - more detailed work to complete but works to allow me to test and update the other related apps
• SageTV Web Applications - lists and links to all web apps running on SageTV Jetty 9 server
• SageTV Web Interface - updated and sent to SkiingWiz to review and update as he has time (as he is the current maintainer)
• SageTV Mobile Web Interface - updated to support J9
• Media Streaming Services - used by the 2 above - updated to J9 but still need to determine how this works and how to test
• SageTV Sagex API Extensions (sagex-api) - updated to J9
• SageTV Sagex Remote API Services (sagex-services) - updated to J9
• SageTV Swagger interface for Sagex remote api testing - updated to J9 and newer swagger ui
• Batch Metadata Tools - Web Interface - updated to J9 plus TMBD TV provider (more testing needed of TV provider)

All of the above plus likely some others that are related (SJQ, SRE etc.) will need to be released at the same time as Jetty 6 and 9 cannot run at the same time.

No release by Christmas but I do plan to just continue to work on this nearly daily.

K

[wayner]

Thanks for the update Ken. I am going to do a new install of Sage - what Java version should I run? I was thinking 11 but from your post should I stay on Java9? This is on unRAID and I may play with a few versions.

[jusjoken]

Originally Posted by wayner

Thanks for the update Ken. I am going to do a new install of Sage - what Java version should I run? I was thinking 11 but from your post should I stay on Java9? This is on unRAID and I may play with a few versions.

I should be more clear...J9 above refers to Jetty 9. Jetty 9 is supported from Java 8+.

I am building everything with a minimum version of Java 8 but we should test 9, 11 and 16 and report back but I have only tested it with Java 8 so far on a few windows 10 vms. As I believe the latest sage jar is built using Java 9 as minimum we should aim for most testing on Java 9.

I have an unraid server so I will soon try out a full install using the stuckless dockers.

K

[waynedunham]

Thanks for all the effort on this. Can't wait to see it when it all gets out into the wild.

[wayner]

Originally Posted by jusjoken

I should be more clear...J9 above refers to Jetty 9. Jetty 9 is supported from Java 8+.

I am building everything with a minimum version of Java 8 but we should test 9, 11 and 16 and report back but I have only tested it with Java 8 so far on a few windows 10 vms. As I believe the latest sage jar is built using Java 9 as minimum we should aim for most testing on Java 9.

I have an unraid server so I will soon try out a full install using the stuckless dockers.

K

Awesome. Presumably if all works would you recommend a new system go with Java 16?

[jusjoken]

Originally Posted by wayner

Awesome. Presumably if all works would you recommend a new system go with Java 16?

Good question and difficult to answer. I am no Java expert but the pat answer is likely the highest version that SageTV and all your plugins will still work with. The answer may be different for other users that use other plugins. We have a very old collection of plugins that use jar libraries from WAY back. Many of these are "standard" libraries that may use Java features no longer available in newer Java releases. So running a newer Java version may raise errors when a plugin users a non supported function...or it may be fine if all the in use functions are still supported.

So the "safe" bet, to ensure everything still works when you have a number of plugins running is to use Java 8 or 9 or do your own testing on the newest Java releases on your set of plugins and check for errors in the logs...and move back to older Java versions until resolved.

My personal opinion would have been to stick with the newest Java 8 that you can get as everything should work with that, however with the latest SageTV jar built with Java 9 I may at least make Java 9 my minimum version. But this may all change if I test out the full suite of plugins and find Java 16 or 17 meet my needs.

Sorry for the long response. Others likely will have a different opinion. YMMV.

I will post my results with the various Java versions and this suite of plugins.

K