mxml layouts / HTTPServices

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

  1. #1

    Default mxml layouts / HTTPServices

    Hi,

    I am new to using Flex so I have a few questions that if anyone could answer
    that would be great!

    As far as I understand it .mxml files are like pages. What I would like to do
    is have a form on 1 'page' that when the form is submitted and the onclick is
    called to a HTTPService I would like the results to be displayed in another
    'page' as the layout will be different to the original 'page'.

    How can I achieve this?

    Also does anyone have any articles/books etc that I can use to learn about
    Flex and especially the HTTPServices?

    Many Thanks for your time.

    Al

    Muller2 Guest

  2. Similar Questions and Discussions

    1. passing variables from one mxml to anther mxml
      Hi i want to know about passing variables from one mxml file to another mxml file both will be different application or i want to call...
    2. How does on Sharing data between main.mxml and a renderer.mxml
      I have a value set in my main mxml file. public var calDate:Date = new Date(); How can I use this value in my renderer mxml file? if...
    3. Can I embed external MXML in another MXML file?
      Hi - I'm new to this so please bear with me. I'm trying to do something like you do in JSP's with a JSP include where I can import prewritten code...
    4. Regarding Httpservices
      Hi How to access the HTML browse control value through getUrl/ HTTP Service /RemoteObjects. Thank you
    5. Odd Shaped Layouts Requiring a Die Cut
      I recently started using InDesign and am unable to find a simple way to create a die line for the last page of a kit cover. Maybe I am going about...
  3. #2

    Default Re: mxml layouts / HTTPServices

    No, you misunderstand the Flex paradigm almost completely.

    If Flex there are no "pages", no "submits", no refreshes. Still with me?

    Flex is more like a Windows application. It stays alive in the browser, until
    the user closes the browser. Instead of "pages", think "screens" or "views".
    When the user performs some action(clicks a menu, button, a tab or a tree item,
    etc that requires the UI to change, you use one of the navigation containers
    (like ViewStack or TabNavigator) in Flex to present a different view.

    You call back to the server only when you need data and the data is returned
    in the background, the UI does not "refresh".

    Look at the sample applications that are installed with Flex Builder.

    Tracy

    ntsiii 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