Hi @ChillAndImprove,

Thanks for reaching out! I don't have much firsthand experience with this specific migration, but here are some insights that should help.

Previous discussions & challenges

Migrating the mxGraph GraphEditor demo to maxGraph has been discussed multiple times. You can check out these discussions for more details:

• #99
• #172
• #253
• #596

At this stage, the GraphEditor has not been migrated to use the maxGraph API. One possible blocker is that the Editor class, which GraphEditor may relies on, is currently not usable due to issue #367. This would need to be resolved before any serious migration effort.

How complex is the migration?

From past discussions, it's clear that this would be a large amount of work. Several people have looked into it, but no one has started a full migration yet. Personally, I don’t need all of GraphEditor’s features and don’t have time to work on this at the moment.

That said, GraphEditor is a great source of inspiration for customizations and learning how to extend maxGraph. Some of its features, like the "lazy zoom" feature (see this comment), could even be integrated into maxGraph directly.

Where to start?

A good entry point for understanding the demo is the Graph.js file, which is quite large (~350 kB). You could start by analyzing it to see how much of it can be adapted for maxGraph.

If you decide to go ahead with this migration, feel free to share your progress or challenges—we’d be happy to discuss and provide guidance where we can! 🚀

Thanks again for your interest! 😊