Flex 2 Training From the Source sample chapters available on Adobe's DevNet Site

Jeff:

I wrote to Peachpit three days ago asking about where to see errata; they replied saying that they were working on it and something should be available in about a week.

They also said to report any errors I might be aware of. I have seen what I thought were coding errors, but later turned out to be errors I made when doing the lessons in the book, and, since I am very new at this, I am reluctant to report anything directly to Peachpit. But here is something that you might want to look at:

Page 169 in 3, the paragraph after the function ‘Category()’ reads: “…. in this case, only the catName property had to use the this prefix because ….”.

But in the constructor, both properties are preceded by ‘this.’. I find this confusing: am I missing something, or should it read differently?

Carlos -

While both elements in the Category() function (also called a constructor) are prefaced with "this." the reality is that it was only required on one of the two (the catName property). In cases where the argument to the function is the same as the property name, you must preface references to the property with "this." to differentiate whether you are refering to the argument passed into the function, or the property of the class. In the case of catID, the classes property is called "catID", but the functions argument is "id" so the "this" prefix is optional. It was included as a stylistic choice, but the constructor would work just as well if it read

public function Category (id:int, catName:String) {
     catID=id;
     this.catName=catName;
}

If the "catName" argument were called something else, then the "this" keyword wouldnt be required for either, like this:

public function Category (id:int, cat:String) {
     catID=id;
     catName=cat;
}

Hello, Jeff –

From what I have seen so far, the book always says exactly what to do, no more, no less; it’s just that sometimes one tends to read more into something than necessary.

Got it! Thank you very much for the clarification.

Simultaneously with this, I have added a comment to the thread titled “INTERNATIONALIZING FLEX 2 APPS PT 2”. I have been having a tough time getting a function defined in the main MXML application to also work in Custom Components in the same project. In this new post, I describe the various things I have tried, with no success.

I would appreciate your looking at this to see if you want to help. I am even willing to pay for solving my problem, as long as the fee is not tailored to a big enterprise – I’m just a little guy, but have a project coming up for a small men’s fashion site, that will be in three languages to start with, and may end up expanding to six or more languages.

Thanks again,

Carlos

Jeff –

You probably want to look into what might be an erratum in the TFS code. I came across this while working on Lesson 8 – it may be a path issue, but I haven’t been able to figure it out:

When I run the Ecomm app, the horizontal display of categories does not show the images, but the missing image icons. So I ran the completed project; same result, with both the images in the categories display and the food items vertical display.

If you can run the project without getting that error, I would appreciate some kind of hint as to what I may be doing wrong.

Regards,

Carlos

Jeff –

You probably want to look into what might be an erratum in the TFS code. I came across this while working on Lesson 8 – it may be a path issue, but I haven’t been able to figure it out:

When I run the Ecomm app, the horizontal display of categories does not show the images, but the missing image icons. So I ran the completed project; same result, with both the images in the categories display and the food items vertical display.

If you can run the project without getting that error, I would appreciate some kind of hint as to what I may be doing wrong.

Regards,

Carlos

Great book. I've recommended it to my company. I'm still trying to get the itemrenderer to happen. But with the revision to add mx:script I'm now getting a parse error. Any thoughts?

Wayne -

What version of Flex are you running? 2.0.0, 2.0.1 or 3 Beta? The neccessary syntax is a bit different depending on which one you are using

hi, i have the problem :" parse error at <mx:script>". i'm use flex builder 3 b2, some idea thanks.

hello, i'm try this click="import valueObjects.ShoppingCartItem; outerDocument.removeItem(valueObjects.ShoppingCartItem(data));" and works in flex builder 3 b2... thanks anyway