Your map looks very nice. Maybe you could write up something describing what you modified and what your approach has been.
Xwt and MonoMac assemblies are both included with Xamarin Studio. I don't know how (or if) Xwt is used in Xamarin Studio since it does not include any templates for creating an Xwt solution.
If anyone is interested in testing Xwt, copy and paste the sample code give in the Hello World app (https://github.com/mono/xwt), changing "ToolkitType.Gtk" to "ToolkitType.Cocoa".
Copy MonoMac.dll, Xwt.dll and Xwt.Mac.dll to the same folder as your test code (eg, test1.cs).
Compile: mcs -r:Xwt test1.cs
Create app bundle: macpack test1.exe
Copy dll's into bundle: cp -p *.dll test1.app/Contents/Resources
Now double click the .app in Finder to run it. It won't have a menu, but at least you can see that Xwt works.
I've worked with cross-platform UI toolkits before. They always look great at first and the ability to easily target multiple platforms with the same codebase, yet adapt to each platform's UI conventions, can seem pretty exciting. At first, that is. Then you realize they're incomplete, or that some of the cross-platform widgets don't behave the same across all platforms, or that the toolkit's development is very slow - and suddenly one day you realize you're no longer solving your own app's problems, but spending most of your time solving the UI toolkit's problems. Then everything becomes very depressing and very sad all at once.
Xwt appears to be exactly that kind of toolkit: incomplete, maybe untested, practically unsupported by either developers or users (take a look at how few forum posts or commits in the last 6 months).
Another approach would be not to try to salvage the DotSpatial WinForms UI stuff, but to create a new set of "DotSpatial" controls based on MonoMac. Then you don't have to worry about maintaining compatibility with other platforms and the WinForms users don't have to worry about sudden instability introduced in what they're using.
DotSpatial apps have a very conventional look and feel to them that would have looked perfectly fine 10 years ago. The menus, the toolbar, the gigantic dialog boxes that have so much stuff in them that they need tabbed inputs, etc. Junking most of that on the Mac side would provide a way of starting with fresh ideas. For example, look at how different this new Mac-only IDE looks compared to conventional IDE's: http://www.remobjects.com/elements/fire/
Note that my thinking is that the few Linux desktop users would probably be okay with a WinForms UI.
Thanks.
-Phil
Xwt and MonoMac assemblies are both included with Xamarin Studio. I don't know how (or if) Xwt is used in Xamarin Studio since it does not include any templates for creating an Xwt solution.
If anyone is interested in testing Xwt, copy and paste the sample code give in the Hello World app (https://github.com/mono/xwt), changing "ToolkitType.Gtk" to "ToolkitType.Cocoa".
Copy MonoMac.dll, Xwt.dll and Xwt.Mac.dll to the same folder as your test code (eg, test1.cs).
Compile: mcs -r:Xwt test1.cs
Create app bundle: macpack test1.exe
Copy dll's into bundle: cp -p *.dll test1.app/Contents/Resources
Now double click the .app in Finder to run it. It won't have a menu, but at least you can see that Xwt works.
I've worked with cross-platform UI toolkits before. They always look great at first and the ability to easily target multiple platforms with the same codebase, yet adapt to each platform's UI conventions, can seem pretty exciting. At first, that is. Then you realize they're incomplete, or that some of the cross-platform widgets don't behave the same across all platforms, or that the toolkit's development is very slow - and suddenly one day you realize you're no longer solving your own app's problems, but spending most of your time solving the UI toolkit's problems. Then everything becomes very depressing and very sad all at once.
Xwt appears to be exactly that kind of toolkit: incomplete, maybe untested, practically unsupported by either developers or users (take a look at how few forum posts or commits in the last 6 months).
Another approach would be not to try to salvage the DotSpatial WinForms UI stuff, but to create a new set of "DotSpatial" controls based on MonoMac. Then you don't have to worry about maintaining compatibility with other platforms and the WinForms users don't have to worry about sudden instability introduced in what they're using.
DotSpatial apps have a very conventional look and feel to them that would have looked perfectly fine 10 years ago. The menus, the toolbar, the gigantic dialog boxes that have so much stuff in them that they need tabbed inputs, etc. Junking most of that on the Mac side would provide a way of starting with fresh ideas. For example, look at how different this new Mac-only IDE looks compared to conventional IDE's: http://www.remobjects.com/elements/fire/
Note that my thinking is that the few Linux desktop users would probably be okay with a WinForms UI.
Thanks.
-Phil