This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Embedded browser in M-Files Desktop Client

Hi,

I was using Craig's app to show Power BI report in M-Files desktop client - it is shown in the right pane, where the metadata and preview tabs are. The problem was that the report was running really slowly. Our development team developed our own app for showing the Power BI report inside M-Files. The reports were still running slowly. We found out the problem is the IE, which is embedded into the M-Files desktop client (correct me, if I'm wrong).

If I open the report in Internet Explorer, it also runs slowly. If I open the report in any other browser, it runs as it should.

Is there a way to change the embedded browser in M-Files desktop client?

Best, Uros

Parents
  • The app isn't mine. Wink

    It was initially done by someone else within M-Files, but it's available as an open-source sample on the GitHub repository.

    To answer your question though: not currently.  We are looking to replace the web browser component with the new WebView2 component that has been released by Microsoft, based on the Chromium engine.  This work is not a simple swap though, unfortunately.  I hope to be able to talk more about this early next year but, at the moment, your options are limited.

    One thing you could do is to alter the sample application so that it creates a button or context menu item which, when clicked, opens the user's local web browser (via ICommonFunctions.ExecuteURL).  This means it's not embedded directly within M-Files, but it does mean that the integration will use whatever browser they have available and thus run better.

Reply
  • The app isn't mine. Wink

    It was initially done by someone else within M-Files, but it's available as an open-source sample on the GitHub repository.

    To answer your question though: not currently.  We are looking to replace the web browser component with the new WebView2 component that has been released by Microsoft, based on the Chromium engine.  This work is not a simple swap though, unfortunately.  I hope to be able to talk more about this early next year but, at the moment, your options are limited.

    One thing you could do is to alter the sample application so that it creates a button or context menu item which, when clicked, opens the user's local web browser (via ICommonFunctions.ExecuteURL).  This means it's not embedded directly within M-Files, but it does mean that the integration will use whatever browser they have available and thus run better.

Children
No Data