4 Replies Latest reply on Mar 21, 2008 6:31 AM by Gregory Lafrance

    General Capability Question

    Daniel Pride Level 1
      I am trying to evaluate flex for a possible application development using a number of tables and functions. I am concerned that in the Docs I read that a "Flex application is typically a single page" and that the appearance of pages is given by showing and hiding elements.
      Is it advisable to attempt to develop a complex application using Flex in Air as a front end for an Oracle or MySQL database or will the single page get overly complicated when you try to go from employees to inventory to orders to accounts???
      Thanks
      danielpride@yahoo.com
        • 1. Re: General Capability Question
          SujitG Level 2
          Hi,

          You can split your Flex applications in many ways. You can try using modules, using which you will load the part of the application only when required. You can also try view states, using which you can define different states of your application, so that you can switch between different states.

          Please find more details on view states at this URL: http://livedocs.adobe.com/flex/3/html/using_states_1.html

          For more details on using modules, please check out the URLs below.
          http://livedocs.adobe.com/flex/3/html/modular_1.html
          http://sujitreddyg.wordpress.com/2008/02/05/splitting-flex-application-into-modules/

          As you are connecting to your database from the flex application, you can may have a look at BlazeDS/LCDS.
          http://opensource.adobe.com/wiki/display/blazeds/BlazeDS
          http://www.adobe.com/products/livecycle/dataservices/

          Hope this helps.
          • 2. Re: General Capability Question
            ntsiii Level 3
            Yes, I think the "single page" stuff is aimed at HTML developers, to emphasize the fact that in a browser delivered app, one does not call urls (change "pages") to navigate.

            Flex apps are component-based. This applies to both the run-time DOM and the source code structure. (DOM and source-code structures are not necessarily related.) You structure source code for management purposes and you structure the run-time DOM for functionality purposes.

            Significant flex apps consist of hundreds, even thousands of source-files/components/Classes. At run-time these classes are used to renderer the application itself.

            As Sugit pointed out, there are many strategies for optimizing memory and download footprints, and run-time performance.

            Tracy
            • 3. Re: General Capability Question
              ntsiii Level 3
              Yes, I think the "single page" stuff is aimed at HTML developers, to emphasize the fact that in a browser delivered app, one does not call urls (change "pages") to navigate.

              Flex apps are component-based. This applies to both the run-time DOM and the source code structure. (DOM and source-code structures are not necessarily related.) You structure source code for management purposes and you structure the run-time DOM for functionality purposes.

              Significant flex apps consist of hundreds, even thousands of source-files/components/Classes. At run-time these classes are used to renderer the application itself.

              As Sugit pointed out, there are many strategies for optimizing memory and download footprints, and run-time performance.

              Tracy
              • 4. Re: General Capability Question
                Gregory Lafrance Level 6
                The single-page metaphor is the same as any application that has a single main window, where the contents of that single main window change based on what the user is doing at any particular time.

                So in a complex application as a front end for an Oracle or MySQL database when you try to go from employees to inventory to orders to accounts, with a single main window app you might select menu items or toolbar buttons that changes what is displayed in the single main window. Same in Flex. Using ViewStack, or modules, etc. you simply display what the user is currently interested in.