On Thu, 2006-07-13 at 20:45 +0100, Alvaro Lopez Ortega wrote:
> Joe Shaw wrote:
>
> >> It is a very different situation. While the power manager support
> >> provides new functionality, GTK# would only provide duplicate
> >> functionality for another development framework that overlaps with
> >> GNOME.
> >
> > Perhaps I am misunderstanding, but this argument doesn't make any
> > sense to me.
> >
> > Gtk# isn't an application, so by itself it's not useful and doesn't
> > really duplicate anything. It does provide a native API to Gtk#,
> > but traditionally language bindings have been considered a strength
> > of GNOME. Gtk# calls into Gtk+, so it's not like we have two
> > competing implementations of the toolkit here. I don't see the
> > duplicate functionality here.
>
> My mistake, I didn't explain it correctly. What I meant was that the
> group of Gtk# plus Mono overlaps with a big chunk of the desktop. My
> understanding is that GNOME is a development framework and Mono is
> another one completely unrelated. Both of them have quite big class
> libraries: XML parsers, string management, asynchronous I/O, etc.
>
> Of course it is possible to use both of them for writing a single
> cool application, although it doesn't seem to be technically correct
> because of all the duplicate code: there would way too many unneeded
> possible failure points and wasted resources.
>
you are right, but what is so different with Mono that this wasn't
raised when Python was included?
--
Rodrigo Moya <[EMAIL PROTECTED]>
_______________________________________________
desktop-devel-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
