Comments on: Problem solved transferring typed objects to Flex

By: Gareth

Gareth — Wed, 11 Nov 2009 21:08:33 +0000

Glad to help. This one has been a frustration for me on a couple of occasions (after I forget that I really *do* know what the issue is )

By: Yannis Develekos

Yannis Develekos — Wed, 11 Nov 2009 20:22:45 +0000

OK. That saved the day for me! Thank you very much.

By: Nathan Levesque

Nathan Levesque — Thu, 15 Jan 2009 02:23:57 +0000

One last note, the above code I gave does the same as specifying the ‘includes’ option to the compiler, but allows you to have it right in your code instead of in a build script somewhere.

By: Nathan Levesque

Nathan Levesque — Thu, 15 Jan 2009 02:15:38 +0000

It’s an undocumented tag. You should be able to define a tag as a child of the tag and drop all your Frame metadata tags in there.

See:
http://livedocs.adobe.com/flex/2/langref/mxml/metadata.html

By: Gareth

Gareth — Wed, 14 Jan 2009 21:25:23 +0000

Looking at the documentation again, I’m not sure where the Metadata stuff goes. Is it in the class itself, and thus Flex “knows” to include that class in your build? I just haven’t been able to find anything specific about where to include the “Frame” information.

By: Gareth

Gareth — Wed, 14 Jan 2009 20:26:18 +0000

Hmm…hadn’t seen that one used before. So (after poking around a bit), I guess you just drop all of the classes in your application mxml page? Flex then knows to include those classes in the compiled code. I guess a benefit is that you don’t unnecessarily instantiate a class in your code. Any other reason for doing it this way?

By: Nathan Levesque

Nathan Levesque — Wed, 14 Jan 2009 19:09:00 +0000

You can also use the Frame metadata tag:

[Frame(extraClass="org.vega.FileInfo")]

just make sure you use the full package name in Flex