Marcus,<div> This is a good way forward. </div><div><br></div><div>With respect to updating the books, I agree with you in that we should update the next editions of the books to focus primarily on the C++ API, and Python as the preferred wrapped language.</div>
<div>I am happy to help converting the C++ examples in the book to the newer version of VTK. I have had a quick look and the conversion is pretty straightforward and I have already completed Cone and Cone2. I will probably finish the rest in a few hours.</div>
<div> I will be also glad to help with the conversion of TCL to Python.</div><div><br></div><div>If you guys (Kitware) set up a repository with the original code and datasets then I can start putting them up. At least then we will have a good working base.</div>
<div><br></div><div><br></div><div>Regards</div><div> Andrew</div><div><br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>---------- Forwarded message ----------<br>
From: "Marcus D. Hanwell" <<a href="mailto:marcus.hanwell@kitware.com">marcus.hanwell@kitware.com</a>><br>To: Wes Turner <<a href="mailto:wes.turner@kitware.com">wes.turner@kitware.com</a>><br>Cc: VTK Developers <<a href="mailto:vtk-developers@vtk.org">vtk-developers@vtk.org</a>>, vtkusers <<a href="mailto:vtkusers@vtk.org">vtkusers@vtk.org</a>>, Will Schroeder <<a href="mailto:will.schroeder@kitware.com">will.schroeder@kitware.com</a>>, Darshan Pai <<a href="mailto:darshanpai@gmail.com">darshanpai@gmail.com</a>><br>
Date: Wed, 28 Mar 2012 19:00:33 -0400<br>Subject: Re: [vtk-developers] [vtkusers] Modularization, Context2D and Tcl<br>Hi,<br>
<br>
I didn't intend to start a thread debating the removal of Tcl. My take<br>
on the situation is that there is a fair bit of legacy code out there<br>
using it, including the VTK books and several projects (primarily in<br>
the medical field). In the modularized VTK tree I have the Tcl<br>
wrapping working (mostly at least - more tests need to be brought in),<br>
and wrapping large parts of the API correctly that had thus far not<br>
been brought in properly.<br>
<br>
I think we should mark the Tcl wrapped code as deprecated, 'heirloom'<br>
or whatever the right term is to indicate to our users that we do not<br>
have plans to significantly extend them. At this stage, with the work<br>
already present to support automatically wrapping and the few<br>
problematic modules mapped to similar names, I think we should keep<br>
them available for compilation even if they are superseded by Python<br>
as the default wrapped language.<br>
<br>
I think we should update the next editions of the books to focus<br>
primarily on the C++ API, and Python as the preferred wrapped<br>
language. Having Tcl and Java examples in there would still be<br>
appropriate in my opinion. I don't have any time to do this, but it<br>
seems like there are some people with time and motivation to help with<br>
that. It would be great to hear what the community at large thinks.<br>
Code will probably need to be updated with the correct module names,<br>
we may be able to do a little work there to import the correct new<br>
modules for the old (and this would also likely help in porting Python<br>
code which would have the exact same issue).<br>
<br>
My $0.10 on the issue. I will continue watching the mailing lists with<br>
interest, and of course welcome further input.<br>
<br>
Thanks,<br>
<br>
Marcus<br>
<br>
On Wed, Mar 28, 2012 at 6:08 PM, Wes Turner <<a href="mailto:wes.turner@kitware.com">wes.turner@kitware.com</a>> wrote:<br>
> That is not my understanding.<br>
><br>
> - Wes<br>
><br>
><br>
> On Wed, Mar 28, 2012 at 6:07 PM, Darshan Pai <<a href="mailto:darshanpai@gmail.com">darshanpai@gmail.com</a>> wrote:<br>
>><br>
>> When you say remove TCL, there will still be a switch like USE_TCL , so<br>
>> that someone who wants to include it in the project can still use it ?<br>
>><br>
>> Regards<br>
>> Darshan<br>
>><br>
>><br>
>> On Wed, Mar 28, 2012 at 5:59 PM, Wes Turner <<a href="mailto:wes.turner@kitware.com">wes.turner@kitware.com</a>><br>
>> wrote:<br>
>>><br>
>>> +1 on seeking input.<br>
>>><br>
>>> The danger of course, is that people who are merrily using tcl without<br>
>>> problems may not be subscribed to the mailing lists and we may not find out<br>
>>> until after we make the change and everything breaks. Still I think that is<br>
>>> the correct way to go and the best that we can do.<br>
>>><br>
>>> - Wes<br>
>>><br>
>>> On Wed, Mar 28, 2012 at 12:04 PM, Aashish Chaudhary<br>
>>> <<a href="mailto:aashish.chaudhary@kitware.com">aashish.chaudhary@kitware.com</a>> wrote:<br>
>>>><br>
>>>> In another email to Wes, I suggested the same. I have cc'd vtkuser's<br>
>>>> mailing list as well ( to provide background on the topic, may be better to<br>
>>>> start a new thread in the vtkusers mailing list).<br>
>>>><br>
>>>><br>
>>>> On Wed, Mar 28, 2012 at 11:55 AM, Bill Lorensen<br>
>>>> <<a href="mailto:bill.lorensen@gmail.com">bill.lorensen@gmail.com</a>> wrote:<br>
>>>>><br>
>>>>> I agree with Will. We should ask the community about the impact of a<br>
>>>>> VTK without tcl.<br>
>>>>><br>
>>>>> On Wed, Mar 28, 2012 at 8:04 AM, Will Schroeder<br>
>>>>> <<a href="mailto:will.schroeder@kitware.com">will.schroeder@kitware.com</a>> wrote:<br>
>>>>> > This may be a bigger issue than just the ARB, I'm wondering if we<br>
>>>>> > should ask<br>
>>>>> > the question across the broader community, and/or create an explicit<br>
>>>>> > transition plan.<br>
>>>>> > W<br>
>>>>> ><br>
>>>>> ><br>
>>>>> > On Wed, Mar 28, 2012 at 9:53 AM, Wes Turner <<a href="mailto:wes.turner@kitware.com">wes.turner@kitware.com</a>><br>
>>>>> > wrote:<br>
>>>>> >><br>
>>>>> >> Changing a few interfaces is manageable. Removing support for the<br>
>>>>> >> entire<br>
>>>>> >> GUI system is much more catastrophic. If this were a democracy I<br>
>>>>> >> would<br>
>>>>> >> stage a filibuster and force a super-majority. :-)<br>
>>>>> >><br>
>>>>> >> As it is, I will happily abide by any decision by the ARB, but I<br>
>>>>> >> strongly<br>
>>>>> >> urge that they make an explicit decision and announce it, rather<br>
>>>>> >> than just<br>
>>>>> >> do it by default or allow support to erode away.<br>
>>>>> >><br>
>>>>> >> - Wes<br>
>>>>> >><br>
>>>>> >><br>
>>>>> >> On Wed, Mar 28, 2012 at 7:51 AM, David Cole <<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>><br>
>>>>> >> wrote:<br>
>>>>> >>><br>
>>>>> >>> I'm not saying that applications like this shouldn't upgrade. On<br>
>>>>> >>> the<br>
>>>>> >>> contrary, I think they should, and I think they should do it soon,<br>
>>>>> >>> and give<br>
>>>>> >>> us feedback on the new layout of modular VTK, and on the rest of<br>
>>>>> >>> the changes<br>
>>>>> >>> (legacy code removal), ... other changes?<br>
>>>>> >>><br>
>>>>> >>> I am saying we're making a bunch of changes anyhow, and<br>
>>>>> >>> applications are<br>
>>>>> >>> going to have to make lots of changes to adapt to them anyhow...<br>
>>>>> >>> and because<br>
>>>>> >>> of this, now is the perfect opportunity to make breaking changes,<br>
>>>>> >>> so that<br>
>>>>> >>> apps that need to adapt only need to do it once, and then we<br>
>>>>> >>> position VTK<br>
>>>>> >>> for better things in the future. (Specifically, a C++ namespace and<br>
>>>>> >>> potential for more modern wrapped languages.)<br>
>>>>> >>><br>
>>>>> >>> Tcl wrapping, even if removed from VTK itself, could be done in a<br>
>>>>> >>> separate project, from the outside, after the fact. That's how<br>
>>>>> >>> ActiViz works<br>
>>>>> >>> for C# wrapping: which is another thing that will have to adapt to<br>
>>>>> >>> this new<br>
>>>>> >>> VTK if it wants to survive. To the best of my knowledge, nobody has<br>
>>>>> >>> spent<br>
>>>>> >>> any effort making sure ActiViz is still going to work flawlessly<br>
>>>>> >>> with the<br>
>>>>> >>> new VTK. That'll be something for somebody's to do list after the<br>
>>>>> >>> dust<br>
>>>>> >>> settles here.<br>
>>>>> >>><br>
>>>>> >>> This is the one chance we'll have in the next decade to break<br>
>>>>> >>> backwards<br>
>>>>> >>> compatibility: we should take it while we have it.<br>
>>>>> >>><br>
>>>>> >>><br>
>>>>> >>> David C.<br>
>>>>> >>><br>
>>>>> >>><br>
>>>>> >>> On Mar 28, 2012, at 6:09 AM, Karthik Krishnan<br>
>>>>> >>> <<a href="mailto:karthik.krishnan@kitware.com">karthik.krishnan@kitware.com</a>> wrote:<br>
>>>>> >>><br>
>>>>> >>> I agree with Wes. Again, not to be too vocal....<br>
>>>>> >>><br>
>>>>> >>> I don't vote for vtk3DWidget being renamed. Despite it being an<br>
>>>>> >>> old<br>
>>>>> >>> generation widgets that we don't recommend folks derive from, but<br>
>>>>> >>> the fact<br>
>>>>> >>> remains that there are a few widgets in VTK that derive from it.<br>
>>>>> >>> There are a<br>
>>>>> >>> lot of widgets in Slicer (<20) and VolView (>10) that derive from<br>
>>>>> >>> it. These<br>
>>>>> >>> are examples from just 2 applications.<br>
>>>>> >>><br>
>>>>> >>> I don't support Tcl wrapping being dropped. There are still a lot<br>
>>>>> >>> of apps<br>
>>>>> >>> under active development out there relying on VTK being wrappable<br>
>>>>> >>> from Tcl<br>
>>>>> >>> (BioImageSuite, VolView, SCIRun, MIPS to name a few). It hasn't<br>
>>>>> >>> been long<br>
>>>>> >>> since Slicer made the switch either.<br>
>>>>> >>><br>
>>>>> >>> These are all large applications, with a large user base and<br>
>>>>> >>> important<br>
>>>>> >>> customers of VTK. Don't you think a stand that: "If these<br>
>>>>> >>> applications want<br>
>>>>> >>> to continue using VTK, they shouldn't upgrade" is a bit harsh.<br>
>>>>> >>><br>
>>>>> >>> thx<br>
>>>>> >>> --<br>
>>>>> >>> karthik<br>
>>>>> >>><br>
>>>>> >>><br>
>>>>> >>> On Wed, Mar 28, 2012 at 1:47 AM, David E DeMarle<br>
>>>>> >>> <<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>> wrote:<br>
>>>>> >>>><br>
>>>>> >>>> And I _will_ add text to the download page to make it clear what<br>
>>>>> >>>> that<br>
>>>>> >>>> binary is because you are entirely right that it shouldn't be the<br>
>>>>> >>>> first thing newbies try.<br>
>>>>> >>>><br>
>>>>> >>>> David E DeMarle<br>
>>>>> >>>> Kitware, Inc.<br>
>>>>> >>>> R&D Engineer<br>
>>>>> >>>> 21 Corporate Drive<br>
>>>>> >>>> Clifton Park, NY 12065-8662<br>
>>>>> >>>> Phone: <a href="tel:518-881-4909" value="+15188814909">518-881-4909</a><br>
>>>>> >>>><br>
>>>>> >>>><br>
>>>>> >>>><br>
>>>>> >>>> On Tue, Mar 27, 2012 at 4:12 PM, David E DeMarle<br>
>>>>> >>>> <<a href="mailto:dave.demarle@kitware.com">dave.demarle@kitware.com</a>> wrote:<br>
>>>>> >>>> > That is an old school 32bit windows tcl interpreter with the tcl<br>
>>>>> >>>> > wrapped vtk libs preloaded. Use it by typing in vtk tcl scripts<br>
>>>>> >>>> > there,<br>
>>>>> >>>> > or just pass tcl scripts as filenames to that executable to run<br>
>>>>> >>>> > them<br>
>>>>> >>>> > without the shell. (Back when I was a young lad, and when Will<br>
>>>>> >>>> > and<br>
>>>>> >>>> > Bill were still old men, that was the _easy_ way to learn VTK.<br>
>>>>> >>>> > Ah<br>
>>>>> >>>> > those were the days, even if we did have to walk five miles in<br>
>>>>> >>>> > the<br>
>>>>> >>>> > snow to get to grad school.)<br>
>>>>> >>>> ><br>
>>>>> >>>> > My plan for this release is to keep it the same as before. I<br>
>>>>> >>>> > hope to<br>
>>>>> >>>> > find the time to make and post the vtkpython equivalent of that<br>
>>>>> >>>> > executable for mac, linux and windows, but I am not going to<br>
>>>>> >>>> > hold up<br>
>>>>> >>>> > the release release for them.<br>
>>>>> >>>> ><br>
>>>>> >>>> > For 6.0 we at least want the python exes, will probably drop the<br>
>>>>> >>>> > tcl<br>
>>>>> >>>> > exe, and will try to make a proper SDK so that you don't need to<br>
>>>>> >>>> > compile vtk to make c++ apps that use it.<br>
>>>>> >>>> ><br>
>>>>> >>>> > David E DeMarle<br>
>>>>> >>>> > Kitware, Inc.<br>
>>>>> >>>> > R&D Engineer<br>
>>>>> >>>> > 21 Corporate Drive<br>
>>>>> >>>> > Clifton Park, NY 12065-8662<br>
>>>>> >>>> > Phone: <a href="tel:518-881-4909" value="+15188814909">518-881-4909</a><br>
>>>>> >>>> ><br>
>>>>> >>>> ><br>
>>>>> >>>> ><br>
>>>>> >>>> > On Tue, Mar 27, 2012 at 3:45 PM, David Doria<br>
>>>>> >>>> > <<a href="mailto:daviddoria@gmail.com">daviddoria@gmail.com</a>><br>
>>>>> >>>> > wrote:<br>
>>>>> >>>> >> On a related note, every Windows user I have suggested VTK to<br>
>>>>> >>>> >> has<br>
>>>>> >>>> >> gone<br>
>>>>> >>>> >> to this page:<br>
>>>>> >>>> >> <a href="http://vtk.org/VTK/resources/software.html#latest2" target="_blank">http://vtk.org/VTK/resources/software.html#latest2</a><br>
>>>>> >>>> >><br>
>>>>> >>>> >> and been extremely confused about what they get with the<br>
>>>>> >>>> >> "Windows<br>
>>>>> >>>> >> (Installer) : vtk-5.8.0-win32-x86.exe". I just downloaded and<br>
>>>>> >>>> >> installed it on a Windows machine, and when I run "VTK" from<br>
>>>>> >>>> >> the<br>
>>>>> >>>> >> start<br>
>>>>> >>>> >> menu (the only thing that appears to be an option), I get a<br>
>>>>> >>>> >> blank<br>
>>>>> >>>> >> terminal window and a blank gray widget with no further<br>
>>>>> >>>> >> instructions/explanation - indeed very confusing!<br>
>>>>> >>>> >><br>
>>>>> >>>> >> My understanding is that this is some sort of TCL-only binary<br>
>>>>> >>>> >> package?<br>
>>>>> >>>> >> My suggestion would be to remove this from the download page<br>
>>>>> >>>> >> entirely,<br>
>>>>> >>>> >> or at least bury it so it is not the first thing you see and so<br>
>>>>> >>>> >> it<br>
>>>>> >>>> >> doesn't look like what you should download as a new user. It<br>
>>>>> >>>> >> should<br>
>>>>> >>>> >> be<br>
>>>>> >>>> >> immediately clear that VTK is intended to be used as a library,<br>
>>>>> >>>> >> not a<br>
>>>>> >>>> >> standalone application.<br>
>>>>> >>>> >><br>
>>>>> >>>> >> David<br>
>>>>> >>>> >> _______________________________________________<br>
>>>>> >>>> >> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>>>>> >>>> >><br>
>>>>> >>>> >> Visit other Kitware open-source projects at<br>
>>>>> >>>> >> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>>>> >>>> >><br>
>>>>> >>>> >> Follow this link to subscribe/unsubscribe:<br>
>>>>> >>>> >> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
>>>>> >>>> >><br>
>>>>> >>>> _______________________________________________<br>
>>>>> >>>> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>>>>> >>>><br>
>>>>> >>>> Visit other Kitware open-source projects at<br>
>>>>> >>>> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>>>> >>>><br>
>>>>> >>>> Follow this link to subscribe/unsubscribe:<br>
>>>>> >>>> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
>>>>> >>>><br>
>>>>> >>><br>
>>>>> >>><br>
>>>>> >>><br>
>>>>> >>> --<br>
>>>>> >>> --<br>
>>>>> >>> karthik<br>
>>>>> >>><br>
>>>>> >>><br>
>>>>> >>> _______________________________________________<br>
>>>>> >>> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>>>>> >>><br>
>>>>> >>> Visit other Kitware open-source projects at<br>
>>>>> >>> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>>>> >>><br>
>>>>> >>> Follow this link to subscribe/unsubscribe:<br>
>>>>> >>> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
>>>>> >>><br>
>>>>> >>><br>
>>>>> >><br>
>>>>> >><br>
>>>>> >><br>
>>>>> >> --<br>
>>>>> >> Wesley D. Turner, Ph.D.<br>
>>>>> >> Kitware, Inc.<br>
>>>>> >> Technical Leader<br>
>>>>> >> 28 Corporate Drive<br>
>>>>> >> Clifton Park, NY 12065-8662<br>
>>>>> >> Phone: <a href="tel:518-881-4920" value="+15188814920">518-881-4920</a><br>
>>>>> >><br>
>>>>> >> _______________________________________________<br>
>>>>> >> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>>>>> >><br>
>>>>> >> Visit other Kitware open-source projects at<br>
>>>>> >> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>>>> >><br>
>>>>> >> Follow this link to subscribe/unsubscribe:<br>
>>>>> >> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
>>>>> >><br>
>>>>> >><br>
>>>>> ><br>
>>>>> ><br>
>>>>> ><br>
>>>>> > --<br>
>>>>> > William J. Schroeder, PhD<br>
>>>>> > Kitware, Inc.<br>
>>>>> > 28 Corporate Drive<br>
>>>>> ><br>
>>>>> > Clifton Park, NY 12065<br>
>>>>> > <a href="mailto:will.schroeder@kitware.com">will.schroeder@kitware.com</a><br>
>>>>> > <a href="http://www.kitware.com" target="_blank">http://www.kitware.com</a><br>
>>>>> > <a href="tel:%28518%29%20881-4902" value="+15188814902">(518) 881-4902</a><br>
>>>>> ><br>
>>>>> > _______________________________________________<br>
>>>>> > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>>>>> ><br>
>>>>> > Visit other Kitware open-source projects at<br>
>>>>> > <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>>>> ><br>
>>>>> > Follow this link to subscribe/unsubscribe:<br>
>>>>> > <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
>>>>> ><br>
>>>>> ><br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> --<br>
>>>>> Unpaid intern in BillsBasement at noware dot com<br>
>>>>> _______________________________________________<br>
>>>>> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>>>>><br>
>>>>> Visit other Kitware open-source projects at<br>
>>>>> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>>>><br>
>>>>> Follow this link to subscribe/unsubscribe:<br>
>>>>> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
>>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> --<br>
>>>> | Aashish Chaudhary<br>
>>>> | R&D Engineer<br>
>>>> | Kitware Inc.<br>
>>>> | <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>>>><br>
>>>> Visit other Kitware open-source projects at<br>
>>>> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>>><br>
>>>> Please keep messages on-topic and check the VTK FAQ at:<br>
>>>> <a href="http://www.vtk.org/Wiki/VTK_FAQ" target="_blank">http://www.vtk.org/Wiki/VTK_FAQ</a><br>
>>>><br>
>>>><br>
>>>> Follow this link to subscribe/unsubscribe:<br>
>>>> <a href="http://www.vtk.org/mailman/listinfo/vtkusers" target="_blank">http://www.vtk.org/mailman/listinfo/vtkusers</a><br>
>>>><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> Wesley D. Turner, Ph.D.<br>
>>> Kitware, Inc.<br>
>>> Technical Leader<br>
>>> 28 Corporate Drive<br>
>>> Clifton Park, NY 12065-8662<br>
>>> Phone: <a href="tel:518-881-4920" value="+15188814920">518-881-4920</a><br>
>>><br>
>>> _______________________________________________<br>
>>> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>>><br>
>>> Visit other Kitware open-source projects at<br>
>>> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>>><br>
>>> Please keep messages on-topic and check the VTK FAQ at:<br>
>>> <a href="http://www.vtk.org/Wiki/VTK_FAQ" target="_blank">http://www.vtk.org/Wiki/VTK_FAQ</a><br>
>>><br>
>>> Follow this link to subscribe/unsubscribe:<br>
>>> <a href="http://www.vtk.org/mailman/listinfo/vtkusers" target="_blank">http://www.vtk.org/mailman/listinfo/vtkusers</a><br>
>>><br>
>><br>
><br>
><br>
><br>
> --<br>
> Wesley D. Turner, Ph.D.<br>
> Kitware, Inc.<br>
> Technical Leader<br>
> 28 Corporate Drive<br>
> Clifton Park, NY 12065-8662<br>
> Phone: <a href="tel:518-881-4920" value="+15188814920">518-881-4920</a><br>
><br>
> _______________________________________________<br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at<br>
> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Please keep messages on-topic and check the VTK FAQ at:<br>
> <a href="http://www.vtk.org/Wiki/VTK_FAQ" target="_blank">http://www.vtk.org/Wiki/VTK_FAQ</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://www.vtk.org/mailman/listinfo/vtkusers" target="_blank">http://www.vtk.org/mailman/listinfo/vtkusers</a><br>
><br><br></blockquote></div><div><br></div>-- <br>___________________________________________<br>Andrew J. P. Maclean<br><br>___________________________________________<br>
</div>