We were primarily testing with just the URL. But I can see about setting up a few workstations/tablets/mobile tests.
This is very cool, I am very much looking forward to trying your module!
This may be a tall order but have you thought about PTZ controls?
Yeah I have, but we actually don't have any on site surprisingly. So it would be hard for me to test.
I was able to get the columns to adapt properly as the screen stops down to mobile size. This way there is just a single column on mobile, 2-3 columns on tablet and whatever you set for desktop.
Looks like its having some issues with showing up in the workstation, so I'm looking into that.
So from what I'm seeing it seems that the Workstation doesn't come with any proprietary codecs. This works for PC because browsers like chrome /edge ship with codecs (h.264 + AAC) built in.
I don't think there is anything I can do about that. So this might not be an option for clients using Ignition's Workstation. Even If I were able to include the codec (which I don't have plans to) the codec would need to live in the workstation application, not in the gateway.
If you have obtained a license to re-use AAC/H264 in your application (this is not an IA licensing problem, but a patent owner negotiation problem), you can provide system property overrides to your workstation launcher config and we'll toggle the proprietary codecs on when we construct JxBrowser:
-Dignition.client.jxBrowser.h264=true (legacy: ignition.jxBrowser.h264)
-Dignition.client.jxBrowser.aac=true (legacy: ignition.jxBrowser.aac)
Which toggle these JxB features.
Note that this is completely offline and based on the honor system. But make sure you pay the patent holders their money.