RE: [Xpipe-developers] 0.6 and Source Hierarchy re-org

[Sean M. <sea...@pr...>]

Bill,

Thanks for this. I've read about direct tweaking from the shell of
CVS files to keep history across renames but it not an option
using SourceForge.

Having said that (picture the bleary eyes), I've already reorganized
EVERYTHING. It has not been pleasant - such drudgery.

I'm also now using Java naming conventions for all class
and method names. It involved changing nearly every line of
code in the whole system, Java, Jython, XML, RNG - everything
was affected. I thought it best to do it now before a reorg became
beyond consideration.

Also, I've started a build.xml for ANT for building the distribution. (The 
mascot
for XPipe by the way is the Leaf Cutter Ant 
http://www.lpzoo.com/tour/factsheets/herps/ant.html
so use of the Ant building tool was of course obligatory.)

All code now revolves around xpipe.net. net.xpipe is the Java and Jython
package name for everything.

Much fun but not yet much new code as it has taken ages to get
everything working again after the reorg.

I have a simple XPipe model working. As soon as I can chain
some XComponents together and execute'em, I'm declaring
a 0.6!

Anon.

Sean

At 14:55 02/02/2002 +0000, =?US-ASCII?Q?Bill_de_hOra?= wrote:

> > Sean McGrath
> >
> > Having discussed source code hierarchy organization with David Starr
> > and others, and having had my
> > ears burned about Java Code Conventions from various quarters
> > :-), I have
> > decided to bite the bullet
> > and do a major code re-org around the domain name xpipe.net.
> >
> > CVS does not make it easy to rename files never mind wholesale
> > rearrange directory structures.
> > All the more reason to put a reasonable structure in place
> > now that can
> > last us into 1.0 and
> > beyond.
>
>There is a way to move files around a cvs repository and keep history
>(hard to tell whether this a feature of cvs or java package spaces), but
>you need to be able to work on the repository files (using cp) directly
>rather than go through cvs. But my understanding is that you can only
>access your source via cvs on sourceforge (I know one admin who's gone
>through pain more than once rejigging directories for java source).
>
>But strictly speaking java package spaces are a logical structure for
>controlling dependency and build; you don't _need_ to have a directory
>per package for Java source, but it's idiomatic to do so. I just ran a
>test with Ant (which is what netBeans uses) and it will compile Java
>classes from various package spaces stored in a single directory (it
>creates the corresponding directory structure of class files). If the
>package structure is in flux, maybe just leave the source in one
>directory for now (and honestly, who cares about idiom if it's holding
>you back?).
>
>Regards,
>Bill de hOra
>
>
>_______________________________________________
>Xpipe-developers mailing list
>Xpi...@li...
>https://lists.sourceforge.net/lists/listinfo/xpipe-developers

http://www.propylon.com