[vtk-developers] Modularization, Context2D and Tcl
Marcus D. Hanwell
marcus.hanwell at kitware.com
Mon Mar 26 11:50:14 EDT 2012
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.
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" ?
>> On Sun, Mar 25, 2012 at 10:58 PM, Marcus D. Hanwell
>> <marcus.hanwell at kitware.com> wrote:
>>> 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.
>>> Powered by www.kitware.com
>>> Visit other Kitware open-source projects at
>>> Follow this link to subscribe/unsubscribe:
>> +1 919 869 8849
More information about the vtk-developers