[Mono-osx] MonoMac.dll depends on System.Drawing.dll?

jmalcolm malcolm.justin at gmail.com
Fri Sep 10 11:11:56 EDT 2010

Miguel de Icaza wrote:
> Hello,
>>     Just so everyone knows: my intention is to turn System.Drawing into a
>> > fully operational stack that works with CoreGraphics instead of Cairo,
>> to
>> > simplify code sharing between platforms.
>> >
>> > Miguel
>> >
>> Miguel, does this mean that Windows.Forms would eventually be more
>> "native"
>> on the Mac?  I know that it is build on System.Drawing.
> Sadly, it would not any difference in that area.
> For Winforms to look more native a number of things need to happen:
> * Someone to write a "theme" engine that fits better with the Mac
> * Likely someone to do a Cocoa port to replace our Carbon code (not
> necessary, but would make a lot of things simpler).
> * New controls for Menus, these you would need to add to your app
> specifically to deal with the native system menus
> Currently, we at Novell are not planning on doing any of those.   If they
> happen, they will be community driven efforts.
> Miguel

Sorry, I guess "native" is a poor description of what I was asking.  I was
not expecting theming or menu placement.

I did assume though that if System.Drawing was rewritten to use CoreGraphics
that this would imply replacing Carbon with Cocoa.  My understanding was
that Windows.Forms used System.Drawing and so if System.Drawing (or even
just GDI+) was ported that Windows.Forms would just inherit that.  What else
needs to be done?  I guess I need to look at the code.

As for theming, is this just expanding the EnableVisualStyles stuff that you
already did for Windows.  As for the menus, I assume that something similar
could be done for Windows Forms as what was done for GTK# on the Mac.
View this message in context: http://mono.1490590.n4.nabble.com/MonoMac-dll-depends-on-System-Drawing-dll-tp2403556p2534600.html
Sent from the Mono - OSX mailing list archive at Nabble.com.

More information about the Mono-osx mailing list