I’m all for moving away from our GWT infrastructure, but I guess we have three important gaps to fill before we’re able to do that for the DMN Editor.
1. https://github.com/apache/incubator-kie-issues/issues/782 - IMHO this is a must-have feature that needs to be present on the new DMN Editor too. 2. https://github.com/apache/incubator-kie-issues/issues/171 - Also an important aspect that is currently only present on the DMN Editor (classic) 3. I don’t think we have an issue for this particular problem, but as long as we don’t have a SceSim Editor working for DMN 1.5, IMHO we can’t force users to depend on the new DMN Editor only and be forced to opt-out of SceSim entirely. Maybe we can layout a deprecation/removal plan for the next releases, provided we covered these three gaps I mentioned? Let me know what you think! Regards, Tiago Bento On Thu, Dec 12, 2024 at 7:30 PM Alex Porcelli <[email protected]> wrote: > Following our 10.0.0 release, I propose removing the legacy GWT-based > DMN Editor from our codebase. We currently maintain two DMN editors in > parallel - our modern implementation and the legacy GWT version. > > Removing the legacy editor would simplify our codebase and reduce > maintenance overhead. The code would remain accessible through git > history if needed for reference. If accepted, we would complete this > removal before our next release. > > Please share your thoughts. > > - > Alex > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
