<A HREF="http://cjos.sourceforge.net/redist/srcserv1d/org.jos.app.calculator.index.html">org.jos.app.calculator</A> <A HREF="http://cjos.sourceforge.net/redist/srcserv1d/org.jos.app.cmdline.index.html">org.jos.app.cmdline</A> <A HREF="http://cjos.sourceforge.net/redist/srcserv1d/org.jos.app.editor.index.html">org.jos.app.editor</A> <A HREF="http://cjos.sourceforge.net/redist/srcserv1d/org.jos.app.editor.plainText.index.html">org.jos.app.editor.plainText</A> <A HREF="http://cjos.sourceforge.net/redist/srcserv1d/org.jos.app.network.whois.index.html">org.jos.app.network.whois</A> <A HREF="http://cjos.sourceforge.net/redist/srcserv1d/org.jos.app.timetracker.index.html">org.jos.app.timetracker</A> <A HREF="http://cjos.sourceforge.net/redist/srcserv1d/org.jos.app.timetracker.gui.index.html">org.jos.app.timetracker.gui</A>
|
|
The cenralization of JOS-related applications is bad practice. Adding "app" to the name of a package is both misleading and impractical. It is misleading because any package might contain one or more applications. Adding "app" to its package name does not make it an application package. Removing "app" does not prevent it from being an application package.
It is impractical because applications can be developed by anyone, not just members of this project. An alternative practice is strongly recommended by Sun Microsystems. To prevent unnecessary collisions, each developer manages their own part of the namespace with their name on it.
An application might require more than one package. All packages belonging to an application should be stored together. In order to identify all kinds of applications, a separate index is required. Namespace is not enough. Centralization does not make it any easier to search for applications. Even a JOS-specific application should go inside its own package. -- GilbertHerschberger (31 August 2000).