[vtkusers] RE: [vtk-developers] New vtk packages; suggestions reqd. for othe r modules

[Prabhu Ramachandran]

hi,

>>>>> "DJB" == Daniel J Blezek <Blezek> writes:


    DJB> was a Good Thing, and helped make the Tcl interface a bit
    DJB> more useful, in the case that you wanted to do batch
    DJB> processing.  In Python does it make sense?  People seemed to
    DJB> be quite happy with "import vtkpython", and off you go.  We
    DJB> are going down a path of gyrations that may or may not be

I have one vapor-ware application that might use this - a class
tracker written in Python.  It finds all new classes in each package
and spits it out in very nice looking HTML. :) I am not going to write
this but someone might.

Point is there might be an application in the future that could use
the split packages.  Agreed that such an application can use
vtk.common and get all the classes but this isnt perfect.

    >> import vtk from vtkpkg.gui.tk import RenderWidget a =
    >> vtk.vtkSomeClass() r = RenderWidget()
    >> 
    >> # or import vtkpkg.common a =
    >> vtkpkg.common.vtkSomeCommonClass()

    DJB>   Cleanly, but not as elegant as I would like.  Having vtk
    DJB> broken into two packages adds some unnecessary complexity.

Well, that complexity is only used by developers so they can always
do 

import vtkpkg.common

this is far better than doing 

if os.name == 'asds':
   import libvtkCommonPython.  

etc.

The whole point is that by allowing one to load parts of vtk we avoid
problems with name changes and the like.

Anyway I think we should think some more about this before making any
more changes.

Thanks for the feedback.

prabhu