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

flash/9.0/main/00000041.html

unasuming_dave — 2008-04-30T15:27:57

In the "Creating packages" section it states "If you do declare variables, functions, or namespaces at the top level of a package, the only attributes available at that level are public and internal, and only one package-level declaration per file can use the public attribute, whether that declaration is a class, variable, function, or namespace."

Actually it seems that only one package-level declaration can be made at all, whether public or internal

flash/9.0/main/00000041.html

peterevensen — 2008-04-03T08:51:46

What isn't explicitly explained here (but is in the AS 2.0 documentation) is that:

1) Each package class has to be in it's own .as file and that file must be named after the one public class contained in that file (e.g., MyClass.as).

2) The .as files for each class in a package must be stored in a folder that matches the package name.

3) The folder containing the package folder must be in the ClassPath (either global or local).

This information is covered in Programming ActionScript 2.0, but not really explained here (and so easily missed by someone new to ActionScript who starts with AS3).

flash/9.0/main/00000041.html

2008-03-24T12:05:17

Hello, another somewhat confused user here...

I think I understand now. I'll give an example of my code, my conclusion from it, and my reflections on what that means:

I have the following file structure:

package/
package.as
Class.as

my intention was to have simple service functions in package.as that will be accessed via package.function(). for example package.initialize().

However, I kept getting compiler errors. I eventually tracked it down to this: you can only declare one public thing in a package - class, function whatever, and that something's name must correspond to the package name.

So I stopped getting compiler errors when I change my files and code like so:

package/
initialize.as - contains package.initialize()
Class.as - contains package.Class

At this point things started working.

However, you must realize this is less than desired. I don't want to be forced to breakdown a library of 10 small utility functions to 10 files. I could of course use static methods on a class, but that beats the whole point of using packages.

flash/9.0/main/00000041.html

tegnegi — 2008-02-23T10:55:26

I ve read the whole section but still can't get that packages can be created
that does not reflect directory hierarchy. Could you please suggest some example code.

flash/9.0/main/00000041.html

2008-01-08T03:07:28

I'm a relative newcomer to Flash but if anyone's having trouble getting packages and package names working, you could do a lot worse than check out this tutorial: http://www.actionscript.org/resources/articles/698/1/Make-your-own-reusable-classes-using-Flash-and-AS3/Page1.html

flash/9.0/main/00000041.html

djtechwriter — 2007-10-01T10:42:59

mgoodes,

You're asking about several different documentation issues. So, in the order you asked:

- This page in Using Flash should help:
http://livedocs.adobe.com/flash/9.0/UsingFlash/WS06D23361-54E6-4ac2-9D24-081C181BD2DF.html

Keep in mind that AS3 classes and packages are compiled by the authoring tool (in this case, Flash CS3, not FlexBuilder). So, the information you want is in the Using Flash book.

- Name them what you want, basically. Look through the AS3 Language Reference and don't name them the same as the ones included with Flash CS3. For simplicity, you can put all your classes at the "top level" as stated above. The names shouldn't spawn a compiler error unless your syntax is incorrect. It doesn't have anything to do with the names you use. This page may help:
http://livedocs.adobe.com/flash/9.0/main/00000028.html

- The new operator is documented here:
http://livedocs.adobe.com/flash/9.0/ActionScriptLangRefV3/operators.html#new

flash/9.0/main/00000041.html

mgoodes — 2007-09-29T19:35:22

Hmm...I've read this twice now, and amidst all the extraneous information I cannot find the things I really need to know:
- How do I name/organize my files and folders so that AS 3.0 can find them
- How do I name my packages/classes to avoid compile errors
- Where do I write the "new" statement - is it even possible to write a "new" statement in a frame without getting a compile time error?
I'm sure all the Java programmers are happy with this documentation but as an AS programmer I'm stuck using frame code because I can't get my packages and classes to compile.