http://livedocs.adobe.com/ Macromedia LiveDocs - online documentation with user feedback. Copyright 2009, Macromedia, Inc. 2009-11-26T05:07:36 en-us http://livedocs.adobe.com/flash/9.0/main/00000034.html#86496 When importing packages, you can think of the package names as directories and, if you follow the recommendation of one class per file, you can think of the classes as files within the directory. (In fact, this is how the ActionScript compiler finds the classes.) <br><br>Thus the import statement: import flash.display.*<br>does not import a single "file" containing all the classes in the flash.display package. Rather, it imports all the classes in this package. These classes are still defined one per file. Joe ... Ward 1 1 2008-08-07T11:03:19 http://livedocs.adobe.com/flash/9.0/main/00000034.html#86309 Continuing down the lost path. <br /><br />You state that multiple classes per file is bad. But earlier pg28 you stated <br /><br />"import flash.display.MovieClip;<br /><br />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:<br /><br />import flash.display.*;"<br /><br />I'm assuming that flash.display has more then just MovieClip in it. <br /><br />Maybe you can use flash as an example of what good organization is, beyond the simple one file one class rule of thumb. Again assuming I'm understanding this at this time.<br /><br />Show us a more complex package/file that is "good" and explain why its good. Todays Past 0 0 2008-07-31T15:18:29