[Mono-devel-list] Windows.Forms schemes.
jay at lincore.co.uk
Wed Aug 27 15:05:46 EDT 2003
correction - dont know why i wrote that - > "swt is definetly worth
IMHO - #gtk is the best option for new gui development ? with themeing
for example : I like being able to run mysql control center with a motif
theme rather than a windows theme when on win2k
and there are probably others with the simmilar opinions.
Strictly sticking to a win32 visual style should not be the direct goal -
ease of development should be the goal and from what i know gtk and qt have
done well in there area for regular apps, and the bindings for #gtk already
What would be an interesting twist would be for qt to write bindings for c#.
windows.form is for compatibility with software built on the ms sdk
a thought - were trying to emulate windows.forms, to let code built on ms
run in mono. If we buld in mono and use #gtk , at the moment (i assume) gtk
needs to be installed on the target platform y/n ?
if (n) is the code in the #gtk wrapper smart enought to a) draw the widget
directly or b) make use of windows api. (ps on a seperate point drawing
directly would be better but that means reimplementing alot of what has
already been done in gtk - and would probably run slower)
if y : whats the problem ? - (retorical question)
PS - when deploying a c# application you would deploy the #gtk binding as
part of the application - hence extending the libraries available to the
Alternativly an "official" installer to install gtk and #gtk on windows is a
must have for effective app deployment.
----- Original Message -----
From: "Jay Bennie" <jay at lincore.co.uk>
To: "Miguel de Icaza" <miguel at ximian.com>; "Moore, Paul"
<Paul.Moore06 at ca.com>
Cc: "Thong (Tum) Nguyen" <tum at veridicus.com>; "Neil Cawse"
<NeilCawse at geotab.com>; <mono-devel-list at lists.ximian.com>
Sent: Wednesday, August 27, 2003 7:43 PM
Subject: Re: [Mono-devel-list] Windows.Forms schemes.
> swt is definetly worth continuing, as there is a need to be able to
> for platforms other than windows and swt or #gtk is probably the quickest
> route to a working solution.
> ----- Original Message -----
> From: "Miguel de Icaza" <miguel at ximian.com>
> To: "Moore, Paul" <Paul.Moore06 at ca.com>
> Cc: "Thong (Tum) Nguyen" <tum at veridicus.com>; "Neil Cawse"
> <NeilCawse at geotab.com>; <mono-devel-list at lists.ximian.com>
> Sent: Wednesday, August 27, 2003 5:51 PM
> Subject: RE: [Mono-devel-list] Windows.Forms schemes.
> > Hello,
> > > Its not simply a case of 'eventually the best solution will win' (or
> > > solutions).
> > Different people have different needs. You have outlined your needs.
> > > Some of us have to place bets now and changing horses late is a tough
> > > thing to do (look at #develop)
> > I would not represent it that way; I would represent it as #develop
> > having different goals than you do. The beauty of open source is that
> > if you care *enough* about a project, you are free to devote time and
> > energy into the direction you want.
> > > I don't care about p/invoke and windows procs, I am looking to create
> > > new apps. I just want a way to
> > >
> > > A) write portable GUI code
> > > B) painlessley if possible (ie a GUI designer)
> > > C) that uses (not looks like) the native widgets
> > If those are your needs, then from the documented I posted your options
> > are SWT or wx.NET.
> > Miguel.
> > _______________________________________________
> > Mono-devel-list mailing list
> > Mono-devel-list at lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list