Project Naming Convention
Project Naming Convention
- Subject: Project Naming Convention
- From: Lotsa Cabo <email@hidden>
- Date: Tue, 25 May 2004 18:14:38 -0400
My apologies for cross-posting. I posted this to the Java group and
then realized that the XCode project naming question should probably be
asked to the XCode group.
_________________________
I want to start port some resource components, that contain a library
of functions, from C# to Java. I am curious about the proper naming of
the project within XCode, the class file, the namespace, and how they
all fit together. What would you recommend?
For example, I want the following hierarchy when the components are
instantiated in the future...
MyName.MyLibrary.MyClass.MyMethod()
In .NET, I simply lumped them into one assembly (component) and named
it "MyName.MyLibrary.DLL". Since .NET only loaded into memory the
exact class that was instantiated, this was no big deal. However,
since Java does not work this way, I am obviously going to split them
all out. Unfortunate, since the class names are somewhat generic
(i.e., "Text", "Database", etc.), I would not want to have
"Database.jar" when I'm done.
Is it "proper" to use "MyName.MyLibrary.MyClass.JAR?" Is this even
allowed? Or, should I just prefix the resulting file somehow (i.e.,
"RText.JAR", "RDatabase.JAR", etc.)?
And, after all is said and done, what SHOULD the project be named in
XCode? Can I have one huge project for all of them or do I need one
for each component?
My apologies if I'm mixing terminology here.
R/S
Ryan
_________________________
Tired of spam? Signup for a FREE SpamJammer.Com account and say
goodbye to junk email forever!
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.