<div dir="ltr">Thanks Claude,<div><br></div><div>Here is the add-on of what functions can be called on Visualizer. (All the function with export)</div><div><br></div><div><a href="https://github.com/Kitware/visualizer/blob/master/src/app.js">https://github.com/Kitware/visualizer/blob/master/src/app.js</a><br></div><div><br></div><div>We are planning to add some helper for extracting arguments from the URL. We actually add a class in the ParaViewWeb repo, but we haven't got to the point of using it and making it available in visualizer.</div><div><br></div><div>Seb</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 11, 2017 at 7:32 AM, claude <span dir="ltr"><<a href="mailto:claude@theweak.link" target="_blank">claude@theweak.link</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Hi Debopam,</p>
<p><br>
</p>
<p>I think there is one thing to consider first before taking care
of data being passed through: if you manually start one instance
of pvw-visualizer, it means all people connecting to port 8080
will see the same thing and act on the same viewer, which means
potentially conflicting with each other action (e.g. a probable
disconnection for everyone if one decide to exit maybe?). In that
case, you need to have a virtual server that will launch a new
process every time someone connect to port 8080. That way, all
viewers are independent, the same person can open several viewers,
etc.</p>
<p><br>
</p>
<p>Now regarding the data being loaded at startup: you html index
file should have a function grabbing the 'data' parameter from a
URL, a form, a dropdown menu, etc. then sending it as a key to the
Visualizer application (so that the launcher knows which file to
load at startup).<br>
</p>
<p>It would have been complicated to explain all the details in a
email, so I made a gist with all the files and "code" addressing
both points (launcher and data):</p>
<p><a class="m_4495136292653519199moz-txt-link-freetext" href="https://gist.github.com/clavicule/7b8b3963ceb17302cff725f8dc36bc57" target="_blank">https://gist.github.com/<wbr>clavicule/<wbr>7b8b3963ceb17302cff725f8dc36bc<wbr>57</a><br>
</p>
<br>
Note that this gist was gathered info from the Paraview Web and
Visualizer online documentations: kuddos to Paraview people.<br>
2nd note: in that gist I'm giving the instructions for Apache server
(you could technically choose any other, e.g. NGinx) for Linux. I
see you are on Windows: I don't know how Apache works on Windows but
I assume (and hope) the steps and config file should be similar.<br>
<br>
I hope it helps! Good luck!<br>
cheers<br>
claude<div><div class="h5"><br>
<br>
<br>
<br>
<div class="m_4495136292653519199moz-cite-prefix">On 01/11/2017 04:10 AM, Debopam Ghoshal
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">Hi,
<div><br>
</div>
<div>
<div>We have a requirement where our application will send a
request to the paraview web server to render a specific file
(which will be available in the data given directory) in the
visualizer app, and this will be embedded within our
application page as a iframe, whose source is the Visualizer
app's index.html.</div>
<div><br>
</div>
</div>
<div>We are using the pvpython.exe executable to start the
paraview web server. The command used to start the server is:<br>
</div>
<div><br>
</div>
<div><font face="monospace, monospace">.\bin\pvpython.exe
"C:\ParaView-5.2.0-Qt4-<wbr>OpenGL2-MPI-Windows-64bit\<wbr>share\paraview-5.2\web\<wbr>visualizer\server\pvw-<wbr>visualizer.py"
--content
"C:\ParaView-5.2.0-Qt4-<wbr>OpenGL2-MPI-Windows-64bit\<wbr>share\paraview-5.2\web\<wbr>visualizer\www"
--data
"C:\ParaView-5.2.0-Qt4-<wbr>OpenGL2-MPI-Windows-64bit\<wbr>data"
--port 8080<br>
</font></div>
<div><br>
</div>
<div><br>
</div>
<div>From the command, we can see that the web content is being
served from the <span style="font-family:monospace,monospace">C:\ParaView-5.2.0-Qt4-<wbr>OpenGL2-MPI-Windows-64bit\<wbr>share\paraview-5.2\web\<wbr>visualizer\www</span> directory.
The <font face="monospace, monospace">index.html </font>file
uses the <font face="monospace, monospace">Visualizer.js </font>script
and calls the following functions:</div>
<div><br>
</div>
<div><font face="monospace, monospace">Visualizer.connect({
application: 'visualizer' });<br>
</font></div>
<div>
<div><font face="monospace, monospace">Visualizer.autoStopServer(10);</font></div>
</div>
<div><br>
</div>
<div>Is there any way to find out the available functions in the
<font face="monospace, monospace">Visualizer.js</font> script
and call them from our custom html file? What we intend to do
is to update the <font face="monospace, monospace">index.html</font>
file and</div>
<div>a. add a javascript function which will accept a filename
to be rendered</div>
<div>b. once the filename is received by this function, it will
call the visualizer and display the specified file</div>
<div>c. in the visualizer page, the open files tab should be
hidden.</div>
<div><br>
</div>
<div>Please let me know if you require any clarification.</div>
<div><br>
</div>
<div>Cheers & Best Wishes,<br>
</div>
<div>
<div>
<div class="m_4495136292653519199gmail_signature">
<div dir="ltr">
<div>Debopam</div>
<div>------------------------------<wbr>-</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="m_4495136292653519199mimeAttachmentHeader"></fieldset>
<br>
</div></div><pre>______________________________<wbr>_________________
Powered by <a class="m_4495136292653519199moz-txt-link-abbreviated" href="http://www.kitware.com" target="_blank">www.kitware.com</a>
Visit other Kitware open-source projects at <a class="m_4495136292653519199moz-txt-link-freetext" href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/<wbr>opensource/opensource.html</a>
Please keep messages on-topic and check the ParaView Wiki at: <a class="m_4495136292653519199moz-txt-link-freetext" href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/<wbr>ParaView</a>
Search the list archives at: <a class="m_4495136292653519199moz-txt-link-freetext" href="http://markmail.org/search/?q=ParaView" target="_blank">http://markmail.org/search/?q=<wbr>ParaView</a>
Follow this link to subscribe/unsubscribe:
<a class="m_4495136292653519199moz-txt-link-freetext" href="http://public.kitware.com/mailman/listinfo/paraview" target="_blank">http://public.kitware.com/<wbr>mailman/listinfo/paraview</a>
</pre>
</blockquote>
<br>
</div>
<br>______________________________<wbr>_________________<br>
Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/<wbr>opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" rel="noreferrer" target="_blank">http://paraview.org/Wiki/<wbr>ParaView</a><br>
<br>
Search the list archives at: <a href="http://markmail.org/search/?q=ParaView" rel="noreferrer" target="_blank">http://markmail.org/search/?q=<wbr>ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/paraview" rel="noreferrer" target="_blank">http://public.kitware.com/<wbr>mailman/listinfo/paraview</a><br>
<br></blockquote></div><br></div>