[Mono-osx] [MonoDevelop] State of MonoDevelop on the Mac

[Steve.Mentzer at lw.com]

In contrast, Monodevelop *is* worth my time. I am in awe about how
mature of a platform it has become... and wish I could do more to
contribute to making the os/x experience better.

Honestly, I wish it were a lot less kludge-like on OS/X, simply
because there are no other .net development tools (native UI or not).
I don't like to leave OS/X for any reason (other than integration
testing). Even transitioning to an XP instance in a VM is a headache.

Personally, it doesn't really bother me that MonoDevelop looks like a
winforms app on OS/X....   99% of the time, I am doing one of two
things in the IDE...  

1 - writing code or using a designer (winforms, asp.net)
2 - debugging

....Neither of which really benefits from native-UI integration all
that much. The menu placements, etc would make it a bit more seamless,
but certainly will not help the overall experience if the designers
and debuggers aren't working.

Good dialogue though!


----------------------------------------------------------------------
--------------------
----------------------------------------------------------------------
--------------------

Message: 4
Date: Mon, 23 Feb 2009 17:31:39 -0500
From: Duane Wandless <duane at wandless.net>
Subject: Re: [Mono-osx] [MonoDevelop] State of MonoDevelop on the Mac
To: mono-osx at lists.ximian.com
Message-ID:
	<d57001c10902231431j25b0c464p5f58085e9ef25181 at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

MonoDevelop is not worth my time.  It is very unstable on OSX.  The UI
metaphor is kludgy.  It looks and feels like a non-native Mac app.
I'd
prefer MonoDevelop practiced what I preach.  In my opinion there is no
good
cross platform *UI* technology.  If you have a Windows app, use
WinForms.
If you have a Mac app, use InterfaceBuilder.  Based on that assumption
(and
opinion), MonoDevelop should be developed using InterfaceBuilder for
the UI
with a C# backend utilizing one of the bridges.

This design is exactly what we implement for our cross platform app.
Two
native UIs, one common library.  Both apps look and feel great on
their
respective platforms.  So right now I have Win7 Beta installed on my
Parallels virtual machine.  I use Visual Studio there and Interface
Builder
on the Mac.  It requires one extra compile but the productivity of
Visual
Studio and the native look and feel thanks to IB are well worth the
extra
step.

Time is money.  The power of Visual Studio saves a lot of time.  If I
get an
Objective-C plugin for VS I would love that!  Never use XCode again.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.ximian.com/pipermail/mono-osx/attachments/20090223/27dc5a
22/attachment.html 
*******************************************************************************
To comply with IRS regulations, we advise you that any discussion of Federal tax issues in this 
e-mail was not intended or written to be used, and cannot be used by you, (i) to avoid any penalties 
imposed under the Internal Revenue Code or (ii) to promote, market or recommend to another party any 
transaction or matter addressed herein.

For more information please go to  http://www.lw.com/docs/irs.pdf
*******************************************************************************

This email may contain material that is confidential, privileged and/or attorney work product for 
the sole use of the intended recipient.  Any review, reliance or distribution by others or forwarding
without express permission is strictly prohibited.  If you are not the intended recipient, please 
contact the sender and delete all copies.

Latham & Watkins LLP