Re: [Paraview] Printing from a macro

2011-10-04 Thread Greg Schussman

On 10/03/2011 02:18 AM, Pierre Chevalier Géologue wrote:

Le 03/10/2011 09:58, Greg Schussman claviota:

Or, even if it's not possible to control which window ("Output Window"
vs. "Python Shell") displays the output, is there at least a way to
predict which one will do the displaying?

It will probably be the one which has the focus, I guess.

Thanks, Pierre.

Would you have any idea how to set the focus from python?

Thanks.

Greg

À+
Pierre



___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview


[Paraview] Accessing OpenGL from standard VTK filter

2011-10-04 Thread Sohail Shafii
Hi,

If I were to write a typical VTK filter C++ (i.e. the type with VTKRequestData, 
not existing in the VTK/Rendering folder), would it be fine to have OpenGL 
calls in there?  I'm guessing based on the way VTK is designed, most classes 
that access OpenGL directly might exist in the Rendering folder.  This is more 
of a design question anyway and relates to how to VTK classes are designed.

My class will add data structures to the pipeline but it may need a fragment 
shader for computations.

Sohail___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview


Re: [Paraview] cannot link Plugin based on Paraview 3.10.1 using Qt 4.7.4 on Mac OS OX 10.6.8 | gcc 4.2.1 | Xcode 4.0 | CMake 2.8-2 (x86_64 is on)

2011-10-04 Thread nikos yiotis
My plugin builds OK if i choose a static library, but of course i cannot
load it into PV.
Can anyone decipher the message below when i choose to build a shared lib,
that is *.dylib?
Thanks

Paraview 3.10.1 using Qt 4.7.4 on Mac OS OX 10.6.8 | gcc 4.2.1 | CMake 2.8-2

*Linking CXX shared library libZ.dylib*
*Undefined symbols for architecture x86_64:*
*  "typeinfo for pqPVAnimationWidget", referenced from:*
*  pqZ::GetTimeSteps()   in pqZ.cpp.o*
*ld: symbol(s) not found for architecture x86_64*

N




On Tue, Oct 4, 2011 at 12:41 PM, nikos yiotis wrote:

>  Hi,
>
> i am working on a Paraview Plugin that adds a new Qt progress bar type to
> the standard ParaView toolbar. I try to build the plugin as a stand-alone,
> that is the plugin is not included in Paraview build but out of source. Note
> that the plugin builds and works fine on linux x86_64 (load/unload at
> runtime).
>
> I ‘ve included /Developer/Tools/Qt to my PATH for Qt/Paraview binaries and
> included the libraries i need in LD_LIBRARY_PATH | DYLD_LIBRARY_PATH (
> LIBRARY_PATH is
> blank, not sure if i have to care about this). While trying to link the
> plug-in with a makefile i get:
>
> Linking CXX shared library libZeo.dylib
> Undefined symbols for architecture x86_64: “typeinfo for
> pqPVAnimationWidget”, referenced from: pqZeo::GetTimeSteps() in pqZeo.cpp.o
> ld: symbol(s) not found for architecture x86_64
>
> Now, pqPVAnimationWidget is related to ParaView, but i believe that
> QList pqZeo::GetTimeSteps() {…}
> makes it relevant to mention the issue here.
>
> The first idea (although irrelevant i am afraid) is to configure the
> CMakeCache file
>
> //Build architectures for OSX
> CMAKE_OSX_ARCHITECTURES:STRING=x86_64
>
> I switched to Qt 4.7.4, qmake query outputs:
> QT_INSTALL_PREFIX:/
> QT_INSTALL_DATA:/usr/local/Qt4.7
> QT_INSTALL_DOCS:/Developer/Documentation/Qt
> QT_INSTALL_HEADERS:/usr/include
> QT_INSTALL_LIBS:/Library/Frameworks
> QT_INSTALL_BINS:/Developer/Tools/Qt
> QT_INSTALL_PLUGINS:/Developer/Applications/Qt/plugins
> QT_INSTALL_IMPORTS:/Developer/Applications/Qt/imports
> QT_INSTALL_TRANSLATIONS:/Developer/Applications/Qt/translations
> QT_INSTALL_CONFIGURATION:/Library/Preferences/Qt
> QT_INSTALL_EXAMPLES:/Developer/Examples/Qt/
> QT_INSTALL_DEMOS:/Developer/Examples/Qt/Demos
> QMAKE_MKSPECS:/usr/local/Qt4.7/mkspecs
> QMAKE_VERSION:2.01a
> QT_VERSION:4.7.4
>
> I don't think there is sth wrong with my Qt installation.
>
>- I can only build Paraview 3.10.1 and my plug-in with Xcode 4.0
>(instead of makefiles i used before) only if i leave BUILT_SHARED_LIBS off,
>which is of no practical merit since the plugin is static (*.a) and cannot
>be loaded to Paraview. When i switch BUILT_SHARED_LIBS to on though, i get
>the exact same message i was getting before (failure while linking)
>
>
> *Linking CXX shared library libZ.dylib*
> *Undefined symbols for architecture x86_64:*
> *  "typeinfo for pqPVAnimationWidget", referenced from:*
> *  pqZ::GetTimeSteps()   in pqZ.cpp.o*
> *ld: symbol(s) not found for architecture x86_64*
> *
> *
>
>- When I am trying to build the Paraview 3.12.0-RC2 version, i cannot
>even build the ParaView.xcodeproj. Cmake GUI 2.8-2 gives me:
>
> Could NOT find
> /Users/nikos/Documents/codin_SRC/test/paraview/Paraview_3.12.0/ParaView-3.12.0-RC2/CMake/.paraview.version
> which is mandatory if Git is not found either.
>
> CMake Error at CMake/ParaViewDetermineVersion.cmake:68 (message):
>   Failed to determine source version correctly.
> Call Stack (most recent call first):
>   CMakeLists.txt:70 (determine_version)
>
> If i manually configure the CMakeLists.txt (which is a bad idea) the
> procedure hangs to CMakeLists.txt:70 (determine_version) again.
>
>
>- When I am trying to build the git version on Xcode, leaving aside the
>vtk warnings like in tif_unix,c "cast to pointer from integer of different
>size,
>
> it builds only a few dylibs and *not* ParaView.app. When i run it it hangs
> to the tests below that i successfully pass
>
> (  0. TestArraySerialization
>
>   1. TestArrayDenormalized )
>
> Has anyone successfully built PV (3.10.1 or RC or the git version) and her
> own plugins with Xcode 4.0?
> Let me know if you have any hints, cheers
>
>
> N
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview


Re: [Paraview] ANN: ParaView 3.12.0 RC-2 available for download

2011-10-04 Thread David Partyka
I Joe, can you redownload the tarball. I forgot to include the version file
in the tarball which the version calculation code uses when there isn't a
git repository. If it still doesn't work let me know. Thanks!

On Tue, Oct 4, 2011 at 5:22 PM, joseph insley  wrote:

> Hello,
>
> I have a question about the source distribution of 3.12.0 RC-2.   I
> understand from a message from Utkarsh back in August that the way that
> version numbers are determined has changed, and now requires a call to "git
> describe".  After downloading the source tarball from
> http://paraview.org/files/v3.12/ParaView-3.12.0-RC2.tar.gz, my attempt to
> build failed, apparently while attempting to call git describe.  So, my
> question is, will git now become a dependency for building release versions
> of ParaView?  Or is this call currently still in there because this is still
> just a release candidate, and not yet an official release?
>
> Thanks,
> joe.
>
> On Sep 29, 2011, at 2:39 PM, David Partyka wrote:
>
> The ParaView team is pleased to announce the availability of the ParaView
> 3.12.0 Release Candidate 2 binaries for download on the ParaView (
> http://paraview.org/paraview/resources/software.html). ParaView 3.12 can
> be considered as a bug-fix release with over 180 issues resolved. The
> detailed list can be found at
> http://www.paraview.org/Bug/changelog_page.php.
>
> With Python being one of the preferred means of interacting with ParaView,
> we've added support to create animation tracks that use Python scripts to
> build highly customized animations.
>
> Plugins support is one of the strong points of ParaView and with this
> release, we've made it easier to load deployed plugins on the server
> processes as well. All distributed plugins are now listed on the client as
> well as the server side.
>
> The release includes updates to LANL's streaming framework.
> The multiresolution streaming view now automatically adjusts resolution
> to match the projected image size. Also, VTK filters are now able to modify
> meta-information which means they can modify the data while still allowing
> the streaming framework to cull and prioritize pieces. An example is a new
> spherical warp filter that projects flat data onto the globe while correctly
> tracking piece bounding boxes.
>
> Also, there are updates to support users of the cosmology and windblade
> formats. For example the MaskPoints filter (used to place glyphs and in
> other places) was updated with new options that improve random sampling in
> parallel. Likewise VTK's Gaussian Splatter filter is now exposed in ParaView
> which makes it easy to visualize point set data with imaging filters. The
> cosmo and windblade readers have also been revised.
>
> This version includes some major changes under the covers. ParaView 3.12
> includes improvements to the underpinnings of ParaView ServerManager. The
> communication layer under the ParaView ServerManager was upgraded to
> minimize communication as well as making it easier to debug and trace
> messages being exchanged between client and server. We now use
> Google Protocol Buffers, for example, to exchange messages between client
> and server.
>
> In addition, there are several small but notable improvements included in
> this release for example, the views now use caching to avoid re-renders from
> repaints due to menus and dialogs popup up on the screen; volume rendering
> of uniform grids now supports shading; ability to enable specular highlights
> when using scalar coloring and others.
>
> The updated userguide can be accessed at:
> http://www.paraview.org/Wiki/ParaView/Users_Guide/Table_Of_Contents
>  Or in PDF form at:
> http://paraview.org/files/v3.12/ParaView%20Users%20Guide%20v3.12.pdf
>
> The development team has adopted a git-workflow-based development process
> that is integrated with the ParaView Bug Tracker (http://paraview.org/Bug).
> The workflow enables us to track every change that goes into ParaView and
> maintain a stable repository.
>
> We value your feedback. Please use http://paraview.uservoice.com/ or click
> on the "Tell us what you think" link on paraview.org to leave your
> feedback and vote for new features.
>  ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
>
>
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview


Re: [Paraview] ANN: ParaView 3.12.0 RC-2 available for download

2011-10-04 Thread joseph insley
Hello,

I have a question about the source distribution of 3.12.0 RC-2.   I understand 
from a message from Utkarsh back in August that the way that version numbers 
are determined has changed, and now requires a call to "git describe".  After 
downloading the source tarball from 
http://paraview.org/files/v3.12/ParaView-3.12.0-RC2.tar.gz, my attempt to build 
failed, apparently while attempting to call git describe.  So, my question is, 
will git now become a dependency for building release versions of ParaView?  Or 
is this call currently still in there because this is still just a release 
candidate, and not yet an official release?

Thanks,
joe.

On Sep 29, 2011, at 2:39 PM, David Partyka wrote:

> The ParaView team is pleased to announce the availability of the ParaView 
> 3.12.0 Release Candidate 2 binaries for download on the ParaView 
> (http://paraview.org/paraview/resources/software.html). ParaView 3.12 can be 
> considered as a bug-fix release with over 180 issues resolved. The detailed 
> list can be found at http://www.paraview.org/Bug/changelog_page.php.
> 
> With Python being one of the preferred means of interacting with ParaView, 
> we've added support to create animation tracks that use Python scripts to 
> build highly customized animations.
> 
> Plugins support is one of the strong points of ParaView and with this 
> release, we've made it easier to load deployed plugins on the server 
> processes as well. All distributed plugins are now listed on the client as 
> well as the server side.
> 
> The release includes updates to LANL's streaming framework. The 
> multiresolution streaming view now automatically adjusts resolution to match 
> the projected image size. Also, VTK filters are now able to modify 
> meta-information which means they can modify the data while still allowing 
> the streaming framework to cull and prioritize pieces. An example is a new 
> spherical warp filter that projects flat data onto the globe while correctly 
> tracking piece bounding boxes.
> 
> Also, there are updates to support users of the cosmology and windblade 
> formats. For example the MaskPoints filter (used to place glyphs and in other 
> places) was updated with new options that improve random sampling in 
> parallel. Likewise VTK's Gaussian Splatter filter is now exposed in ParaView 
> which makes it easy to visualize point set data with imaging filters. The 
> cosmo and windblade readers have also been revised.
> 
> This version includes some major changes under the covers. ParaView 3.12 
> includes improvements to the underpinnings of ParaView ServerManager. The 
> communication layer under the ParaView ServerManager was upgraded to minimize 
> communication as well as making it easier to debug and trace messages being 
> exchanged between client and server. We now use Google Protocol Buffers, for 
> example, to exchange messages between client and server.
> 
> In addition, there are several small but notable improvements included in 
> this release for example, the views now use caching to avoid re-renders from 
> repaints due to menus and dialogs popup up on the screen; volume rendering of 
> uniform grids now supports shading; ability to enable specular highlights 
> when using scalar coloring and others.
> 
> The updated userguide can be accessed at: 
> http://www.paraview.org/Wiki/ParaView/Users_Guide/Table_Of_Contents
> Or in PDF form at: 
> http://paraview.org/files/v3.12/ParaView%20Users%20Guide%20v3.12.pdf
> 
> The development team has adopted a git-workflow-based development process 
> that is integrated with the ParaView Bug Tracker (http://paraview.org/Bug). 
> The workflow enables us to track every change that goes into ParaView and 
> maintain a stable repository.
> 
> We value your feedback. Please use http://paraview.uservoice.com/ or click on 
> the "Tell us what you think" link on paraview.org to leave your feedback and 
> vote for new features.
> ___
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the ParaView Wiki at: 
> http://paraview.org/Wiki/ParaView
> 
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview

___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview


[Paraview] cannot link Plugin based on Paraview 3.10.1 using Qt 4.7.4 on Mac OS OX 10.6.8 | gcc 4.2.1 | Xcode 4.0 | CMake 2.8-2 (x86_64 is on)

2011-10-04 Thread nikos yiotis
Hi,

i am working on a Paraview Plugin that adds a new Qt progress bar type to
the standard ParaView toolbar. I try to build the plugin as a stand-alone,
that is the plugin is not included in Paraview build but out of source. Note
that the plugin builds and works fine on linux x86_64 (load/unload at
runtime).

I ‘ve included /Developer/Tools/Qt to my PATH for Qt/Paraview binaries and
included the libraries i need in LD_LIBRARY_PATH | DYLD_LIBRARY_PATH (
LIBRARY_PATH is
blank, not sure if i have to care about this). While trying to link the
plug-in with a makefile i get:

Linking CXX shared library libZeo.dylib
Undefined symbols for architecture x86_64: “typeinfo for
pqPVAnimationWidget”, referenced from: pqZeo::GetTimeSteps() in pqZeo.cpp.o
ld: symbol(s) not found for architecture x86_64

Now, pqPVAnimationWidget is related to ParaView, but i believe that
QList pqZeo::GetTimeSteps() {…}
makes it relevant to mention the issue here.

The first idea (although irrelevant i am afraid) is to configure the
CMakeCache file

//Build architectures for OSX
CMAKE_OSX_ARCHITECTURES:STRING=x86_64

I switched to Qt 4.7.4, qmake query outputs:
QT_INSTALL_PREFIX:/
QT_INSTALL_DATA:/usr/local/Qt4.7
QT_INSTALL_DOCS:/Developer/Documentation/Qt
QT_INSTALL_HEADERS:/usr/include
QT_INSTALL_LIBS:/Library/Frameworks
QT_INSTALL_BINS:/Developer/Tools/Qt
QT_INSTALL_PLUGINS:/Developer/Applications/Qt/plugins
QT_INSTALL_IMPORTS:/Developer/Applications/Qt/imports
QT_INSTALL_TRANSLATIONS:/Developer/Applications/Qt/translations
QT_INSTALL_CONFIGURATION:/Library/Preferences/Qt
QT_INSTALL_EXAMPLES:/Developer/Examples/Qt/
QT_INSTALL_DEMOS:/Developer/Examples/Qt/Demos
QMAKE_MKSPECS:/usr/local/Qt4.7/mkspecs
QMAKE_VERSION:2.01a
QT_VERSION:4.7.4

I don't think there is sth wrong with my Qt installation.

   - I can only build Paraview 3.10.1 and my plug-in with Xcode 4.0 (instead
   of makefiles i used before) only if i leave BUILT_SHARED_LIBS off, which is
   of no practical merit since the plugin is static (*.a) and cannot be loaded
   to Paraview. When i switch BUILT_SHARED_LIBS to on though, i get the exact
   same message i was getting before (failure while linking)


*Linking CXX shared library libZ.dylib*
*Undefined symbols for architecture x86_64:*
*  "typeinfo for pqPVAnimationWidget", referenced from:*
*  pqZ::GetTimeSteps()   in pqZ.cpp.o*
*ld: symbol(s) not found for architecture x86_64*
*
*

   - When I am trying to build the Paraview 3.12.0-RC2 version, i cannot
   even build the ParaView.xcodeproj. Cmake GUI 2.8-2 gives me:

Could NOT find
/Users/nikos/Documents/codin_SRC/test/paraview/Paraview_3.12.0/ParaView-3.12.0-RC2/CMake/.paraview.version
which is mandatory if Git is not found either.

CMake Error at CMake/ParaViewDetermineVersion.cmake:68 (message):
  Failed to determine source version correctly.
Call Stack (most recent call first):
  CMakeLists.txt:70 (determine_version)

If i manually configure the CMakeLists.txt (which is a bad idea) the
procedure hangs to CMakeLists.txt:70 (determine_version) again.


   - When I am trying to build the git version on Xcode, leaving aside the
   vtk warnings like in tif_unix,c "cast to pointer from integer of different
   size,

it builds only a few dylibs and *not* ParaView.app. When i run it it hangs
to the tests below that i successfully pass

(  0. TestArraySerialization

  1. TestArrayDenormalized )

Has anyone successfully built PV (3.10.1 or RC or the git version) and her
own plugins with Xcode 4.0?
Let me know if you have any hints, cheers


N
___
Powered by www.kitware.com

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: 
http://paraview.org/Wiki/ParaView

Follow this link to subscribe/unsubscribe:
http://www.paraview.org/mailman/listinfo/paraview