Juan, <div><br></div><div>Thank you for your interest, feedback, and offer to help! I have addressed each of your concerns inline below:<br clear="all"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
1) For a long time ITK and VTK user, it is faster and more comfortable<br>
to use the examples from GIT rather than from the wiki. </blockquote><div><br></div><div>I completely agree. We are working on systems that will allow working on the examples directly through the repository. </div><div><br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">When I got the examples from git I found two issues:<br>
a) The qt examples and the wiki are not in sync. At first I couldn't<br>
make them work, because I didn't know some files where generated from<br>
the .ui file, which BTW is missing from the git repo.<br></blockquote><div><br></div><div>You are correct, the UI files are missing from the repository. Bill mentioned that he will fix that shortly. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
b) The qt examples are not built by default and I did not find an easy<br>
way to enable them. Maybe the missing .ui file is related to this<br>
issue.<br></blockquote><div><br></div><div>You're right, they are currently not setup to build in the repository. I will look into doing that once the ui files are scraped nightly.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
c) either a) and b) are correct, or I am missing something. If I'm<br>
missing something, this means that we need a better documentation to<br>
make whats needed clear.<br></blockquote><div><br></div><div>At the top of the Qt section (<a href="http://www.vtk.org/Wiki/VTK/Examples/Cxx#Qt">http://www.vtk.org/Wiki/VTK/Examples/Cxx#Qt</a>) , there is a link to "Qt Setup" (<a href="http://www.vtk.org/Wiki/VTK/Tutorials/QtSetup">http://www.vtk.org/Wiki/VTK/Tutorials/QtSetup</a>) Perhaps this would be a good place to explain the current process?</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2) After failing with the git examples, I've fallen back to the wiki.<br>
Once copy/pasted everything I found out two problems:<br>
a) On osx with cmake 2.8.6, it will fail, because some escape<br>
sequences were missing. See the following post for an explanation:<br>
<a href="http://www.vtk.org/pipermail/vtk-developers/2012-May/011548.html" target="_blank">http://www.vtk.org/pipermail/vtk-developers/2012-May/011548.html</a>.<br>
Using cmake 2.8.9 the problem is gone.<br></blockquote><div><br></div><div> I'm not sure there is a fix that we can do for that as it was a problem in CMake itself?</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
b) The CMakeLists.txt is incorrect. The line: TARGET_LINK_LIBRARIES(<br>
RenderWindowUIMultipleInheritance QVTK ) does not work. I don't have<br>
libQVTK on any of my systems. It should read: TARGET_LINK_LIBRARIES(<br>
RenderWindowUIMultipleInheritance ${VTK_LIBRARIES} ${QT_LIBRARIES} )<br>
or at least:<br>
TARGET_LINK_LIBRARIES( RenderWindowUIMultipleInheritance<br>
${VTK_LIBRARIES} ). I did not test the second one.<br></blockquote><div><br></div><div> QVTK was for VTK 5.x. With 6.0, you are correct that ${VTK_LIBRARIES} is the correct thing to use. On this page: <a href="http://www.vtk.org/Wiki/VTK/Examples/Cxx/Images/ImageSlice">http://www.vtk.org/Wiki/VTK/Examples/Cxx/Images/ImageSlice</a> you can see how we check for the condition that requires the old or new way (I suppose we could also explicitly check the VTK version number?). If you could modify the CMakeLists.txt files on the Qt examples pages to use QVTK or only ${VTK_LIBRARIES} conditionally that would be great.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
All those minor issues are really a stopper for a newcomer to Qt, even<br>
being proficient in Cmake and VTK. I'm not asking for any work, but<br>
offering it. I volunteer to correct those minor things. It passed some<br>
time since I contributed examples so I don't remember the proper way<br>
to correct them. Is directly the wiki the proper place?<br></blockquote><div><br></div><div>Changes to the code (h/cxx) files should be done directly on the wiki. The CMakeLists.txt files are not scraped/used in the repository, because there is a testing framework in place that generates the necessary files to test the examples, and those are much different from the CMakeLists.txt that a user would need to build a single example. To modify the build system of the examples, you should fork the repository and send a merge request.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The cmake issue in particular, made me think about the necessity of<br>
adding a little readme to the each example, or at least to the whole<br>
wiki section. Is there a standard way to do it? Because that cmake<br>
issue will occur in every Qt example and putting a small notice could<br>
help the newcomer.<br></blockquote><div><br></div><div>Perhaps we could make a MediaWiki macro called {{QT_VTKExample}} or something similar that would post a sentence with a link to the Qt tutorial page that I linked to earlier? This way at least this would be in a centralized place so if we want to change what it says/links to we wouldn't have to do it in every Qt example separately in the future.</div>
<div><br></div><div>Thanks again for your input, and let us know if you have any trouble or any more questions.</div><div><br></div><div>David</div></div></div>