Native OS X port

Hello,

I have recently been very interested in seeing a native Mac
OS X port  
of MonoDevelop. Along those lines, I have begun hacking away
at the  
latest SVN source, rewriting the GUI code in Cocoa#. So far,
as a  
proof-of-concept, I have gotten the splash screen to come
up.

I would like to continue these efforts, and if possible,
contribute  
what I can back to the project. However, I am quite new to
all of  
this, and I'm not quite sure the best way to go about it.

Any pointers, tips, ideas, etc. you may have to help me get
headed in  
the right direction would be most appreciated.

Thank you,


Alexander Corrado
_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

Hey there Alex,

Please feel free to post your patches here and we'll help
you review
them.  MD is currently pretty tightly coupled to gtk#, so
having a
cocoa# front end will make for some interesting re-factors. 
I'd love to
help you with it, though, so please let us see the code that
you've
developed so far.

IMHO, we should de-couple the front end from the rest of the
features
and make a native Forms front end as well as Cocoa#. 
However, lluis and
the novell guys are already quite busy with their own work.

Anyway, I need to head off to the easter festivities, so
I'll stop
here 

Cheers,

C.J.


On Wed, 2007-04-04 at 00:15 -0700, Alex Corrado wrote:
> Hello,
> 
> I have recently been very interested in seeing a native
Mac OS X port  
> of MonoDevelop. Along those lines, I have begun hacking
away at the  
> latest SVN source, rewriting the GUI code in Cocoa#. So
far, as a  
> proof-of-concept, I have gotten the splash screen to
come up.
> 
> I would like to continue these efforts, and if
possible, contribute  
> what I can back to the project. However, I am quite new
to all of  
> this, and I'm not quite sure the best way to go about
it.
> 
> Any pointers, tips, ideas, etc. you may have to help me
get headed in  
> the right direction would be most appreciated.
> 
> Thank you,
> 
> 
> Alexander Corrado
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-listlists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-li
st
> 

_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

On 4/8/07, C.J. Adams-Collier <cjcolliercolliertech.org> wrote:
> Hey there Alex,
>
> Please feel free to post your patches here and we'll
help you review
> them.  MD is currently pretty tightly coupled to gtk#,
so having a
> cocoa# front end will make for some interesting
re-factors.  I'd love to
> help you with it, though, so please let us see the code
that you've
> developed so far.
>
> IMHO, we should de-couple the front end from the rest
of the features
> and make a native Forms front end as well as Cocoa#. 
However, lluis and
> the novell guys are already quite busy with their own
work.

Actually, Lluis has already done a lot of work to split out
the GUI
stuff into separate assemblies and namespaces where
possible, so that
MD can be used as a command-line tool without depending on
GTK#. The
problem is that a *lot* of the IDE is necessarily
GUI-dependent, and
there are limits to how much you can split out.

See http
://www.monodevelop.com/Architecture_Overview for info
about
the architecture: MonoDevelop.Core and MonoDevelop.Projects
should be
able to be used unmodified. Apart from that, huge chunks
will need to
be rewitten to make it natively Cocoa#. IMO it's important
to avoid
forking as far as possible, so any patches to improve the
separaration
cleanly would be much-appreciated.

-- 
Michael Hutchinson
http://mjhutchinson.com
_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st

Here is a patch with the code I've hacked at so far. MD gets
its  
splash up and then hangs.

>> MD is currently pretty tightly coupled to gtk#, so
having a
>> cocoa# front end will make for some interesting
re-factors.  I'd  
>> love to
>> help you with it, though, so please let us see the
code that you've
>> developed so far.

> any patches to improve the separaration
> cleanly would be much-appreciated.

I will try to help separate the gui-dependent code from the
gui- 
independent code as much as possible as I go through.
However I am so  
unfamiliar with the structure of MD that I am very hesitant
to change  
more than a few lines of code here and there.

At this point, I have just commented out the Gtk code and
swapped in  
the equivalent Cocoa# code. I guess there should be a
configure  
switch and preprocessor directives to select between Gtk and
cocoa?  
Or perhaps there is a better way?

Alex



On Apr 8, 2007, at 12:15 PM, Michael Hutchinson wrote:

> On 4/8/07, C.J. Adams-Collier <cjcolliercolliertech.org> wrote:
>> Hey there Alex,
>>
>> Please feel free to post your patches here and
we'll help you review
>> them.  MD is currently pretty tightly coupled to
gtk#, so having a
>> cocoa# front end will make for some interesting
re-factors.  I'd  
>> love to
>> help you with it, though, so please let us see the
code that you've
>> developed so far.
>>
>> IMHO, we should de-couple the front end from the
rest of the features
>> and make a native Forms front end as well as
Cocoa#.  However,  
>> lluis and
>> the novell guys are already quite busy with their
own work.
>
> Actually, Lluis has already done a lot of work to split
out the GUI
> stuff into separate assemblies and namespaces where
possible, so that
> MD can be used as a command-line tool without depending
on GTK#. The
> problem is that a *lot* of the IDE is necessarily
GUI-dependent, and
> there are limits to how much you can split out.
>
> See http
://www.monodevelop.com/Architecture_Overview for info
about
> the architecture: MonoDevelop.Core and
MonoDevelop.Projects should be
> able to be used unmodified. Apart from that, huge
chunks will need to
> be rewitten to make it natively Cocoa#. IMO it's
important to avoid
> forking as far as possible, so any patches to improve
the separaration
> cleanly would be much-appreciated.
>
> -- 
> Michael Hutchinson
> http://mjhutchinson.com


_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st