[Mono-list] Windows Forms...wah

[Seun Osewa]

Hi!

I don't know about designing something like swing ...
are we talking about something that looks the same way
on all platforms?  Something thatwould run slower on
target platforms (even though the speed would be
'acceptable')?  Something that would we would have to
convert people to?

I wouldn't say the mono effort should focus on such a
toolkit because, but for compatibility sake, we
already have gtk# (and qt# is in the works).  I don't
see why we would need something else.  I am not really
sure that many peope share your enthusiasm about
swing; the end user doesn't see the 'wonderful
design'.  What he sees is that: the program is
available on time (when he needs it).  it performs
well on his hardware.  If its 'ill-designed' but fast,
the application designer can always layer something OO
on top of it.  If its a standard that layer built on
top will be portable.

This is my own 2 kobo (about 1/140 of 2 cents ;) )

Just some thoughts.

bye!


--- code <code@263.net> wrote:
> 
> I agree with you. If there is a better GUI toolkit
> and it could run on
> most platforms, most people will use it instead of
> WinForm.
> 
> 
> > -----Original Message-----
> > From: mono-list-admin@ximian.com 
> > [mailto:mono-list-admin@ximian.com] On Behalf Of
> Tum
> > Sent: Friday, September 20, 2002 9:58 PM
> > To: mono-list@ximian.com
> > Subject: [Mono-list] Windows Forms...wah
> > 
> > 
> > Hi everyone,
> > 
> > Here are some of my thoughts on the state of GUIs
> and Windows Forms.
> > 
> > +
> > Windows Forms has very nice native controls.  It
> is fast, 
> > responsive but VERY POORLY designed.  It is only a
> thin layer 
> > about native windows controls.  Using native
> controls is 
> > *ok*, but they could have at least used the 
> > model-view-controller design pattern. The first
> thing I did 
> > when I started using Windows Forms was to write 
> > model/controller classes for lists and trees.
> > 
> > +
> > Swing is wonderfully designed.  It is the best and
> most pure 
> > OO UI class library out there.  It used to have
> major speed 
> > problems, but that hasn't been too much of an
> issue lately.
> > 
> > +
> > I really think that instead of porting
> Windows.Forms (which 
> > would be VERY hard), we should be thinking more
> along the 
> > lines of creating something similar to Swing or
> SWT.  A swing 
> > like implementation would be better as you would
> have more 
> > control over component drawing (and thus better
> support 
> > printing and UI capturing).  A designer plugin for
> VS.NET can 
> > easily be written to support the new toolkit.  I
> think the 
> > added bonus of being able to *reliably* port .NET
> GUI 
> > applications to .NET would encourage people to use
> the new 
> > toolkit over Windows.Forms.
> > 
> > +
> > If a swing-like toolkit was written, only a few
> native 
> > routines would be needed.  Drawing/blting
> (System.Drawing?), 
> > window creation and message/event dispatching. 
> This would be 
> > trivial to implement on Windows and Linux.  Most
> of the UI 
> > could then be written in portable managed code :D.
> > 
> > ::Tum
> > 
> > 
> > 
> > _______________________________________________
> > Mono-list maillist  -  Mono-list@ximian.com 
> > http://lists.ximian.com/mailman/listinfo/mono-list
> > 
> 
> 
> _______________________________________________
> Mono-list maillist  -  Mono-list@ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list

__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com