Why not just use a DataSet? Piers.
> -----Original Message----- > From: Tum [mailto:[EMAIL PROTECTED]] > Sent: Friday, September 20, 2002 8:56 PM > To: 'fssc'; 'mono-list' > 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > 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" <[EMAIL PROTECTED]> > > To: "fssc" <[EMAIL PROTECTED]> > > Cc: "Mono List" <[EMAIL PROTECTED]> > > 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 <[EMAIL PROTECTED]> > > > > > > > > > > > > > > _______________________________________________ > > Mono-list maillist - [EMAIL PROTECTED] > > http://lists.ximian.com/mailman/listinfo/mono-list > > > _______________________________________________ > Mono-list maillist - [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/mono-list > _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
