Embedding dynamically generated website in VSW as an iframe

Marius Kreß

30 juillet 2025 07:49

We are currently moving from WebOffice to VSW. In WebOffice, we use webpages that are dynamically generated with PHP scripts, using a feature's ID that's handed over as a URL parameter as input. The resulting webpage displays some information in a table. We then embed this webpage into WebOffice as an iframe.

In a first version, I use “Open URL” to open the page, but it would be more comfortable for the users to have the page open e.g. in the sidebar instead of having to switch tabs.

3 years ago, someone asked a similar question, and was refered to this example. But this is a custom component, which is reasonable for a more complex use case (as in the example), but would add a lot of complexity for basically opening a URL.

Finally, to make this clear: I know that using an external PHP script is not a very elegant solution. Probably it's possible to get and display the information using a workflow and a form, which would be closer to the “philosophy” of VertiGIS Studio. But to speed up the transition to VSW, I would prefer to just change the interface for now and keep the old scripts in the background. Then, after the first release, I can switch these functions over to workflows/forms one by one.

0

• 

  Jasper Kroon

  31 juillet 2025 08:30

  This was one of our mayor missing points switching from the previous viewer to the current.

  We now have a custom flexible workflow build that is capable of opening a iFrame panel with an url based on the clicked feature. This opens up a big door of possibilities integrating all kinds of external information to the viewer without having to click to other tabs.

  Next wish on the list would be sending coordinates from the iFrame to the viewer. Working on it, but some good examples from Vertigis would help. I guess looking at the Esri widgets should explain some things.

   

  0
• 

  Marius Kreß

  31 juillet 2025 11:23

  Hi Jasper,

  thanks for your reply. Can you share this custom workflow with me, or is this not possible because it contains internal information etc.?

  0
• 

  Birgit Ligtvoet

  5 août 2025 13:00

  Hi Marius,

  Unfortunately Jasper forgot to add that the workflow also needs a custom built component to actually work. I think the workflow does contain some info we would need to remove but you would still need the plugin with the component itself so it would be quite useless.

  0
• 

  Marius Kreß

  6 août 2025 07:24

  Hi Birgit,

  thanks for the clarification. That's a pity, but thanks for the information. I'll talk to my colleagues about the best way to proceed.

  0

Vous devez vous connecter pour laisser un commentaire.