[Vm-dev] what to do with old carbon based plugins?

David T. Lewis lewis at mail.msen.com
Sat Mar 26 18:28:50 UTC 2011


On Sat, Mar 26, 2011 at 03:18:45PM -0300, Esteban Lorenzano wrote:
> 
> 
> El 26/03/2011, a las 3:10p.m., David T. Lewis escribi?:
> 
> > 
> > On Sat, Mar 26, 2011 at 12:39:06PM -0300, Esteban Lorenzano wrote:
> >> 
> >> Hi, 
> >> I started to build some needed external plugins (they are being build with Cocoa CogMT)... but I found some plugins still using carbon lib (SerialPlugin, MIDIPlugin)... and also, there are some others (B3DAcceleratorPlugin) who I didn't include it because uses carbon very intensively. 
> >> 
> >> So, I wonder how to proceed with this plugins? 
> >> I would like to have a "carbon clean vm", so I prefer to gently ask to the plugin owners to rewrite their sources to not use carbon. 
> >> 
> >> What do you think?
> > 
> > Hi Esteban,
> > 
> > I think that these issues are in the platforms support code, so I fear
> > that the plugin owner might be you at this point ;-)
> 
> ouch!, I was afraid someone would say that :)
> yes... I can help, but sometimes (for example for the B3DAcceleratorPlugin) it needs some work/understanding... and it will take some time to achieve a full list of plugins running (in other cases, the work is easy... and of course, not all plugins needs carbon lib. 
> So, now... I wanted to have the plugins Matthew ask for (no other reason that he asked for them... :) and then move the others plugins as soon as I have time... 
> 

That sounds like the right approach to me :)

Also, you will find that for things like SerialPlugin or MIDIPlugin,
there are other people in the vm/squeak/pharo community who may have
a specific interest in these plugins, and who may be able to help.

Dave


> 
> > 
> > I'm afraid that I am not knowledgeable about OS X development, but I
> > know that in many cases John has been able to adopt code from the
> > unix platforms tree for things like this. Maybe other people with
> > OS X expertise can volunteer to help also?
> > 
> > Dave
> > 


More information about the Vm-dev mailing list