List Info

Thread: Planning MonoDevelop 1.0




Planning MonoDevelop 1.0
user name
2006-11-25 17:59:44
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.

-- Christian

On 11/25/06, "Andrés G. Aragoneses [ knocte ]"
<knoctegmail.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[1]) 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 
>
> Regards,
>
>         Andrés  [ knocte ]
>
> --
> [1]
> http://photos1.blogger.
com/x/blogger2/2083/1611/1600/150782/SQL_Prompt_Animated_Ima
ge.gif
>
>
>
> _______________________________________________
> Monodevelop-list mailing list
> Monodevelop-listlists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monodevelop-li
st
>
_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st
Planning MonoDevelop 1.0
user name
2006-11-28 13:15:20
El ds 25 de 11 del 2006 a les 09:59 -0800, en/na Christian
Hergert va
escriure:
> 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.

Lluis.


_______________________________________________
Monodevelop-list mailing list
Monodevelop-listlists.ximian.com
http://lists.ximian.com/mailman/listinfo/monodevelop-li
st
[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )