[MonoDevelop] monodevelop-boo: What work lies ahead?
jdong at ubuntu.com
Tue Feb 10 11:08:44 EST 2009
Thanks for the quick reply, Lluis,
I will have to take a closer look at MonoDevelop's parser infrastructure and
also Boo's interpreter services and see what's a better approach. Definitely
loading assemblies sounds like the easy way out but it gets ugly pretty
On Tue, Feb 10, 2009 at 10:22 AM, Lluis Sanchez Gual <lluis at novell.com>wrote:
> > I've been a long-time user of Mono/MonoDevelop and just recently
> > discovered Boo. I noticed that the Boo support in MonoDevelop 1.9.1 no
> > longer has autocompletion support, and was wondering if there's
> > anything we can do to help.
> Thanks a lot for your interest. The code completion engine and MD's
> parser service api have undergone important changes in the past months
> and the Boo add-in has not been updated to use the new api. Migrating
> the code to use the new API shouldn't be too hard.
> However, the big problem of the Boo add-in is that it loads project
> assemblies into the MD process, and that should never be done. IIRC the
> parser provided by Boo and the Boo console load assemblies, so that has
> to be changed.
> > I noticed an earlier posting  to the list asking for help with the
> > project, and if time permits this term, I'd like to see if there's
> > anything I can do. My general question is, I guess, what work needs to
> > be done on the -boo plugin? I see that the parser needs some work for
> > code completion, and I also see that Boo uses GTKSourceView while the
> > other language support addins don't seem to?
> Boo uses GtkSourceView in the Boo console, which other languages don't
> have. It would be good to update the code to support GtkSourceView 2.0,
> so it can be built with recent linux distros which don't provide GSV 1.0
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Monodevelop-list