LiveDocs Comments - flash - 9.0 - main - 00000033.html

flash/9.0/main/00000033.html

Joe ... Ward — 2008-08-08T10:40:34

The package both organizes your classes, and in the case where two class names are the same, provides a mechanism for distinguishing between them. The full class name is really package.Class, but the import statement allows you to use just the class name in your code. If you were using two classes that had the same name from two different packages, you would have to use the full package.Class syntax whenever you referred to them in code.

You can think of a packages as directories and subdirectories of class files (and in fact that is how the compiler finds the source files). Each segment of the package name between the dots is a directory. The class at the end is the file defining that class. Using "*" in an import statement is like using a wildcard when listing a directory, all the classes/files in that directory are included. So when the classes in the flash.display package was compiled, the compiler looked for the classes in the following directory structure:
flash/
display/
MovieClip.as
Sprite.as
...

Yes, packages are more fully explained further on. They have to be mentioned here since the package statement is required to get a class to work.

flash/9.0/main/00000033.html

Todays Past — 2008-07-31T15:11:43

Okay, you lost me. The whole thing seems very buried to me and I need some help to climb out.

Why do you need the "Package" statement? What's so special about what it does?

In a single Package{} there should be only one class defined?

Can there be multiple Package{}'s in a single .as file?

Is there a naming restriction on the Package Name, the class name, the file name - is there a relationship between them?

This question comes from previously on page 28 where you stated

"Use the import statement to specify the full name of the class, so the ActionScript compiler knows where to find it. For example, if you want to use the MovieClip class in ActionScript, you first need to import that class using its full name, including package and class:

import flash.display.MovieClip;

Alternatively, you can import the package that contains the MovieClip class, which is equivalent to writing separate import statements for each class in the package:

import flash.display.*;"

I'm assuming this all ties together, but I'm confused about how.

BTW - If the answer is "please see page 41" which I have not done yet, then let me propose that this section be enhanced, eliminated, or worst case include a forward reference, because too many questions/answers are being forward referred.

All was said with a smile on my face and a song in my heart.

flash/9.0/main/00000033.html

2007-12-01T13:42:54

I think you need to add "this." in your eventlistener to make it work.

flash/9.0/main/00000033.html

LPCpatrick — 2007-05-31T13:10:38

Having issues with calling private methods from event listerners inside custom classes. Is there something I am missing or any documentation on this?

ex.

package {
// imports
class MyExample extends Sprite {
// propreties and constructor....
xmlLoader.addEventListener(Event.COMPLETE, myXMLHandler)

private function myXMLHandler(evt:Event):void{
// dostuff to XML doc and call other function....
myOtherFunction()
}
private function myOtherFunction():void{
// do something with some propreties
}
}
}

results in : 1009 error.

thanks

flash/9.0/main/00000033.html

djtechwriter — 2007-04-23T14:39:21

Only one class per package, but you can add classes within the same file outside the package declaration. For more details see this section:
http://livedocs.adobe.com/flash/9.0/main/00000041.html

flash/9.0/main/00000033.html

philggg — 2007-04-22T14:09:36

What is the relationships between:
.as files
packages
classes

Can there be more than one class in a package?