[MonoDevelop] Planning MonoDevelop 1.0
christian.hergert at gmail.com
Sat Nov 25 12:59:44 EST 2006
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.
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.
the sql query view is pretty bad. most of the time i dont even know
what button to push to do what i want.
On 11/25/06, "Andrés G. Aragoneses [ knocte ]" <knocte at gmail.com> wrote:
> Christian Hergert escribió:
> > If we have until mid-January, I can make some time to make the
> > monoquery addin use reflection. I'd also like to add a couple of other
> > things before 1.0.
> > * turning your db queries into csharp code
> > * generate nhibernate mappings for your project
> > * graphical table builder
> > * possibly integrate into the project build process (lluis, if you
> > could put a quick doc together on how to do this that would be great)
> > * store configuration data in the solution
> > * generate classes from database structures
> This sounds awesome, Christian. BTW, I wonder if we could have
> codecompletion in MonoQuery too (something like this) but I suppose
> this could be very very more complex and long to implement. But it would
> be nice to have it in the roadmap for post1.0 :)
> Andrés [ knocte ]
> Monodevelop-list mailing list
> Monodevelop-list at lists.ximian.com
More information about the Monodevelop-list