<br>Juan,<br><br>The .ui and .cpp files on the wiki should now be mirrored in the git repo.<br><br>Thanks for the report,<br><br>Bill<br><br><br><div class="gmail_quote">On Tue, Oct 23, 2012 at 8:06 AM, Juan Cardelino <span dir="ltr"><<a href="mailto:juan.cardelino@gmail.com" target="_blank">juan.cardelino@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks Bill and David,<br>
The situation is very clear now. I will change what I can<br>
using your suggestions. And I will try to write something down<br>
whenever I have the time.<br>
Best,<br>
Juan<br>
<div class="HOEnZb"><div class="h5"><br>
On Mon, Oct 22, 2012 at 5:56 PM, David Doria <<a href="mailto:daviddoria@gmail.com">daviddoria@gmail.com</a>> wrote:<br>
> Juan,<br>
><br>
> Thank you for your interest, feedback, and offer to help! I have addressed<br>
> each of your concerns inline below:<br>
><br>
>> 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.<br>
><br>
><br>
> I completely agree. We are working on systems that will allow working on the<br>
> examples directly through the repository.<br>
><br>
>> 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>
><br>
><br>
> You are correct, the UI files are missing from the repository. Bill<br>
> mentioned that he will fix that shortly.<br>
><br>
>><br>
>> 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>
><br>
><br>
> You're right, they are currently not setup to build in the repository. I<br>
> will look into doing that once the ui files are scraped nightly.<br>
><br>
>><br>
>> 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>
><br>
><br>
> At the top of the Qt section (<a href="http://www.vtk.org/Wiki/VTK/Examples/Cxx#Qt" target="_blank">http://www.vtk.org/Wiki/VTK/Examples/Cxx#Qt</a>) ,<br>
> there is a link to "Qt Setup"<br>
> (<a href="http://www.vtk.org/Wiki/VTK/Tutorials/QtSetup" target="_blank">http://www.vtk.org/Wiki/VTK/Tutorials/QtSetup</a>) Perhaps this would be a good<br>
> place to explain the current process?<br>
><br>
>><br>
>> 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>
><br>
><br>
> I'm not sure there is a fix that we can do for that as it was a problem in<br>
> CMake itself?<br>
><br>
>> 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>
><br>
><br>
> QVTK was for VTK 5.x. With 6.0, you are correct that ${VTK_LIBRARIES} is<br>
> the correct thing to use. On this page:<br>
> <a href="http://www.vtk.org/Wiki/VTK/Examples/Cxx/Images/ImageSlice" target="_blank">http://www.vtk.org/Wiki/VTK/Examples/Cxx/Images/ImageSlice</a> you can see how<br>
> we check for the condition that requires the old or new way (I suppose we<br>
> could also explicitly check the VTK version number?). If you could modify<br>
> the CMakeLists.txt files on the Qt examples pages to use QVTK or only<br>
> ${VTK_LIBRARIES} conditionally that would be great.<br>
><br>
>><br>
>> 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>
><br>
><br>
> Changes to the code (h/cxx) files should be done directly on the wiki. The<br>
> CMakeLists.txt files are not scraped/used in the repository, because there<br>
> is a testing framework in place that generates the necessary files to test<br>
> the examples, and those are much different from the CMakeLists.txt that a<br>
> user would need to build a single example. To modify the build system of the<br>
> examples, you should fork the repository and send a merge request.<br>
><br>
>><br>
>> 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>
><br>
><br>
> Perhaps we could make a MediaWiki macro called {{QT_VTKExample}} or<br>
> something similar that would post a sentence with a link to the Qt tutorial<br>
> page that I linked to earlier? This way at least this would be in a<br>
> centralized place so if we want to change what it says/links to we wouldn't<br>
> have to do it in every Qt example separately in the future.<br>
><br>
> Thanks again for your input, and let us know if you have any trouble or any<br>
> more questions.<br>
><br>
> David<br>
</div></div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <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: <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>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Unpaid intern in BillsBasement at noware dot com<br><br>