You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The /app_direct/ verion of the Shiny Application does not show the loading message in contrary to the /app/ version.
/app/:
The time it takes to load the application is the same, but while /app/ shows you the following message, the /app_direct/ will not show anything until the application loads up.
/app_direct/:
Is there any reason for now showing the startup message in /app_direct/ ?
Thank, you, Dylan
The text was updated successfully, but these errors were encountered:
The /app/ version is an HTML page created from the app.html template - the loading screen is a javascript call from that template. The /app_direct/ version is the raw shiny app, which is then iframed into the /app/ template.
It's indeed correct that no loading screen is shown when using the app_direct endpoint, this is the intended behavior. The idea of this endpoint is to integrate it in some other application and then also create your own loading page.
Since ShinyProxy 2.5.0, you can now also load an application with the sp_hide_navbar=true query parameter. For example:
This still uses an iframe to load the application and therefore also displays the loading animation, however, the navigation bar is hidden. I hope this option is a good alternative for the app_direct endpoint.
Since I think this issue is solved now, I'm closing it. Feel free to open a new issue if you encounter any problem.
The
/app_direct/
verion of the Shiny Application does not show the loading message in contrary to the/app/
version./app/
:The time it takes to load the application is the same, but while
/app/
shows you the following message, the/app_direct/
will not show anything until the application loads up./app_direct/
:Is there any reason for now showing the startup message in
/app_direct/
?Thank, you, Dylan
The text was updated successfully, but these errors were encountered: