Hoppa till huvudinnehållet

Embed old AMD module in new vertigis studio web?

Kommentarer

2 kommentarer

  • Gareth Evans

    Hi Marc Rempel,

    I appreciate your proactive approach to reusing the old module in the new viewer. However, due to the significant differences between the ES module interface used by the new viewer and the AMD one used by the old viewer, a wrapper is unlikely to simplify this process.

    However, every challenge also brings an opportunity! This might be a great time to take a step back and reassess the functionality of this specific custom module. It's possible that revisiting its business use case could open up new, more efficient ways to achieve the same result, or even enhance it. Could you share more about what this module does?

    0
  • Marc Rempel

    Hi Gareth,

    Yeah, maybe an opportunity...

    We have a couple applications that we created pretty involved custom AMD modules.

    1. Aquaculture Financial Planning Tool:

    This is a popup module in the html viewer that lets a user choose from a couple types of aquaculture systems and change inputs dynamically to see estimated costs and gains of production. It uses a lot of the observables to bind interactions based on Excel spreadsheet that had the default configurations and formulas. 

     

    2. Watershed Restoration Area Reports:

    This is similar in that it handles a report in a popup module pulling in data from an external data api to show restoration projects over time and with charts, etc. We had tried using spatial data calls to do integrated charts in the viewer, but the performance and overall workflow was not suitable at the time so we used a preprocessed data queries to more quickly populate the reports.

    Happy to share code, but that might be too much in the weeds.

    -- Marc

    0

Du måste logga in om du vill lämna en kommentar.