# AS3 Project, Architecture

**URL:** <https://forum.kirupa.com/t/as3-project-architecture/324525>\
**Category:** flash\
**Created:** [August 25, 2011, 1:04pm UTC](https://forum.kirupa.com/t/as3-project-architecture/324525 "2011-08-25T13:04:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![remote](https://avatars.discourse-cdn.com/v4/letter/r/f08c70/32.png) [@remote](https://forum.kirupa.com/u/remote)\
**Post date:** [August 25, 2011, 1:04pm UTC](https://forum.kirupa.com/t/as3-project-architecture/324525/1 "2011-08-25T13:04:50Z")

</div>

The question will have hit this and other forums many times before and I sure have tried to consult existing resources to ease my confusion with AS3 project architecture, being used to working with (mainly procedural) PHP and new to AS3.

I am familiar with the very essentials of OOP (scope, classes, methods, inheritance) but fail to organize/structure my AS3 project in a way that does not leave me with a huge mess of dependencies and partly also very long classes that act all over the place.

I’d be greatful if someone could point me to a good primer on the subject. I dont need/want to read about all sorts of OOP design patterns just yet… so a dumbed down approach on how to bring some sanity in pure AS3 projects would be great.

Thank you,  
remote

- 

[SIZE=2]To give you an idea of what I need this for, let me briefly describe what the project consists of:

- a background with different states (image or video content)
- a GUI with two simple menubars
- an more complex, animated sub menu (similar to wp cumulus, but more complex in terms of content and events)
- ‘windows’ with the content that get added via either of the menus, these can be holders for html content, audio players and other content types.[/SIZE]\*