Ultrashock Forums - View Single Post

Nutrox · 2008-03-20 #2

Package names can be anything you want, but it is good practice to base the package names on a domain name structure especially if you intend to distribute any classes in those packages. In a nutshell it helps to avoid conflicts between two classes with the same name. Adobe are actually starting to do that now with their com.adobe.* package, I use com.neondust.*, and you might use com.holaso.* if you have the holaso domain name.

I think Macromedia/Adobe used the flash.* and fl.* package names because it makes things a lot easier when manually typing the package names in Flash, plus those classes are the core classes of the application. If I made a huge application called Fishy then I would probably just use the fishy.* package name instead of using com.neondust.fishy.*

Hope that makes some kind of sense.

	Nutrox 17 Creative Assets	2008-03-20 #2
	Package names can be anything you want, but it is good practice to base the package names on a domain name structure especially if you intend to distribute any classes in those packages. In a nutshell it helps to avoid conflicts between two classes with the same name. Adobe are actually starting to do that now with their com.adobe.* package, I use com.neondust., and you might use com.holaso. if you have the holaso domain name. I think Macromedia/Adobe used the flash.* and fl.* package names because it makes things a lot easier when manually typing the package names in Flash, plus those classes are the core classes of the application. If I made a huge application called Fishy then I would probably just use the fishy.* package name instead of using com.neondust.fishy.* Hope that makes some kind of sense.