[MonoDevelop] Planning MonoDevelop 1.0

Lluis Sanchez lluis at ximian.com
Tue Nov 28 08:15:20 EST 2006

El ds 25 de 11 del 2006 a les 09:59 -0800, en/na Christian Hergert va
> I hacked together the separate db provider stuff yesterday and it
> seems to be working pretty well. I will commit that when i get back
> from holiday vacation.
> Lluis, since the new monoquery stuff will use reflection, do you think
> it would make sense to open up the AssemblyLoader stuff to generic
> addins? I think that would be nice to avoid the loading of bad
> assemblies into the appdomain and potentially crashing.

I'm not sure what you mean by "generic add-ins", but in any case I think
it should be ok to load ADO.NET providers into the MD appdomain.

> as for autocompletion, its not out of the question. if peter, lluis,
> and the others who have done it before could show a couple places i
> could start id be more than willing to check it out. the contextual
> parsing stuff will probably be the most time consuming.

There is some support for code completion in
MonoDevelop.Projects.Gui.Completion. You have to implement
ICompletionDataProvider (the object which will provide the completion
entries), ICompletionWidget (the widget when completion is applied, I
think there is already an implementation for Gtk.TextView), and then use
CompletionListWindow.ShowWindow to display the completion window
whenever you need.


More information about the Monodevelop-list mailing list