<div>Hi Bill,</div><div><br></div>I have converted all the *.cxx examples.<br><br>Regards<br><div> Andrew</div><div><br><div class="gmail_quote">On Thu, Mar 29, 2012 at 3:13 PM, Andrew Maclean <span dir="ltr"><<a href="mailto:andrew.amaclean@gmail.com">andrew.amaclean@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Hi Bill,</div><div><br></div>I think this would be a good idea. I am all for keeping the number of locations for examples to a minimum. Do we keep the datasets there too? Namely Data.tgz, Frog.tgz, Full-Head.tgz ad PineRoot.tgz. In this day and age they are not big datasets and don't change.<div>
<br></div><div>If no one has any objections could you please move the VTKTextbook directory there? Once this is done I can commit the changes I have made already.</div><div><br></div><div>Regards</div><span class="HOEnZb"><font color="#888888"><div>
Andrew</div></font></span><div class="HOEnZb"><div class="h5">
<div><br><br><div class="gmail_quote">On Thu, Mar 29, 2012 at 12:19 PM, Bill Lorensen <span dir="ltr"><<a href="mailto:bill.lorensen@gmail.com" target="_blank">bill.lorensen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Justin,<br>
<br>
The VTK WIki Examples: <a href="http://www.vtk.org/Wiki/VTK/Examples" target="_blank">http://www.vtk.org/Wiki/VTK/Examples</a> could use<br>
more python examples. These examples are scraped every night and kept<br>
in a git repository.<br>
<span><font color="#888888"><br>
Bill<br>
</font></span><div><div><br>
On Wed, Mar 28, 2012 at 6:07 PM, Justin Weber <<a href="mailto:onlyjus@gmail.com" target="_blank">onlyjus@gmail.com</a>> wrote:<br>
> All,<br>
><br>
> I would be willing to help with the python examples. Converting C++ to<br>
> python isn't that bad. Also, along the lines of python, it would be great if<br>
> examples could be written for conversions between numpy arrays and vtk<br>
> arrays, as well as taking 3D numpy arrays and converting them into<br>
> structured grids or data sets.<br>
><br>
> Justin<br>
><br>
><br>
> On Wed, Mar 28, 2012 at 8:34 PM, Andrew Maclean <<a href="mailto:andrew.amaclean@gmail.com" target="_blank">andrew.amaclean@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Marcus,<br>
>> This is a good way forward.<br>
>><br>
>> With respect to updating the books, I agree with you in that we<br>
>> should update the next editions of the books to focus primarily on the C++<br>
>> API, and Python as the preferred wrapped language.<br>
>> I am happy to help converting the C++ examples in the book to the newer<br>
>> version of VTK. I have had a quick look and the conversion is pretty<br>
>> straightforward and I have already completed Cone and Cone2. I will probably<br>
>> finish the rest in a few hours.<br>
>> I will be also glad to help with the conversion of TCL to Python.<br>
>><br>
>> If you guys (Kitware) set up a repository with the original code and<br>
>> datasets then I can start putting them up. At least then we will have a good<br>
>> working base.<br>
>><br>
>><br>
>> Regards<br>
>> Andrew<br>
>><br>
>><br>
>>><br>
>>> ---------- Forwarded message ----------<br>
>>> From: "Marcus D. Hanwell" <<a href="mailto:marcus.hanwell@kitware.com" target="_blank">marcus.hanwell@kitware.com</a>><br>
>>> To: Wes Turner <<a href="mailto:wes.turner@kitware.com" target="_blank">wes.turner@kitware.com</a>><br>
>>> Cc: VTK Developers <<a href="mailto:vtk-developers@vtk.org" target="_blank">vtk-developers@vtk.org</a>>, vtkusers <<a href="mailto:vtkusers@vtk.org" target="_blank">vtkusers@vtk.org</a>>,<br>
>>> Will Schroeder <<a href="mailto:will.schroeder@kitware.com" target="_blank">will.schroeder@kitware.com</a>>, Darshan Pai<br>
>>> <<a href="mailto:darshanpai@gmail.com" target="_blank">darshanpai@gmail.com</a>><br>
>>> Date: Wed, 28 Mar 2012 19:00:33 -0400<br>
>>> Subject: Re: [vtk-developers] [vtkusers] Modularization, Context2D and<br>
>>> 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" target="_blank">wes.turner@kitware.com</a>><br>
>>> 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" target="_blank">darshanpai@gmail.com</a>><br>
>>> > wrote:<br>
>>> >><br>
>>> >> When you say remove TCL, there will still be a switch like USE_TCL ,<br>
>>> >> 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" target="_blank">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<br>
>>> >>> without<br>
>>> >>> problems may not be subscribed to the mailing lists and we may not<br>
>>> >>> find out<br>
>>> >>> until after we make the change and everything breaks. Still I think<br>
>>> >>> 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" target="_blank">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<br>
>>> >>>> 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" target="_blank">bill.lorensen@gmail.com</a>> wrote:<br>
>>> >>>>><br>
>>> >>>>> I agree with Will. We should ask the community about the impact of<br>
>>> >>>>> 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" target="_blank">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<br>
>>> >>>>> > explicit<br>
>>> >>>>> > transition plan.<br>
>>> >>>>> > W<br>
>>> >>>>> ><br>
>>> >>>>> ><br>
>>> >>>>> > On Wed, Mar 28, 2012 at 9:53 AM, Wes Turner<br>
>>> >>>>> > <<a href="mailto:wes.turner@kitware.com" target="_blank">wes.turner@kitware.com</a>><br>
>>> >>>>> > wrote:<br>
>>> >>>>> >><br>
>>> >>>>> >> Changing a few interfaces is manageable. Removing support for<br>
>>> >>>>> >> the<br>
>>> >>>>> >> entire<br>
>>> >>>>> >> GUI system is much more catastrophic. If this were a democracy<br>
>>> >>>>> >> 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<br>
>>> >>>>> >> <<a href="mailto:david.cole@kitware.com" target="_blank">david.cole@kitware.com</a>><br>
>>> >>>>> >> wrote:<br>
>>> >>>>> >>><br>
>>> >>>>> >>> I'm not saying that applications like this shouldn't upgrade.<br>
>>> >>>>> >>> On<br>
>>> >>>>> >>> the<br>
>>> >>>>> >>> contrary, I think they should, and I think they should do it<br>
>>> >>>>> >>> soon,<br>
>>> >>>>> >>> and give<br>
>>> >>>>> >>> us feedback on the new layout of modular VTK, and on the rest<br>
>>> >>>>> >>> 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<br>
>>> >>>>> >>> anyhow...<br>
>>> >>>>> >>> and because<br>
>>> >>>>> >>> of this, now is the perfect opportunity to make breaking<br>
>>> >>>>> >>> 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<br>
>>> >>>>> >>> and<br>
>>> >>>>> >>> potential for more modern wrapped languages.)<br>
>>> >>>>> >>><br>
>>> >>>>> >>> Tcl wrapping, even if removed from VTK itself, could be done in<br>
>>> >>>>> >>> 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<br>
>>> >>>>> >>> to<br>
>>> >>>>> >>> this new<br>
>>> >>>>> >>> VTK if it wants to survive. To the best of my knowledge, nobody<br>
>>> >>>>> >>> has<br>
>>> >>>>> >>> spent<br>
>>> >>>>> >>> any effort making sure ActiViz is still going to work<br>
>>> >>>>> >>> flawlessly<br>
>>> >>>>> >>> with the<br>
>>> >>>>> >>> new VTK. That'll be something for somebody's to do list after<br>
>>> >>>>> >>> 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" target="_blank">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<br>
>>> >>>>> >>> an<br>
>>> >>>>> >>> old<br>
>>> >>>>> >>> generation widgets that we don't recommend folks derive from,<br>
>>> >>>>> >>> but<br>
>>> >>>>> >>> the fact<br>
>>> >>>>> >>> remains that there are a few widgets in VTK that derive from<br>
>>> >>>>> >>> it.<br>
>>> >>>>> >>> There are a<br>
>>> >>>>> >>> lot of widgets in Slicer (<20) and VolView (>10) that derive<br>
>>> >>>>> >>> 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<br>
>>> >>>>> >>> lot<br>
>>> >>>>> >>> of apps<br>
>>> >>>>> >>> under active development out there relying on VTK being<br>
>>> >>>>> >>> 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" target="_blank">dave.demarle@kitware.com</a>> wrote:<br>
>>> >>>>> >>>><br>
>>> >>>>> >>>> And I _will_ add text to the download page to make it clear<br>
>>> >>>>> >>>> what<br>
>>> >>>>> >>>> that<br>
>>> >>>>> >>>> binary is because you are entirely right that it shouldn't be<br>
>>> >>>>> >>>> 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" target="_blank">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" target="_blank">dave.demarle@kitware.com</a>> wrote:<br>
>>> >>>>> >>>> > That is an old school 32bit windows tcl interpreter with the<br>
>>> >>>>> >>>> > tcl<br>
>>> >>>>> >>>> > wrapped vtk libs preloaded. Use it by typing in vtk tcl<br>
>>> >>>>> >>>> > scripts<br>
>>> >>>>> >>>> > there,<br>
>>> >>>>> >>>> > or just pass tcl scripts as filenames to that executable to<br>
>>> >>>>> >>>> > run<br>
>>> >>>>> >>>> > them<br>
>>> >>>>> >>>> > without the shell. (Back when I was a young lad, and when<br>
>>> >>>>> >>>> > Will<br>
>>> >>>>> >>>> > and<br>
>>> >>>>> >>>> > Bill were still old men, that was the _easy_ way to learn<br>
>>> >>>>> >>>> > VTK.<br>
>>> >>>>> >>>> > Ah<br>
>>> >>>>> >>>> > those were the days, even if we did have to walk five miles<br>
>>> >>>>> >>>> > 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<br>
>>> >>>>> >>>> > 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<br>
>>> >>>>> >>>> > the<br>
>>> >>>>> >>>> > tcl<br>
>>> >>>>> >>>> > exe, and will try to make a proper SDK so that you don't<br>
>>> >>>>> >>>> > 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" target="_blank">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" target="_blank">daviddoria@gmail.com</a>><br>
>>> >>>>> >>>> > wrote:<br>
>>> >>>>> >>>> >> On a related note, every Windows user I have suggested VTK<br>
>>> >>>>> >>>> >> 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<br>
>>> >>>>> >>>> >> and<br>
>>> >>>>> >>>> >> installed it on a Windows machine, and when I run "VTK"<br>
>>> >>>>> >>>> >> 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<br>
>>> >>>>> >>>> >> binary<br>
>>> >>>>> >>>> >> package?<br>
>>> >>>>> >>>> >> My suggestion would be to remove this from the download<br>
>>> >>>>> >>>> >> page<br>
>>> >>>>> >>>> >> entirely,<br>
>>> >>>>> >>>> >> or at least bury it so it is not the first thing you see<br>
>>> >>>>> >>>> >> and so<br>
>>> >>>>> >>>> >> it<br>
>>> >>>>> >>>> >> doesn't look like what you should download as a new user.<br>
>>> >>>>> >>>> >> It<br>
>>> >>>>> >>>> >> should<br>
>>> >>>>> >>>> >> be<br>
>>> >>>>> >>>> >> immediately clear that VTK is intended to be used as a<br>
>>> >>>>> >>>> >> 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" target="_blank">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" target="_blank">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" target="_blank">(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" target="_blank">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" target="_blank">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>
>> Andrew J. P. Maclean<br>
>><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>
>> 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>
> 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>
Unpaid intern in BillsBasement at noware dot com<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>___________________________________________<br>Andrew J. P. Maclean<br><br>___________________________________________<br>
</div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>___________________________________________<br>Andrew J. P. Maclean<br><br>___________________________________________<br>
</div>