I encourage everyone to make sure Adobe knows we’d like a better approach to stage instances.

dude ive been saying this for years: Flash should take a cue from .NET…

Anything on the stage is added in code in the .as file. Anything removed from stage is removed from the .as file. Nothing should be magically compiled into the swf and NOT added to the .as file for all to see as well.

I HATE how the stage and class are separate and treated with different rules.

for me though im a purist trapped in a pragmatist body (or the other way around, i forget). So I ALWAYS declare my movieclips but i have a small team and can enforce standards.

However, if your dealing with designers that just need to get things done outside of your influence, you can’t spend your time purifying their code. So I saw do what works best for you at the time.

also, and i haven’t touched the project panel since it never really worked for me EVER. it be nice if settings like that where in a standardized project.xml file so flash, fdt, flex etc could read and handle it to avoid the toggles between different users, ides, prefs, evil monkeys, etc.

-erik

What they should have done (and still should do) is make it so you can declare stuff in the class, and if you check the box in Flash to do it for you, it doesn’t complain about it, and instead says “Obviously we have a designer and developer working together here.”

I don’t see how it would be so hard to have an option to auto-declare turned on and also allow you to declare what you need. I’m so tired of seeing Adobe post lame ideas like “How do we make the Actions window better?” How about making the Flash IDE Compiler better first?