Now for those of you who want to know what this forum is actually about...
Basically we felt a key part of the development process was lacking a place in the FlashKit forums, so here it is!
All too often the concepts for designing a good application, whether it be in Flash or not, are afterthoughts or not considered at all.
Often people just don't know that there's cleaner, more flexible way of working that someone else has already worked out the details for.
The aim of this forum is to help us all find out and get to grips with the various methods that are around for making the development process smoother, and ultimately more solid.
So far, this has all been a bit 'conceptual', so what are we really talking about?
Some examples of suitable topics for this forum might be:
Object Orientated Programming theory
Usability; designing applications with their use in mind
User testing methods
Obviously, these are just examples of things we aim to push this forum toward, feel free to discuss anything and everything you think fits in well!
I have been doing the design and architecture of total applications for a couple of years now and boy have I done some learning on the way! I have now taken to scouting around for how others do it to try and avoid re-inventing the wheel.
Architecture is just about the single most important aspect of application design - get it wrong and watch that deadline zoom up to you with horns and lights flashing!!!
Maybe we could kick off with a discussion on the planning process?
site check spec: ADSL (UK), PC P4 3Ghz, 1024MB RAM, Res: 1440 X 900, Player: Flash 9, WinXP Home, Firefox 2
dev spec: Flash 8 Pro, Flash MX 2004, Flash MX
well, as an animtaor, i'm used to thinking of my process in terms of trying to plan things out ahead of time to save myself pain in the long run. so i see two adjacent issues of "useability": that of the "end user" and that of... myself the "designer". i actually find the latter to be much more complex to plan for when engaged in larger scale, complex Flash projects. everyone's read (hopefully) at least a few things about "useability" as it pertains to the end user. ya know:
you make the navigation traceable, learnable, coherent, yada yada. you avoid mystery meat (in most cases).
but what about useability for the designer him(her)self? whew! that's where i hope over time i may learn some new things from all of you seasoned Flash gurus here at the KIT. it's a given that raw experience with the process of complex Flash design is the cornerstone of understanding usebility. but i'm really interested in learning new things about managing my Flash assets, in terms of setting up a successful approach that will allow me to most easily come back later and dynamicly update my assets. the intricacies of organizing multiple FLAs that get loaded into _levels. MCs that house alternate, non linear animation sequences.stuff like that. that's why when i look for books on Flash, i like the ones written by authors who share their particular process. most of the how to books just have the "push this button" approach, which doesn't really reveal anything deep about process... whatever ideas or input you have, i'd be all ears.