Today is Flex Camp Cleveland, an educational seminar targeted at someone starting out in Flex. If you’ve had some experience doing software development and are interested in building RIA’s, the entire Flex Camp series are really useful to attend.
The lineup of speakers is pretty impressive, including Ben Forta and Adam Lehman from Adobe, Kris Schultz and myself from Resource Interactive, Doug Pierce and Curtis Gayheart from WonderLab and Scott Andrews from DimpleDough. I’ll be giving a more detailed event report when it’s over, however for the time being I will post my presentation assets here for download.
| Source Code | [Digger.zip] |
|---|---|
| Presentation | [Flex Camp Presentation.pdf] |
First, thanks for providing source code!
There is an issue, after importing the zip of the source code into Flex Builder 3,
the source code throws an error on import.
Is libs a custom library you’ve created? Or, can we redirect it somewhere in the Flex code library?
Thanks!
Actually, the libs directory describes a folder that the compiler will read for any additional precompiled libraries. Good examples of this are practically anything that has a .swc extension- drop them into the folder, and the compiler has access to any classes contained within.
Having said that, to resolve your bug you need to right-click on your project and select properties, then select Flex Build Path on the left and Library Path at the top. Within this screen you can manage where the compiler looks for these directories, and since the Digger application doesn’t require any you can go ahead and delete the reference to “libs”.
Michael, great job today. Just got back into Columbus. Had a fun day. Continue to have a great time at RI.
Ben Forta warned about dashes in XML.
E4X treats them as subtraction operators.
So what’s the work around?
Hello world!
This doesn’t work…
{xmlService.lastResult.data.first-child.second-child}
This was suggested by the Adobe Flex team [http://www.nabble.com/e4x-Dash-td16386671.html]…
{xmlService.lastResult.data.descendants(“first-child”)}
which may work for one child but not more…
{xmlService.lastResult.data.descendants(“first-child”).descendants(“second-child”)}
I also tried this…
{xmlService.lastResult.data.eval(“first-child”).eval(“second-child”)}
Any suggestions? Thanks
The best practice is not to use dashes, or any other basic inline mathematical operators, in favor of camelCase resource identifiers.
The workaround… well, I tried a few things but wasn’t able to come up with something immediately. If I have time in the morning I’ll give it another go.
I have no control over the structure of the XML in this case. Also Castor [Java object to XML package] uses dashes as the default. A property of String firstName in Java becomes a [first-name] node via Castor. Of course you can change this.
What about name spaces in XML, like an [content:encoded] node from a WorpPress RSS feed?
This doesn’t work…
{xmlService.lastResult.data.content:encoded}
If you want to start playing around with XML Namespaces, take a read through the QName class. It may, in fact, be what you’re looking for.