Roughly speaking, one operates main System.Windows.Forms.Form, and another one the main Mac-style menu, and some cross-thread code provides collaboration between the two. To develop such native interface, you can use another product, Monobjc:Monobjc — Wikipedia, the free encyclopedia,It's usage is much trickier for a Windows developer you should better understand native Mac development at least a little and it would be good to understand Objective-C, at least the basic ideas: Objective-C — Wikipedia, the free encyclopedia.This may be beyond your question, but I want to mentioned another, pretty exotic possibility: I experimented with Mono development on Mac and tried out the following unusual application architecture: I managed to create two separate UI threads, one running System.Windows.Forms.Application, and another one Mac OS X API application. Yes, but they won't be compatible with Windows. Even when you successfully develop correctly working Windows Forms application, it will look foreign on Mac in particular, you will see that the standard Mac menu on top of the desktop is shown as always, but is unrelated to your application, which may have it's own main menu, like in "normal" Windows Forms applications.Can you develop Mono applications to behave natively on Mac. If some code works well on Mono for Windows, additional problems with Mono for other platforms are much less likely.SharpDevelop — Wikipedia, the free encyclopedia,MonoDevelop — Wikipedia, the free encyclopedia,Now, more problems: Mono is good for many platforms, but Apple platforms is notoriously hostile to the "foreigners". This way, you can do essential inner development cycle on Windows only.
![]() ![]() ![]() Visual Studio Windows Application Code Provides Collaboration
0 Comments
Leave a Reply. |
Details
AuthorNick ArchivesCategories |