On 3/20/07, Karl Fogel <email@example.com> wrote:
> "Mark Phippard" <firstname.lastname@example.org> writes:
> > The problem is that for these files to "work" they pretty much have to
> live in
> > the root of what the user will checkout. That is the only place Eclipse
> > going to look for them and since they are needed to configure the
> > properly you need them right from the beginning.
> Hmmm. Let's get concrete: if you could put them right where you
> wanted them, without regard to anyone else using the tree, what are
> the exact files and where would they live? (If they're all under a
> .settings dir, for example, I doubt anyone would mind...)
At Max's suggestion on IRC, I am going to work up a sample.
There would be 2, perhaps 3 small files directly under trunk, and then a
.settings folder directly under trunk with a few more files in it.
Part of this is based on the idea of being able to use the Eclipse C/C++
tooling at least a little bit. I am evaluating that a little more to see if
it is at all worth it right now. For example, I want to see if I can
configure the editor so that someone does not have to fight against it to
write code that is formatted the way it is wanted. In the Java editor, this
is definitely the case, but in the C editor, not as sure right now.
So let me work this idea up a little further and come back with more solid
Received on Wed Mar 21 02:48:24 2007