[vtk-developers] Re: GUISupport directory ?

Clinton Stimpson clinton at elemtech.com
Wed Feb 16 18:16:43 EST 2005

Mathieu Malaterre wrote:

> Clinton,
>     Does the MDI, SDI and Dialog sounds familiar to you in Qt terms ? 
> Or is this only a MFC thing ? 

MDI's SDI's and Dialogs definitely exist in Qt.  But, MFC and Qt differ 
For MFC, some feedback seems to indicate that it is easier to use 
specialized widget classes for the application type.
For Qt, a generic VTK/Qt widget is much easier to use.

>     Ingo, are you sure with MDI, SDI and Dialog you went thought all 
> possibilities. Won't there be redundancy in between those projects. I 
> would assume you could reuse the same generic VTK-MFC windows at least 
> as a super class. I would like to make a difference in between example 
> and actuall vtk classes. 

That's an idea I hadn't considered yet either.

>     For me MDI, SDI and Dialog would be examples of use of the generic 
> VTK-MFC classes.
>     If this sound irrational, could you provide an extract of the code 
> that makes an SDI VTK-MFC window deeply different from let say a MDI 
> VTK-MFC window., thanks. 

The view isn't different between SDI and MDI app.  It is the document 
related to the view that is different.
So perhaps we put a vtkMFCView class in which wraps the generic 
vtkMFCWindow.  Then integrating a vtk window into an SDI/MDI app is a 
touch easier for the MFC people.


> What do you think ?
> Mathieu
> de Boer Ingo wrote:
>>> Thanks for the discussion.  So I guess we replace the generic 
>>> MFC/VTK class in there with specialized ones for targeting tyes of 
>>> MFC applications (SDI, MDI, Dialog).  Should we leave the generic 
>>> one there in case?
>> I am not sure about it. But in my opinion this is not needed, really.
>> Normaly when you do MFC programming you have an application wizard, 
>> which
>> makes you a MDI, SDI or Dialog. After that you fill it with information.
>> Imagine you do that, use the generic VTK-MFC class, what do you have ?
>> A blank window. You still have to add some actors and stuff to see an
>> object. So you have your own CView class based on a generic VTK-MFC 
>> class
>> with some actors code in you CView class. Looking at the generic
>> VTK-MFC class with a small amount of code, at a certain time or amount
>> of code the programmer will delete the generic VTK-MFC and copy the
>> code into his own class.
>> My opinion on this: keep it simple. I think, a MFC programmer likes
>> to look at a small demo with small classes in a well-known doc-view
>> architecure without wondering why there is an additional class 
>> inbetween.
>> Anyways, I'll try to make a small generic windows class (using the 
>> existing
>> one from Clinton) for MDI, SDI and Dialog.
>> So, maybe we can compare that to the ones I've written already and than
>> we decide what might be easier to understand, which should be the major
>> goal. Or, if it works... We include all the samples into the CVS ;)
>> greets
>>   Ingo
>> ---
>> Dr.-Ing. Ingo H. de Boer
>> Polytec GmbH
>> Polytec-Platz 1-7, 76337 Waldbronn, Germany
>> phone: ++49 7243 604 106
>> fax  : ++49 7243 604 255
>> _______________________________________________
>> vtk-developers mailing list
>> vtk-developers at vtk.org
>> http://www.vtk.org/mailman/listinfo/vtk-developers

More information about the vtk-developers mailing list