[vtk-developers] Modularization, Context2D and Tcl

Marcus D. Hanwell marcus.hanwell at kitware.com
Mon Mar 26 14:13:50 EDT 2012


That does sound like a great thing to do once we have merged in
modularization to make that possible (in my opinion at least).

On Mon, Mar 26, 2012 at 1:31 PM, David Cole <david.cole at kitware.com> wrote:
> Thanks for the explanations.
>
> So... to piggy back on while we're making rather large changes anyway... :-)
>
> Would it make sense to rename the classes vtk2DHistogramItem,
> vtk3DSImporter and vtk3DWidget while we're at it? Just to avoid future
> problems as reported by David Gobbi's ruby wrapping fellow?
>
> Eventually, a namespace-enclosed set of VTK classes without the "vtk"
> prefix could be possible. But not if some of them start with numbers
> like those three.
>
> Just an idea.
>
>
> On Mon, Mar 26, 2012 at 1:25 PM, Marcus D. Hanwell
> <marcus.hanwell at kitware.com> wrote:
>> Yes - it was just the module names. Class names have no impact here as
>> far as I can tell.
>>
>> On Mon, Mar 26, 2012 at 12:24 PM, David Gobbi <david.gobbi at gmail.com> wrote:
>>> Hi David,
>>>
>>> It's just the modules that can't have digits (I think that Tcl
>>> reserves digits for version numbers, each Tcl module is versioned).
>>>
>>> However, I was helping a fellow write Ruby wrappers for VTK a while
>>> back, and he wanted "vtk" to be a namespace but couldn't because
>>> vtk::3DWidget is not a valid name...
>>>
>>>  - David
>>>
>>>
>>> On Mon, Mar 26, 2012 at 10:11 AM, David Cole <david.cole at kitware.com> wrote:
>>>> This whole thing doesn't make a lot of sense to me...
>>>>
>>>> We've had classes named "vtk3DSImporter" and "vtk3DWidget" for a long time.
>>>>
>>>> Here's the doc for 3DWidget from the 5.8 docs:
>>>>
>>>>  http://www.vtk.org/doc/release/5.8/html/a00095.html
>>>>
>>>> Are you saying they've never been accessible from tcl?
>>>>
>>>>
>>>> On Mon, Mar 26, 2012 at 11:58 AM, Jean-Christophe Fillion-Robin
>>>> <jchris.fillionr at kitware.com> wrote:
>>>>> As far as Slicer is concerned, we migrated to python with the advent of
>>>>> version 4 :)
>>>>> Jc
>>>>>
>>>>>
>>>>> On Mon, Mar 26, 2012 at 11:50 AM, Marcus D. Hanwell
>>>>> <marcus.hanwell at kitware.com> wrote:
>>>>>>
>>>>>> So, for now I have applied a mapping of numerals to Roman numerals,
>>>>>> and that works well. The TCL objects have the 2 replaced by II,
>>>>>> everything else remains as is. This is a possible option too, although
>>>>>> I am not particularly tied to the name.
>>>>>>
>>>>>> None of these classes were ever wrapped in Tcl or Java as we failed to
>>>>>> add the handwritten code to make them part of those wrapped imports.
>>>>>> This is not automated, but it does beg the question of how many Tcl
>>>>>> users are out there and if they are largely supporting legacy Tcl
>>>>>> scripts and not looking at new API.
>>>>>>
>>>>>> Marcus
>>>>>>
>>>>>> On Sun, Mar 25, 2012 at 11:19 PM, Marcus D. Hanwell
>>>>>> <marcus.hanwell at kitware.com> wrote:
>>>>>> > That was my other thought, although at this stage the 3D stuff is so
>>>>>> > new and small it hardly seems worth it. It also looks ugly to me, but
>>>>>> > I could learn to live with it. As a policy it looks like we must only
>>>>>> > allow letters a-z to guarantee it will work everywhere (or do some
>>>>>> > weird transform for Tcl).
>>>>>> >
>>>>>> > On Sun, Mar 25, 2012 at 11:11 PM, Jean-Christophe Fillion-Robin
>>>>>> > <jchris.fillionr at kitware.com> wrote:
>>>>>> >> Good point.
>>>>>> >> On the other want if we still want to maintain the difference, what
>>>>>> >> about
>>>>>> >> "ContextThreeD" and "ContextTwoD" ?
>>>>>> >>
>>>>>> >> Jc
>>>>>> >>
>>>>>> >> On Sun, Mar 25, 2012 at 10:58 PM, Marcus D. Hanwell
>>>>>> >> <marcus.hanwell at kitware.com> wrote:
>>>>>> >>>
>>>>>> >>> Hi,
>>>>>> >>>
>>>>>> >>> Tcl has been an adventure. It appears that Tcl modules are not allowed
>>>>>> >>> to have numbers in them, and so Rendering/Context2D and
>>>>>> >>> Views/Context2D will have to change. Perhaps their names can simply be
>>>>>> >>> Context, and that would remove the oddness that the 2D context modules
>>>>>> >>> have some 3D rendering code in there too.
>>>>>> >>>
>>>>>> >>> Marcus
>>>>>> >>> _______________________________________________
>>>>>> >>> Powered by www.kitware.com
>>>>>> >>>
>>>>>> >>> Visit other Kitware open-source projects at
>>>>>> >>> http://www.kitware.com/opensource/opensource.html
>>>>>> >>>
>>>>>> >>> Follow this link to subscribe/unsubscribe:
>>>>>> >>> http://www.vtk.org/mailman/listinfo/vtk-developers
>>>>>> >>>
>>>>>> >>
>>>>>> >>
>>>>>> >>
>>>>>> >> --
>>>>>> >> +1 919 869 8849
>>>>>> >>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> +1 919 869 8849
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Powered by www.kitware.com
>>>>>
>>>>> Visit other Kitware open-source projects at
>>>>> http://www.kitware.com/opensource/opensource.html
>>>>>
>>>>> Follow this link to subscribe/unsubscribe:
>>>>> http://www.vtk.org/mailman/listinfo/vtk-developers
>>>>>
>>>>>
>>>> _______________________________________________
>>>> Powered by www.kitware.com
>>>>
>>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>>>
>>>> Follow this link to subscribe/unsubscribe:
>>>> http://www.vtk.org/mailman/listinfo/vtk-developers
>>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.vtk.org/mailman/listinfo/vtk-developers
>>>



More information about the vtk-developers mailing list