Aller au contenu principal

A VertiGIS Studio Web Roadmap (sort of)

Épinglée En avant

Commentaires

37 commentaires

  • Gareth Evans

    Hi Steve Schunzel that article now lives here: Is feature X that was in GVH available in VSW yet? – VertiGIS 

    Note this new URL is due to our transition to our new VertiGIS Community.

    Re: a comparison matrix of VertiGIS vs Esri solutions, I'm not aware of one though I can certainly see the need.

    2
  • Cam Barnard

    Steve Schunzel ... missed that one in the comment stream. Updated link is: 

    https://support.vertigis.com/hc/en-us/community/posts/11497803083154-Feature-Comparison-Matrix-Is-feature-X-that-was-in-GVH-available-in-VSW-yet-

    This one is also pinned at the top of the community posts since it is often referenced. 

    No comparison matrix comparing all four viewer frameworks exists that I'm aware of, you are right that would be a big endavor. I think one of the reasons you don't see something like this is that it would be inherently 'tool/feature' focused when the decision making criteria between those frameworks should be about more than just its current list of features.

    Examples that come to mind.

    GVH/Web AppBuilder are both based on Esri's JavaScript 3.x API, building a new app with those is fine if what it provides solves your problem today, but investing custom development in either would be an investment in a soon to be end of life technology from Esri.

    Framework considerations is another area. Both VSW and Experience Builder are based on Esri's JavaScript 4.x API, and both can be extended using VertiGIS Studio Workflow so for many cases you could use either and they look similar. VSW starts to shine when you begin to wrestle with larger framework considerations. What if you need to internationalize your application? What if your application is public facing and needs to be WCAG AA accessibility compliant? What if you want a SaaS application, but you also want to add some of your own custom modules to it. VSW handles those three scenarios well, while Experience Builder can't really handle any of the three (at least today).

    Finally, I encourage people to think about history and track record. Compare the 'mature' version of GE/GVH to the 'mature' version of Web AppBuilder. Part of our core business at VertiGIS is supplying a really great viewer framework with as many out of the box tools and capabilities as possible to help folks build great apps. We don't generally stop until we've achieved that. I'd argue that Web AppBuilder stopped far short of that. To be fair, it appears that Esri is continuing their investment in Experience Builder (more so than they did in Web AppBuilder) but I'm pretty confident that in 12-24 months when you put VertiGIS Studio Web and Experience Builder side-by-side you'd prefer to use VertiGIS Studio Web. For us, it is CORE to everything we do. For Esri, it is one of many, many things that they are working on.

    Cam

    2
  • Steve Schunzel

    @..., Cam Barnard  Thank you both for the quick, thoughtful replies!  It's very helpful.  We're fortunate to have all these tools available to us, but some of our folks aren't familiar enough with ExB and VSW so I was hoping create some sort of guide for them.  I think the best solution will be for them to just jump in.  Your comment about VSW being at the core of what you do is spot on and together with fantastic support is a huge advantage that I'll be sure to mention.

    0
  • Ted Cronin

    I would say just have them Jump right in and use the forums for questions.  There is a VSW class they can attend as well.

    1
  • Cam Barnard

    Updated post to reflect state of Web at 5.26

    0
  • GIS-Admin PM

    Hi there,

    when will be [soon] COGO editing Workflow (Theme 4 – Feature Editing) available?

    Kind regards

    Christoph

    1

Vous devez vous connecter pour laisser un commentaire.