4 ms·

For us the most attractive option would probably be to wrap yEd Live in Electron. We're not a large team and rewriting yEd with something else is a major undert

by ygra 7y ago

For us the most attractive option would probably be to wrap yEd Live in Electron. We're not a large team and rewriting yEd with something else is a major undertaking (especially for a tool given away for free). That makes it hard to justify development costs. Personally, I'm still hoping for Microsoft to see the need for a good cross-platform managed-code UI toolkit. Perhaps they're open to funding or adopting Avalonia. But perhaps that's just me being open to rewriting an aging Java application in C# ;-)

tannhaeuser 7y ago
Interesting. Btw I have an old half-finished Java Swing diagramming (not UML) app lying around waiting to see the light of the day in ... this millenium hopefully ;) Electron is surprisingly good-behaving and I get that it's of course attractive to develop mostly a web app that can also be deployed as desktop app, but isn't entirely without problems (for one, it isn't accepted in the App Store as it is). Things always look brighter on the other side of the fence, but throwing away your whole Java code base is kindof gross. Maybe we Java old schoolers could push JetBrains to open their Swing refactorings (of which I suppose there must be many) or sell their renovated Swing + Addons as a rich desktop appdev product. It's only in their best interest for Swing to have a future. And as IntelliJ shows, Swing isn't half bad a GUI toolkit in the hands of competent developers.