[MonoDevelop] Missing Widgets

Rafael Teixeira monoman at gmail.com
Thu Mar 15 12:24:56 EDT 2007

I didn't say that the binding mechanism was tied to ADO.NET, it is
used (implemented)  by ADO.NET but is defined below it, it is
basically in System.ComponentModel namespace housed in the System

So I think it is safe to use it for enabling databindness in GTK#. And
Monodevelop already messes with System.ComponentModel classes, exactly
in your ASP.NET-centered addins...


On 3/15/07, Michael Hutchinson <m.j.hutchinson at gmail.com> wrote:
> On 3/15/07, Rafael Teixeira <monoman at gmail.com> wrote:
> > Delphi now supports ADO.NET, and it's binding mechanism which is
> > similar but incompatible with Delphi's own. I think that writing GTK#
> > controls/widgets that accept the ADO.NET binding mechanism like the
> > ones we already implemented for WinForms and for ASP.NET(WebForms) is
> > easier to do and more consistent, as the programmer sees things in the
> > same way across all UI-toolkits, and uses the database tools already
> > available in the framework and in MonoDevelop.
> Bear in mind that GTK# is part of the parallel Free stack, so it
> should ideally avoid taking hard dependencies on technologies which
> are not part of the CLR/CLI/C# standard. I haven't checked but I'd
> assume it doesn't include ADO.NET.
> That said, there's no problem with creating a databinding library
> subclassed from the GTK widgets that uses ASP.NET. Alternatively GTK#
> could have some other kind of databinding mechanism built in with an
> ADO.NET adaptor made available to make things easier for people.
> --
> Michael Hutchinson
> http://mjhutchinson.com

Rafael "Monoman" Teixeira
"The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man." George Bernard Shaw

More information about the Monodevelop-list mailing list