Configure and default mode drivers build

[/C=FR/O=CNRS/OU=UMR8607/CN=Laurent Garnier/emailAddress=garnier@…]

See mail thread : Rép : Configure script and Qt

Hi Laurent

I don't understand what you say. Perhaps what I said was not clear.
- You could have a QtVis without a QtUI (it's not beautiful, but it's working....)

Ah, o.k. I see what you mean - I'd previously thought that Qt Vis required Qt UI to be built - I was getting mixed up with the concrete classes of G4VInteractorManager, e.g. G4Qt, which are always built if one has something, a UI or Vis driver, that needs interaction with Qt/Xt etc.

- If you have a QtUI, you could have Xm,X, or Win32 Viewer without any problems, but the default one should be Qt.

It depends whether we want to set defaults for Vis drivers based off of the UI choices. It makes sense - and if you're able to build a UI, e.g. Xm, then there's no real reason *not* to build the corresponding Vis driver because being able to build the UI means all the external features needed are there.

Perhaps we should consider combining the questions, e.g.

"Do you want to enable building of Xm support for UI and Vis"

or something to that effect for the UI/Vis modules that use the same external package.

That's for building - I think there are other issues at the user level (the USE variables), but that can wait for the next release.


To be coherent, it should be the same case for all viewers ? Or perhaps we can do that in a major release ?

I agree with Gabriele's previous mail - it looks like a good thing to do and we should look at it for the next release!

Cheers,

Ben.

-- 
===============================================================================
Dr. Ben Morgan
Research Fellow
Department of Physics
University of Warwick
Coventry CV4 7AL
===============================================================================