[Paraview] ParaView and QT

[Berk Geveci]

That's not what I am suggesting, unless you are doing ParaView
development. If you are doing ParaView development, you probably
cannot use any of the VTK releases.

* If you are doing VTK development for the purpose of inclusion in
VTK, use the VTK that comes with VTK (which is what I do)
* If you are doing VTK development for any other reason, use the
latest VTK release unless
* The feature you need is not available in the latest VTK release.
Then use VTK cvs

-berk


On Mon, Jun 2, 2008 at 4:12 PM, Dominik Szczerba <domi at vision.ee.ethz.ch> wrote:
> Are you suggesting that the PV's VTK version should be used instead of the
> 'official' one - for the 'usual' VTK coding?
> Thanks,
> -- Dominik
>
> Berk Geveci wrote:
>>
>> In a way, I suppose. However, keep in mind that VTK and ParaView
>> release cycles are completely different. VTK is released at most once
>> per year (and it is almost a miracle when that happens) whereas
>> ParaView is released 3-4 times per year. If we were stuck with the
>> latest version of VTK (5.0 from 2 years ago), we would end up bundling
>> a lot of improvements and bug fixes for VTK in ParaView. This would
>> make the development a major pain and the migration of improvements
>> from ParaView to VTK would almost never happen. Maybe one day, if the
>> release cycles are close AND VTK is as widely distributed as Qt, we
>> can stop bundling VTK.
>>
>> -berk
>>
>> On Mon, Jun 2, 2008 at 9:03 AM, Dominik Szczerba <domi at vision.ee.ethz.ch>
>> wrote:
>>>
>>> Hi,
>>>
>>> Is bundling VTK not falling into the same category?
>>>
>>> -- Dominik
>>>
>>> Berk Geveci wrote:
>>>>
>>>> I agree with Michael that it is not a good idea to bundle Qt with
>>>> ParaView. I was not happy with bundling Tcl/Tk despite the fact that
>>>> they are pretty small compared to Qt. I think we will try to keep up
>>>> with Qt better in the future. We may officially support a specific
>>>> version but we will try new version as they come out and make sure
>>>> that they compile at least.
>>>>
>>>> -berk
>>>>
>>>> On Mon, Jun 2, 2008 at 5:05 AM, Michael Wild <themiwi at gmail.com> wrote:
>>>> Or, as you're using Debian, you can use pinning to prevent apt from
>>>> updating
>>>> Qt. See e.g. [1] or ask google.
>>>>
>>>> I would hate a bundled Qt because it is a large beast and if everybody
>>>> starts doing it we end up in Windows-Land where every program comes with
>>>> the
>>>> full set of libraries it depends on, cluttering the system until it's so
>>>> broken only a clean install can solve the problems...
>>>>
>>>> HTH
>>>>
>>>> Michael
>>>>
>>>> [1] http://www.debian.org/doc/manuals/apt-howto/ch-apt-get.en.html
>>>>
>>>>
>>>> On 1Jun, 2008, at 2:42, Berk Geveci wrote:
>>>>
>>>>>>> It is not easy to keep up with Trolltech guys, they keep busy :-) I
>>>>>>> recommend downloading your own version of Qt, building it and
>>>>>>> installing it somewhere out of the system path (I use /opt/qt-4.X.X).
>>>>>>> We will start supporting Qt 4.4 after we release 3.4.
>>>>>>> Also, it sounds like the problem you are running into is with CMake
>>>>>>> parsing the output of qmake. Did you test with cvs CMake?
>>>>>>>
>>>>>>> -berk
>>>>>>>
>>>>>>> On Sat, May 31, 2008 at 8:29 PM, Andrew Maclean
>>>>>>> <andrew.amaclean at gmail.com> wrote:
>>>>>>>>
>>>>>>>> This is really frustrating as my debian machines all upgraded to QT
>>>>>>>> 4.4 a few weeks ago so the ParaView builds are now broken. Even
>>>>>>>> editing the CMakeLists.txt files does not work.
>>>>>>>>
>>>>>>>> Why is it that everytime Trolltech changes QT it seems to require a
>>>>>>>> major amount of work?
>>>>>>>>
>>>>>>>> If it is not possible to keep up with the changes coming through
>>>>>>>> from
>>>>>>>> TrollTech, is it possible to do what you used to do with the older
>>>>>>>> version of ParaView and have a special version of QT that is bundled
>>>>>>>> with it?
>>>>>>>>
>>>>>>>> You say ParaView only works with a particular version of QT so why
>>>>>>>> not
>>>>>>>> bundle it?
>>>>>>>>
>>>>>>>> Sorry if I sound cranky - I am getting frustrated!
>>>>>>>>
>>>>>>>> --
>>>>>>>> ___________________________________________
>>>>>>>> Andrew J. P. Maclean
>>>>>>>> Centre for Autonomous Systems
>>>>>>>> The Rose Street Building J04
>>>>>>>> The University of Sydney 2006 NSW
>>>>>>>> AUSTRALIA
>>>>>>>> Ph: +61 2 9351 3283
>>>>>>>> Fax: +61 2 9351 7474
>>>>>>>> URL: http://www.acfr.usyd.edu.au/
>>>>>>>> ___________________________________________
>>>>>>>> _______________________________________________
>>>>>>>> ParaView mailing list
>>>>>>>> ParaView at paraview.org
>>>>>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> ParaView mailing list
>>>>>>> ParaView at paraview.org
>>>>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>>> _______________________________________________
>>> ParaView mailing list
>>> ParaView at paraview.org
>>> http://www.paraview.org/mailman/listinfo/paraview
>>>>
>>>> _______________________________________________
>>>> ParaView mailing list
>>>> ParaView at paraview.org
>>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>>> --
>>> Dominik Szczerba, Ph.D.
>>> Biomedical Simulation Group
>>> Computer Vision Lab CH-8092 Zurich
>>> http://www.vision.ee.ethz.ch/~domi
>>>
>
> --
> Dominik Szczerba, Ph.D.
> Biomedical Simulation Group
> Computer Vision Lab CH-8092 Zurich
> http://www.vision.ee.ethz.ch/~domi
>