Application High Level Design

Ask a Question related to Macromedia Flex General Discussion, Design and Development.

  1. #1

    Default Application High Level Design

    I am building a registration form in Flex that could have up to 120 fields for
    the user to fill out depending upon what they select. They may not see some of
    the items.

    My thought is that I would have one registration class that has those 120
    items as variables?

    Then as each field gets updated, I would update that variable?

    Or do I somehow bind each field to each corresponding item in the class so
    that works automatically?

    Then when the user clicks submit, I would validate the required fields, then I
    would be posting all of the variables in that class to a hidden URL.


    If anyone could suggestions or terms to research within the forums, or better
    yet working examples of something that might be close to what I want to do, I
    would appreciate it.


    Thanks
    Mathias

    AwesomeDigital2 Guest

  2. Similar Questions and Discussions

    1. High-level question about ASP.NET web controls..
      I'm a bit of a noob when it comes to web controls... What I want to do, is create web control that appears in the toolbox, that one could drag onto...
    2. Different User Context returned in high volume application
      I have an asp.net application that uses windows integrated authentication to grant access to the site. When the default page loads, I grab the nt...
    3. Newby High Level Design/Architecture Question
      Hi there, Firstly, sorry for the cross post. I didn't get a reply on the dotnet.framework.webservices group so I though this group may be able to...
    4. Application level variables
      Christopher wrote: you need a permanent data store. usually available resources include text files, RDMS and code. global.asa is a good place...
    5. How to create top-level site/application
      Hum...am I missing something here. Seems like when I create a new web application in visual studio .net, it will put it at...
  3. #2

    Default Re: Application High Level Design

    You could use an <mx:request> tag nested inside your HTTPService tag that has
    bound vars to all fields, have the AS code decide which fields to show
    depending on the user's interaction (add some sweet transitions to show new
    fields too!) and then upon submit, validate and just send.

    So the code might look something like

    <mx:HTTPService id="myService" .......>
    <mx:request>
    <param1>{field1.text}</param1>
    <param2>{field2.text}</param2>
    </mx:request>
    </mx:HTTPService>

    General form goodness:

    [url]http://www.adobe.com/devnet/flex/quickstart/validating_data/http://www.adobe.com[/url]
    /devnet/flex/quickstart/validating_data/

    jinx82002 Guest

  4. #3

    Default Re: Application High Level Design

    Thanks Jinx!

    I'll give that a try.


    Mathias
    AwesomeDigital2 Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139