Facility Control

Is there a way to specify the default browser used by Dashboard?

I'm asking because there is a browser we need to schedule streams. The page is accessible internally only and uses a specific port. I am only able to access the page on Chrome. 

The address is as follows http://xxx.xxx.xxx.xxx:8081.

When I enter the url as follows, it comes up blank.

Under Window-Preferences->Web Browser, you can change what web browser DashBoard uses by default.

#DashBoard

Heya Ben, 

It is a bit misleading but that only changes the browser opened from dashboard not the custom panel <browser> tag.  It is goofy for sure.

There is also a bug in the current version of Dashboard (V9) that calls IE 9 instead of 11 which fails to load certain elements. Something you can try on windows is:

1. Select start and search for "Registry Editor" 
2. open and navigate to HKEY_CURRENT_USER -> Microsoft -> Internet Explorer -> Main -> FEATURE_BROWSER_EMULATION
3. select the java.exe 
4. under "Base" on the right of the popup select "decimal" 
5. input 11001
6. If "Dashboard.exe" is also in the same folder repeat steps 4&5 for that entry as well. 

Bit of a work around. I'm sure it is being worked on for the next release. 

Credit to our Dashboard king James for the fix.

Best, 

Brandon

#DashBoard

Ben,

I tried this, I still could not get my browser window to open the page needed. Thanks

#DashBoard

Brandon,

I tried the regedit solution as well. It didn't work.

Part of my problem is that the web page is not compatible with Internet Explorer 11. I even tried opening directly in a Internet Explorer 11 web browser and got the same result. It is only compatible in Firefox or Chrome.

#DashBoard

Shawn, 

That is a major bummer. Might be worth putting in a ticket about it. I know there is already one in their backlog for a chromium base, but more voices might make for more urgency.  

I'm guessing you tried the <webget> tag as well and that is sorta the only other way around it that i'm aware of without making your own api.  

I hope you find a solution my dude. 

#DashBoard

I had the same experience as described by Brandon.  If it could be placed on the project roadmap for DashBoard to support the Microsoft Edge WebView runtime natively - instead of IE - I think that would be extremely helpful going forward.  We have some internal tools that use the new WebSockets features which don't work with the IE engine and it would be awesome to display these within the DashBoard grid file directly.

In doing a bit of research I don't think it would be too difficult to roll this out, from what I could determine trying to reverse engineer the implementation, the builtin browser runs as a Java app within C:\DashBoard\IEProcess.jar which is a class that implements the Eclipse SWT browser widget.  It seems like the capability to use various browser engines is already available for use... the FAQ from the Eclipse website states: "To specify that an Edge renderer be used by a Browser instance, create it with style SWT.EDGE (since 4.19) or set the Java property org.eclipse.swt.browser.DefaultType=edge."

So this makes me wonder if it might be possible for the developers to add a DashBoard preference item which controls the aforementioned style or the DefaultType property.  That might be an easy way to get us a modern browser environment within the <browser> widget.

------------------------------
Landon Gaus
KTRK
------------------------------

Original Message:
Sent: 03-10-2021 18:16
From: Brandon
Subject: Specify Dashboard Browser

Shawn, 

That is a major bummer. Might be worth putting in a ticket about it. I know there is already one in their backlog for a chromium base, but more voices might make for more urgency.  

I'm guessing you tried the <webget> tag as well and that is sorta the only other way around it that i'm aware of without making your own api.  

I hope you find a solution my dude. 

#DashBoard

Hi Landon
The 64-bit Windows build of DashBoard switched to using Microsoft Edge for all <browser/> tags in Custom Panels as of DashBoard 9.5.0.  It does require the Microsoft WebView2 Runtime to be installed on the system (available by default on most windows machines or available here).

We have removed the 32-bit DashBoard build from the Ross Video website and made it available upon request (though it will still target Internet Explorer). 

Hope this helps.

James

------------------------------
James Peltzer
Ross Video
------------------------------

Original Message:
Sent: 02-06-2023 17:16
From: Landon
Subject: Specify Dashboard Browser

I had the same experience as described by Brandon.  If it could be placed on the project roadmap for DashBoard to support the Microsoft Edge WebView runtime natively - instead of IE - I think that would be extremely helpful going forward.  We have some internal tools that use the new WebSockets features which don't work with the IE engine and it would be awesome to display these within the DashBoard grid file directly.

In doing a bit of research I don't think it would be too difficult to roll this out, from what I could determine trying to reverse engineer the implementation, the builtin browser runs as a Java app within C:\DashBoard\IEProcess.jar which is a class that implements the Eclipse SWT browser widget.  It seems like the capability to use various browser engines is already available for use... the FAQ from the Eclipse website states: "To specify that an Edge renderer be used by a Browser instance, create it with style SWT.EDGE (since 4.19) or set the Java property org.eclipse.swt.browser.DefaultType=edge."

So this makes me wonder if it might be possible for the developers to add a DashBoard preference item which controls the aforementioned style or the DefaultType property.  That might be an easy way to get us a modern browser environment within the <browser> widget.

------------------------------
Landon Gaus
KTRK

Original Message:
Sent: 03-10-2021 18:16
From: Brandon
Subject: Specify Dashboard Browser

Shawn, 

That is a major bummer. Might be worth putting in a ticket about it. I know there is already one in their backlog for a chromium base, but more voices might make for more urgency.  

I'm guessing you tried the <webget> tag as well and that is sorta the only other way around it that i'm aware of without making your own api.  

I hope you find a solution my dude. 

#DashBoard

Hi James
That is fantastic news!  Having the ability to use a modern browser will help a lot going forward on our end.  Thanks to you and the team for making this happen.
Regards

------------------------------
Landon Gaus
KTRK
------------------------------

Original Message:
Sent: 02-08-2023 11:28
From: James
Subject: Specify Dashboard Browser

Hi Landon
The 64-bit Windows build of DashBoard switched to using Microsoft Edge for all <browser/> tags in Custom Panels as of DashBoard 9.5.0.  It does require the Microsoft WebView2 Runtime to be installed on the system (available by default on most windows machines or available here).

We have removed the 32-bit DashBoard build from the Ross Video website and made it available upon request (though it will still target Internet Explorer). 

Hope this helps.

James

------------------------------
James Peltzer
Ross Video

Original Message:
Sent: 02-06-2023 17:16
From: Landon
Subject: Specify Dashboard Browser

I had the same experience as described by Brandon.  If it could be placed on the project roadmap for DashBoard to support the Microsoft Edge WebView runtime natively - instead of IE - I think that would be extremely helpful going forward.  We have some internal tools that use the new WebSockets features which don't work with the IE engine and it would be awesome to display these within the DashBoard grid file directly.

In doing a bit of research I don't think it would be too difficult to roll this out, from what I could determine trying to reverse engineer the implementation, the builtin browser runs as a Java app within C:\DashBoard\IEProcess.jar which is a class that implements the Eclipse SWT browser widget.  It seems like the capability to use various browser engines is already available for use... the FAQ from the Eclipse website states: "To specify that an Edge renderer be used by a Browser instance, create it with style SWT.EDGE (since 4.19) or set the Java property org.eclipse.swt.browser.DefaultType=edge."

So this makes me wonder if it might be possible for the developers to add a DashBoard preference item which controls the aforementioned style or the DefaultType property.  That might be an easy way to get us a modern browser environment within the <browser> widget.

------------------------------
Landon Gaus
KTRK

Original Message:
Sent: 03-10-2021 18:16
From: Brandon
Subject: Specify Dashboard Browser

Shawn, 

That is a major bummer. Might be worth putting in a ticket about it. I know there is already one in their backlog for a chromium base, but more voices might make for more urgency.  

I'm guessing you tried the <webget> tag as well and that is sorta the only other way around it that i'm aware of without making your own api.  

I hope you find a solution my dude. 

#DashBoard