[Mono-winforms-list] Why no longer using WineLib as base?

Paul Johnson paul@all-the-johnsons.co.uk
Tue, 23 Nov 2004 15:03:31 +0000


> I think, I have red, that you no loger use WineLib as foundation.

> It it right?

Sure is.

> What foundation do you use now? Gtk+ or something other?


> And why do you no longer use WineLib?

It was decided that using winelib was like trying to hit a moving target
and as it was too unreliable a solution, it was decided to write a
native implementation which calls a module to the underlying windowing
system - that means that as long as there a module for a platform, then
anyone with a port of the new SWF (it's actually Managed.Windows.Forms
now) on mcs can access it.

> It is so portable like Gtk+, Qt and so on.

True, but it's forever changing. GTK, Qt etc do bug fixes which are easy
enough to keep up with, winelib is under constant development which is a
different kettle of fish



"I'm gonna hit the highway like a battering ram with a Cilla Black fan on
the bike" - Meatloaf