"best" is a slippery concept.
But what is your business reason for requiring editing through a pop-up? That is a lot of logic and user interaction just to edit a value, unless you have a powerful reason to do it. What don't you like about normal editing controls? Under your scenario, you will be updating the database on every field edit. Why do you want to do this? 35 fields in one view is too much. Break the ui up into logical business groupings and navigate them using a tabNavigator or ViewStack, or menu or tree or something. Tracy ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of gotgoose09 Sent: Saturday, February 24, 2007 1:08 PM To: [email protected] Subject: [flexcoders] Re: Best way for editing massive amounts of data? I guess no one here has had this problem before? --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "gotgoose09" <[EMAIL PROTECTED]> wrote: > > I'm web-enabling by using Flex 2 a project that has many fields for > each record in the database. A typical UI screen has upwards of 35 > fields in it. This application has to be easy to use. e.g. explained > over the telephone to customers who use it. > > I was thinking that one way to make editing fields consistent would be > to have the user double click the data field, popping up a window with > the right kind of input to edit the data, whether it is a TextInput, > TextArea, DateField, etc. Then, if the user presses the submit > button, the data would be saved to the database, but if the user > presses the cancel button, the data would not be saved and they would > return to the large form. > > Does anyone have experience in this type of application? Anyone have > their own opinion on the matter? > > Thanks in advance! :) >
