Are you planning work with modules? Or will you use this structure in a single flex project?
[]s. Ivan On Mon, Apr 19, 2010 at 2:55 PM, md_ars <[email protected]> wrote: > > > Hello, > > We are planning to use MATE framework for our project. We will have two > separate applications our main transaction application will have probably > over 150 screens and 100 reports. The application is mostly data driven and > we are using web-services to display and enter the data. I tested the MATE > frame work with one screen and it was easy to implement. Now I am trying > with one MENU and two screens and it is getting complicated to use shared > classes etc. Is the MATE framework good for our application? If yes what is > the best way to implement MATE? With two screens I am already finding tricky > to use Injectors. The main code structure of my project looks like as given > below. > > Main – Contains Application module > view > Forms – Contains screens based on panels/vbox or mdi window > Events - Contains main event map and following folders > Session – Events triggered from the screens. > EventManager – Parsing the data after session events fetched data through > web service. > ControlClass – Common classes used for screens etc. > > Should I use a common structure of the whole application or should it a > separate for each screen? To me it will be too messy to have common > structure whereas too tedious for each screen. So far team size is 2 and may > extend to 3. Please suggest an optimum way. > > Thanks > Ars > > > -- Ivan Perez -
