I don't have a suggestion right now, but just in terms of why this might not elicit a response from the flex community, this isn't a flex question. It's a UI question that is the same question if you're talking about building a UI in flex, HTML, Java, .NET, etc etc.
I don't think there are going to be any flex-related insights to solve the problem. Figure out a good way to display that many form fields, regardless of what frontend technology you're using, and it will work. So this isn't very helpful to answer you're question, but maybe it explains why flex developers aren't jumping at replying. On 2/24/07, gotgoose09 <[EMAIL PROTECTED]> wrote:
I guess no one here has had this problem before? --- In [email protected] <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! :) >
