[Mono-list] Windows Forms...wah

[fssc]

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


----- Original Message -----
From: "Tum" <tum@veridicus.com>
To: "'fssc'" <hsauro@fssc.demon.co.uk>; "'mono-list'" <mono-list@ximian.com>
Sent: Friday, September 20, 2002 8:55 PM
Subject: RE: [Mono-list] Windows Forms...wah


> Firstly, I think you'll find that most of the time you never need to do
> this because list boxes usually contain runtime data.  And when you have
> runtime data, the MVC shines because you never need to store and
> synchronize data in and between two locations.
>
> Anyway, of course you visually design MVC based controls.
>
> 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.
>
> This is actually more flexible.  If you ever want to replace the listbox
> with some other list control (like a combo box), you won't have to
> re-enter the data.  This can be quite a common occurrence and a source
> of frustration when using drag and drop IDEs.  Using MVC, the problem is
> solved.
>
> You could also support other drag'n'drop listmodel components like
> DataSourceListModel, XmlListModel, ResourceListModel etc...
>
> ::Tum
>
> > -----Original Message-----
> > From: mono-list-admin@ximian.com [mailto:mono-list-admin@ximian.com]
> On
> > Behalf Of fssc
> > Sent: Saturday, 21 September 2002 3:06 a.m.
> > To: mono-list
> > Subject: Re: [Mono-list] Windows Forms...wah
> >
> >
> > Many of use I'm sure come from visual ide development environments and
> > sometimes we just like to populate a drop down list visually, could
> one do
> > this with a MVC approach?
> >
> > Herbert
> >
> > ----- Original Message -----
> > From: "Rodrigo Moya" <rodrigo@ximian.com>
> > To: "fssc" <hsauro@fssc.demon.co.uk>
> > Cc: "Mono List" <mono-list@ximian.com>
> > Sent: Friday, September 20, 2002 10:44 AM
> > Subject: Re: [Mono-list] Windows Forms...wah
> >
> >
> > > On Fri, 2002-09-20 at 06:00, fssc wrote:
> > > > When you talk about model/controller classes would implement a
> list
> > box
> > say
> > > > as two separate entities, one to display the data and another to
> store
> > the
> > > > data? If so please don't, or at least give the option to go either
> > your
> > way
> > > > or as they have now. It's all very well bringing in comp sci ideas
> > like
> > this
> > > > but sometimes they just get in the way when you just want a list
> box
> > that
> > > > displays, say the days of the week.
> > > >
> > > then, you just have to write:
> > >
> > > ListBox lb = new ListBox (new ListModel ("Monday", "February", ...);
> > >
> > > but still have the model/view/controller separation, which is very
> nice
> > > for a lot of things.
> > >
> > > cheers
> > > --
> > > Rodrigo Moya <rodrigo@ximian.com>
> > >
> > >
> >
> >
> >
> > _______________________________________________
> > Mono-list maillist  -  Mono-list@ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-list
>
>