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

[brett l. <wak...@gm...>]

> 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.
>


Rainer - I think this is the core problem I'm having with many of
these suggestions. Instead of learning how we've been working, and
doing it our way for a while, you're suggesting a lot of large,
drastic changes to accomodate your own preferences.

I think that we should focus more on reaching our existing goals.  So
far, I haven't received a patch for the first item you brought up (the
disclaimer) and now you're moving on to suggesting changing our RCS
and moving all of our files around and reworking large portions of our
architecture.


> 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.
>

Erik - Yes, this likely needs to find some common working default that
we can check in to CVS. Perhaps we should compare our .project files
and see why they're different. I think we might have done this before,
but I can't remember the results.

> 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.
>

I don't think it's all worth a try just yet. It seems like many of
things are big changes with questionable benefit and a definite impact
on our immediate productivity.  I don't want to stop development to
undertake any of these big changes just to come out on the other side
of it with minimal gains.

I think we're much better off taking smaller steps, and carefully
selecting which changes we make that either work well with our
existing methods or provide a definite, tangible benefit.

---Brett.