[Paraview-developers] load pvsm file in LiveArticles

[Sebastien Jourdain]

This is strange, I don't know what is happening here.
Which version of the code are you using?

As with the latest master, you should be able to use the FileViewer URL
directly while providing extra arguments such as the file to load.
The only issue there, is that it does not support a state file yet. But if
you will, you can create your own server script that will handle the state
file loading.

Seb


On Tue, Nov 5, 2013 at 8:46 AM, kyr <akyrieleis at gmail.com> wrote:

> When I use this line in the Jetty config file (sphere_12.vtu holds a simple
> sphere I made in paraview):
>
> pw.file_loader.cmd=./bin/pvpython
> lib/paraview-4.0/site-packages/paraview/web/pv_web_file_loader.py
> --data-dir
> . --file-to-load ../Data/sphere_12.vtu --port PORT --authKey SECRET
>
> then the sphere is briefly visibly (1 sec) but then I get the black iframe
> again but no exception. Why is that ? The same happens if I read in a file
> from ParaViewData-v4.0.1.
>
> When I use :
>
> pw.file_loader.cmd=./bin/pvpython
> lib/paraview-4.0/site-packages/paraview/web/pv_web_file_loader.py
> --data-dir
> . --file-to-load ../Data/cyl.pvsm --port PORT --authKey SECRET
>
> then I get the new runtime error in the log:
>
>  raise RuntimeError, msg
>         exceptions.RuntimeError: File not readable. No reader found for
> '../Data/cyl.pvsm'
>
>
> Thanks for any help.
> k.
>
>
>
>
>
>
> --
> View this message in context:
> http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/load-pvsm-file-in-LiveArticles-tp2573p2582.html
> Sent from the The Unofficial ParaView Developers Forum mailing list
> archive at Nabble.com.
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20131105/a040d1d2/attachment-0001.htm>