[Mono-list] Windows Forms...wah

[Tum]

I really don't understand why forcing MVC would be bad.

Writing models such as StringListModel would give the average programmer
not wanting to understand MVC (is it really that hard?) a familiar
interface to lists.

Perhaps we shouldn't have pushed VB programmers into the OO age with
implantation inheritance?

If we're going to introduce them to OO, lets do it right...


::Tum

> -----Original Message-----
> From: mono-list-admin@ximian.com [mailto:mono-list-admin@ximian.com]
On
> Behalf Of fssc
> Sent: Saturday, 21 September 2002 4:32 a.m.
> To: mono-list
> Subject: Re: [Mono-list] Windows Forms...wah
> 
> 
> I do not deny the usefulness of MVC, I've used it myself, but only
when
> the
> problem requires it. eg if you're linking a database table to a combo
then
> it's obviously critical. In many cases I think it's overkill. Case in
> point,
> in VS.NET when you want to populate a combo with a fixed set of
strings
> you
> simply use the items property list. You bearly have to use a brain
cell to
> do that, why go to all the bother of putting together a MVC?
> 
> > An example using VS.NET would be like this:
> >
> > +Drag-Drop the ListBox onto the form.
> > +Drag-Drop the ArrayListModel onto the form.
> > +Set the "Model" property of the ListBox to the ArrayListModel.
> > +Configure the ArrayListModel with the list of data you want.
> 
> If you do need to use a MVC on a listbox the option is there via the
> datasource property (doesn't have a model property).
> 
> Windows.Forms gives you the best of both worlds. My only issue with
> Windows.Forms is that it is still a bit immature compared to other
> toolkits
> but other than that I don't quite understand why people complain about
it.
> 
> I'm only thinking that it would be unfair to hoist one mode of
thinking on
> to every one else, when in fact we could have both approaches, then
you
> wouldn't alienate anyone. You'll get on board those who like to fiddle
and
> the rest who just want to get the job done. Critical mass is important
in
> a
> GUI develpoment community so that we get a vibrant group of people
> develpoing components. The Delphi and VB communities have a huge
developer
> base, the volume of ready made free and commerical components is
immense.
> Part of the reason for this is that it's easy to program in these
> frameworks, the environments allow one to develop on many different
levels,
> from simple drag and drop all the way down to assembler. Sure you can
do
> MVC
> if you want but if the problem is so simple, it's nice that you don't
have
> to.
> 
> Herbert