[Mono-list] Windows Forms...wah

[Tum]

Well, if it is that disturbing, you could always program the control to
insert and bind to a StringListModel by default.

The lack of "simplicity" of having to draw one extra component (ooooh
:P) will be overridden by the fact that you suddenly have a powerful,
flexible new way of populating and synchronizing the list.

Do we really want people to use the classic VB technique of using UI
components to store data?!  No!  Data should be stored separately from
the UI component.

The UI should never, ever store the data.  MVC allows this to happen...

With MVC you gain functionality and flexibility and only lose a little
bit of simplicity.


I think you'll be surprised at how many people would find it useful.
Everyone finds data-binding much more convenient than having to
populate/update controls manually.  MVC allows data-binding with
programmable, customizable non-database-like sources.


::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:34 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
> >
> 
> I meant to say 'simply', ie without having to put an extra component
down
> to
> represent the model.
> 
> Herbert
> 
> 
> 
> _______________________________________________
> Mono-list maillist  -  Mono-list@ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list