Re: [Rails-devel] rails-package rails.ui.swing SVG revenue

[Erik V. <eri...@hc...>]

> rails-package:
> 
> >We have not discussed this before, and I like the idea of putting
> >rails in 
> >front of all package names. 
> ...
> >That seems good. If you send me a patch for just moving and renaming
> >the 
> >existing GameTest, I'll apply that.
> 
> OK - you will get a RailsMain under rails, witch will 
> integrate the rest of
> the GameTest, which is not in RailsMain yet.
> 
> Moving existing code to a different directory has a main 
> drawback in CVS.
> You will have a break in History. 
> That is one of the reasons, why many people are changing to 
> SVN (SubVersion
> http://subversion.tigris.org/ ),which is developed by the 
> same main peoples,
> who have develop CVS. 
> I know, that you can use SVN under Souceforge, but I don't 
> know how you can
> switch to it under Sourceforge. I have convert some 
> CVS-Projects into SVN -
> easy doing.
> If we don't change, we should discuss some other possible 
> layout changes
> also, so we will have this break not to often:

A move to Subversion might be a good idea, 
but I don't know either how to do that, 
nor what it would mean for how I'm currently working with Eclipse
(see below).
 
> project-directory-layout:
> I'm using maven (http://maven.apache.org/ ) as a build &
> site-generation-tool. 
> They have a clear project-dir-layout
> (http://maven.apache.org/guides/introduction/introduction-to-t
> he-standard-di
> rectory-layout.html ).
> We do not need all dirs by now, but there are good reasons, 
> why many people
> use this layout in general, even if thy don't use maven or 
> even know it.
> Have a clear devision between different code-languages, resources,
> configurations and documentation makes it easer for new developers,
> spezially, if you use a common layout.
> Separation of test- and main-code makes it easy to build a 
> smaller jar,
> without the testing-overhead.
> If you want, I can move the project into the maven layout at 
> this weekend,
> including eclipse project files and you can have a look at it.
> To make it clear: I don't want to use maven at this project, just the
> dir-layout. At my company-projects, we are using maven just for the
> morning-checkout, for the test automatisation on the 
> Development-Server and
> to build the project websites overnight. The last two, we 
> don't have at
> rails and the first think is perfect done by the Eclipse 
> CVS/SVN-Plugin.
 
With all these proposals, what is most important for me is
what all these changes would mean for the way I work with Eclipse.
With some trouble I have achieved a working relationship with Eclipse,
and I don't really have a picture how that will change with such a new
layout.

I suppose you'll have to provide some instructions on how to restructure
my Eclipse project. 

As of now, Brett and I don't even use the same .project file
(I've put mine in .cvsignore). That may have to change.

One minor thing is, that the hierarchy will get a lot deeper,
which makes dealing with the (narrow) Navigator view a bit more
difficult. But that's no big deal.

Perhaps it is all worth a try.
 
Erik.