What do you find to be best practice when it comes to writing AS code to manage a big app ?

Question

Right now I am considering 3 options:
1) I write all the code in a root component that extends group for example like this:
<s:Application>
     <s:AppGroup>
               <s:List />
     </s:AppGroup>
</s:Application>
So in it I will write the code to manage the list. Ok but Imagine now I have 10 views inside that AppGroup each having a list which needs to be managed. So here comes my option 2.
2) I write code in the AppGroup component to manage what's on it's level and for new level (view for example) I create another component like ViewGroup1, ViewGroup2 etc which extends group or something else and I write code in it to manage what's inside of it. This looks like this:
<s:Application>
     <s:AppGroup>
          <s:ViewGroup1>
               <s:List />
          </s:ViewGroup1>
          <s:ViewGroup2>
               <s:List />
          </s:ViewGroup2>
     </s:AppGroup>
</s:Application>
So this time the code to manage the views will be in AppGroup and the code for managing the Lists will be in the ViewGroup1/2 component.
3) of course sometimes mixed architecture if for example the ViewGroup1 is very simple and doesn't have list but a label or something like that the code could be written in the AppGroup.
What do you think of this code structure? Is my logic good or there's something else considered a best practice at the moment ? Thanks!

Answer 1

Thank you all for the thoughts. Could we please stick to flex only for now...
Currently I have a project where I see this structure:
<Application creationComplete="init();">
     <fx:Script source="MainApp.as" /> - all initialization code is here
     <components /> - many components
</Application>
In the creation complete of the Application which is in MainApp.as, dataProviders are set and a controller class is initiated to which the Application is passed as Object and everything is manipulated from that controller. As you mentioned I guess you can always create additional controllers and pass them the Application or some other components from which they could start controlling so to speak.
I am not sure if this structure is good or not, I started comparing it with mine and I ended up here...
What I see at this point compared to mine is that:
- in the included MainApp.as in Application I have question marks when i type something like "stage" in a function, I needs me to type "this.stage", which I don't like. To me it looks like including is bad and maybe everything should have started with creationComplete in the Application mxml with importing and initiating the controller with passing him the Application right away. Is that correct?
- in the example given above, after MainApp initiates the controller by passing him the Application, the controller looses all of the nice code hints since now the Application is an object... maybe it's wrong for it to be object ? Should it be something else?
Compared to my approach when I separate my logic into AS Group which is then extended as MXML Group. All I have to do is declare the instances in AS which I have as IDs in MXML and voila... I can control them and write their logic with all the nice code hints present.
So basicly at this point you say instead of extending Group in AS every time I want to separate logic, write a controller right ?
Here is what I summarized for now:
1) Create a RootController class
2) Initiate it in the creation complete of the Application passing the Application (as what type - object or something else?)
3) manage all logic in that controller
4) if parts of the application are too complex they can be separated into additional controllers.
5) the RootController can initiate SubControllers which can initiate SubSubControllers
6) to all controllers a component must be passed as a starting point for the logic
Is this correct? If yes, what about the code hinting compared to my approach?
Would be very nice if someone of you could make a very very very simple app with the model you are talking about, or if you have an article you took it from share the link! Thanks!