This may or may not be helpful, but I build my ActionScript 3 projects
in Flex Builder in a similar way, spare I only create the raw graphic
assets in flash and assemble them in the AS3. A contrived example
would be a 3 state button would be made of 3 embedded assets, and I
create the TextField in AS.  So there are no child MovieClips, sprites
or TextFields to reference that I my classes themselves don't create.
Understand, there's no good reason I do things this way, it's just how
I introduced myself to combining flash & flex/as3, but it does sort of
speak to your concern.

I've used another technique, though I'm not as happy with it. At the
day job, our artist creates the UI and ISD's create content in flash
-- but neither know much, if any AS3. I take the UI, Embed that in my
app and I create an instance of the controls and send each to a sort
of "Proxy" Class for each control type that handles all the logic for
the control. That way, I only interact with the "Proxy" -- the actual
on-stage instance is a private member of the Proxy passed into the
constructor.  Like I said, I'm not as happy with this technique, but
it's the most useful for handing our Instructional Designers a toolkit
they can use with little to no AS knowledge.

As far as the label & background being public, I say don't worry about
it. It's just not that big a break. I mean really, those pieces are
available via getChildAt(i) anyway, right? They have instance names?
Technically, they are already public.

Sorry, didn't mean to write a novel. Interested to see other's
opinions (specially where I'm wrong with this stuff - which happens
more than a little).

Jer



On Fri, Dec 18, 2009 at 4:30 PM, Henrik Andersson <[email protected]> wrote:
> Long story short, it must be public or else the Flash player can not set it
> for you. In practice isn't not a big deal. It's just something that people
> who cares about keeping things tidy and neat worry about.
>
> I am not saying that it is a bad thing, but I don't think too much about it.
> _______________________________________________
> Flashcoders mailing list
> [email protected]
> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
>
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders

Reply via email to