[vtk-developers] GUISupport directory ?

[Sebastien BARRE]

At 2/2/2005 07:19 PM, Moreland, Kenneth wrote:
> > Anyhow. Just my 2 cents.  My feeling was just that if
> > GUISupport/ is only for a couple of classes with restricted
> > licensing, then it probably belongs to
> > Utilities/GUISupport/QVTKWidget or more likely
> > Example/GUI/QVTKWidget.
> > This is a big tree already. I would guess a newbie looking at
> > the top dir would expect GUISupport/ to hold more GUI stuff.
>
>And so we go around in circles.  Clint was originally going to put
>QVTKWidget in Utilities, but decided to make a new directory based on
>the prompting of Brad King.

I think the level of the directory is kind of relevant too. I remember 
years ago we had a decent debate on how  and where we were going to put the 
top directory named Hybrid/ now. And from what I understand in a recent 
discussion in vtk-dev, the Patented/ top directory will be removed at some 
point, making things cleaner and leaner too I guess.

So, if it's only for a single small project with license constraints, then 
I don't think it should be a top directory ; in that case, I agree with 
Brad actually, Utilities/ would not be my first choice, but 
Examples/GUI/QVTKWidget would be. Unless you see bigger plans for this 
top-directory, in that case it sounds reasonable we organize and sub-divide 
it soon enough so that it does not help spreading the GUI confusion you 
noticed too, and people feel like it's a good/better place to put their UI 
work alongside yours.

Are those discussions outdated ? As we add more and more code, it sounds to 
me that we should pay attention as where we put things, how we can 
potentially use that opportunity to move/clean classes, or just lead the 
way for contributors. One of the things I hear very often from people 
approaching VTK is: "it's so huge, I can't find my way around, why so many 
classes/code, how do they relate to each other", etc. Directory structure 
helps a little bit.