35 fields? peanuts :) We did one that is variable here... anywhere from 50 to 200. Basically the way we tackled the problem is to display a 3 pane view divide like so: left pane: displays section names in a list, when u select one, it populates the middle pane middle pane: displays the fields in a section as list of name/value pair right pane: display the field info with the appropriate control to edit the data (its more complex than that, but u get the idea Dimitrios Gianninas RIA Developer Optimal Payments Inc.
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Doug McCune Sent: Saturday, February 24, 2007 1:32 PM To: [email protected] Subject: Re: [flexcoders] Re: Best way for editing massive amounts of data? 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] <mailto:[EMAIL PROTECTED]> > wrote: 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! :) > -- WARNING ------- This electronic message and its attachments may contain confidential, proprietary or legally privileged information, which is solely for the use of the intended recipient. No privilege or other rights are waived by any unintended transmission or unauthorized retransmission of this message. If you are not the intended recipient of this message, or if you have received it in error, you should immediately stop reading this message and delete it and all attachments from your system. The reading, distribution, copying or other use of this message or its attachments by unintended recipients is unauthorized and may be unlawful. If you have received this e-mail in error, please notify the sender. AVIS IMPORTANT -------------- Ce message électronique et ses pièces jointes peuvent contenir des renseignements confidentiels, exclusifs ou légalement privilégiés destinés au seul usage du destinataire visé. L'expéditeur original ne renonce à aucun privilège ou à aucun autre droit si le présent message a été transmis involontairement ou s'il est retransmis sans son autorisation. Si vous n'êtes pas le destinataire visé du présent message ou si vous l'avez reçu par erreur, veuillez cesser immédiatement de le lire et le supprimer, ainsi que toutes ses pièces jointes, de votre système. La lecture, la distribution, la copie ou tout autre usage du présent message ou de ses pièces jointes par des personnes autres que le destinataire visé ne sont pas autorisés et pourraient être illégaux. Si vous avez reçu ce courrier électronique par erreur, veuillez en aviser l'expéditeur.
