Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought


Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Pages: [1]
Print
Author Topic: package naming conventions  (Read 3364 times)
Neil Manuell
Courseware Beta
Sr. Member
***
Posts: 109


View Profile Email
« on: July 24, 2008, 02:15:55 »

Ok, I'm writing a set of utilities for pureMVC

and I wanted opinions regarding packages, and the best practice.

at the mo, my packages are name like this:

uk.co.revisual.puremvc

so all my code implemented using pureMVC is in this package. Is this acceptable, and easy to port to other peoples class libraries without too much confusion?
« Last Edit: July 24, 2008, 04:13:27 by fleecie » Logged
puremvc
Global Moderator
Hero Member
*****
Posts: 2871



View Profile WWW Email
« Reply #1 on: July 24, 2008, 04:46:09 »

If you plan on distributing and maintaining the utilities on your own site, then of course, this will be fine.

If you'd like to contribute them to the project, then you'll need to repackage according to the naming conventions you see with the rest of the PureMVC demos and utilities. See the post in the Contributor Central board for more info about this.

-=Cliff>
Logged
Neil Manuell
Courseware Beta
Sr. Member
***
Posts: 109


View Profile Email
« Reply #2 on: July 24, 2008, 04:53:07 »

ok, cool, I didn't realise I could contribute so easily.
Will get my project up to scratch first
:~)
Logged
Pages: [1]
Print