Hello, There was a very quiet period (mid-2010 to early 2011), mostly because I was working on the new bridge engine; as you can see the project is still active.
With the new 3.0 release, comes: - a new bridge engine. The engine has been designed for stability and a lower memory use. It will also be able to support 64 bits Mono when it become official. - a new wrapper generator. It makes the wrapping of frameworks easier. - new MonoDevelop addins (inspired from the Eric Butler'). I have added some refactoring options to simplify the implementation of informal protocols. What is coming: - The CorePlot framework binding. The framework is nearly wrapped, and I am working on the sample applications. - Xcode 4.0 support. Hope it helps. Regards, Laurent Etiemble. PS: I have cross-post on the user list, because this is where most traffic goes. 2011/4/5 Thomas Leppkes <tlepp...@jjk.de> > Hi, > > > > because of a email from Eric Butler I thought that MonoObjC isn’t further > developed (sry, shame on me !) > > > > [quote] > > Hi Thomas, > > > > The Monobjc Monodevelop addin is no longer maintained. > > > > I highly recommend using MonoMac ( > http://tirania.org/blog/archive/2010/Apr-19.html) instead of Monobjc in > general. > > > > Sorry for the bad news, > > - Eric > > [/quote] > > > > I converted my project to MonoMac but I had many problems/crashes > > (Ok. Monomac is on an early stage…) > > > > Today I saw that monobjc is updated to 3.0 and that are plugins for > monodevelop !!! yeepy J > > > > My question is should I go back to MonObjC ?? > > > > I think its much more stable !!! but , is it future proof ?? > > > > Any comment is welcome > > >