We've had many customers engage with us over the years to fund projects, and this funding allows our team to grow temporarily to expedite a feature.
There's also the option of fast-tracking less demanded features and guaranteeing their inclusion into future releases through a custom development project.
That said, we know it needs to be addressed eventually, so we're considering adding WebView2 support to the roadmap for VAST 2023. Understandably, we needed to prioritize other updates and fixes that apply to more of our customers. We've been aware of this upcoming IE and OLE issue and have considered including a solution in past releases, but we found that less than 1% of our customer-base have voiced a need for this feature. WebView2 is certainly the better option though.įor further context about this feature's inclusion in VAST: There is also a commercial ActiveX component, named WebKitX, that could be used. Thanks for taking the time to write this post.Ī WebView2 integration for VAST is the best path forward. Has anyone done this, or have other suggestions? My client can't be the only ones dependent on this OLE control. They see Smalltalk as obsolete, and this IE issue tends to confirm that view. That would be a major effort, and the client doesn't want to invest further in this application. Bite the bullet and rewrite the application as thin client in Seaside.
But I'm not much of a C++ programmer, and don't know if it's even possible to integrate WebView2 into VASt.
0 kommentar(er)
