Your approach makes the most sense for now. Once V6 is released, then porting may make sense if you want your scripts to run on Mac. If you are only concerned with Windows, then continuing to use WinForms will work just fine in V6.
We have a admittedly very poor port of WinForms for Mac which really isn’t worth considering for the long run. Even WinForms on Windows is showing it’s age and some areas like high DPI support are still being fixed by Microsoft.
We probably won’t have a visual editor anytime soon, but we are hoping to have some sort of previewer over time where you can immediately see the UI update as you type. I’m also hoping (now were talking about code that doesn’t even exist yet) to create a python package that makes working with Eto much more “pythonic”.
I think the ListBox is what you are looking for as a replacement for System.Windows.Forms.ListView
Sure (https://github.com/picoe/Eto/wiki/Controls). A Form is modeless and a dialog is modal
This is implemented in an assembly we ship named Rhino.UI. I’ll need to figure out how to make this easily callable from python