From debanshu at 2pirad.com  Fri Jan  2 00:08:41 2015
From: debanshu at 2pirad.com (Debanshu Saha)
Date: Fri, 2 Jan 2015 10:38:41 +0530
Subject: [Paraview-developers] Facing Problem with Server in ParaView 4.1
	Web Version
Message-ID: <CAGCCciR5ZXR-adv_uH6YzVFqAra9RAMCa0nq10T2_Sc5RMNK-w@mail.gmail.com>

Hello,

I have followed the below mentioned steps while installing ParaView Web:-

1) We have downloaded the ParaView-4.1.0-Windows-64bit.zip from ParaView
website.

2) We have downloaded the same data like can.ex2 and disk_out_ref.ex2 from
ParaView website.

3) Then we executed the below code in a batch file:-
$ unzip ParaView-4.1.0-Windows-64bit.exe
$ cd ParaView-4.1.0-Windows-64bit\bin
$ pvpython.exe
..\lib\paraview-4.1\site-packages\paraview\web\pv_web_visualizer.py
--content ..\share\paraview-4.1\www --data-dir .\path-to-share --port 8080
So, the ParaView server is started.

4) Started the application by hitting the URL
http://localhost:8080/apps/Visualizer/

Now, we facing the below problems:-

1) When we again hit the same URL in the same browser window, the server
stops. It does not happen when we hit the same URL in different browser.

Kindly advice what is wrong with it.

*Regards*
Debanshu
*2PiRad*
*Contact: *+91-8981409005
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150102/bf0b081d/attachment.html>

From sebastien.jourdain at kitware.com  Fri Jan  2 00:36:21 2015
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Thu, 1 Jan 2015 22:36:21 -0700
Subject: [Paraview-developers] Facing Problem with Server in ParaView
 4.1 Web Version
In-Reply-To: <CAGCCciR5ZXR-adv_uH6YzVFqAra9RAMCa0nq10T2_Sc5RMNK-w@mail.gmail.com>
References: <CAGCCciR5ZXR-adv_uH6YzVFqAra9RAMCa0nq10T2_Sc5RMNK-w@mail.gmail.com>
Message-ID: <CABObKxchymfQXzhtN-CCosYhx+vSzSdGCAPgbbTKiBb4Y_Etcw@mail.gmail.com>

Hi Debanshu,

what you are seeing is exactly expected. For multiple user, we expect to
start one server per client. Hence we use a launcher to automate that task
and use apache to serve everything on the same port.

What you just did was to validate that ParaViewWeb does work on your
computer.
(Which is impressive considering that Windows is not officially supported.)

You can read more here:
http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/multi_user_setup

Seb

On Thu, Jan 1, 2015 at 10:08 PM, Debanshu Saha <debanshu at 2pirad.com> wrote:

> Hello,
>
> I have followed the below mentioned steps while installing ParaView Web:-
>
> 1) We have downloaded the ParaView-4.1.0-Windows-64bit.zip from ParaView
> website.
>
> 2) We have downloaded the same data like can.ex2 and disk_out_ref.ex2 from
> ParaView website.
>
> 3) Then we executed the below code in a batch file:-
> $ unzip ParaView-4.1.0-Windows-64bit.exe
> $ cd ParaView-4.1.0-Windows-64bit\bin
> $ pvpython.exe
> ..\lib\paraview-4.1\site-packages\paraview\web\pv_web_visualizer.py
> --content ..\share\paraview-4.1\www --data-dir .\path-to-share --port 8080
> So, the ParaView server is started.
>
> 4) Started the application by hitting the URL
> http://localhost:8080/apps/Visualizer/
>
> Now, we facing the below problems:-
>
> 1) When we again hit the same URL in the same browser window, the server
> stops. It does not happen when we hit the same URL in different browser.
>
> Kindly advice what is wrong with it.
>
> *Regards*
> Debanshu
> *2PiRad*
> *Contact: *+91-8981409005
>
> _______________________________________________
> 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/20150101/b437db72/attachment.html>

From Anton.Piccardo-Selg at tessella.com  Mon Jan  5 03:25:18 2015
From: Anton.Piccardo-Selg at tessella.com (Anton.Piccardo-Selg at tessella.com)
Date: Mon, 5 Jan 2015 08:25:18 +0000
Subject: [Paraview-developers] Which signal to use when trying to register a
 change of the background color of a view?
Message-ID: <OF0CDD200A.7E5452D7-ON80257DC4.002E4333-80257DC4.002E4336@tessella.co.uk>

An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150105/53c6562b/attachment-0001.html>

From panos.asproulis at gmail.com  Mon Jan  5 06:51:44 2015
From: panos.asproulis at gmail.com (Panos Asproulis)
Date: Mon, 05 Jan 2015 12:51:44 +0100
Subject: [Paraview-developers] CSVReader - How to import Fortran Double
	Precision Data
Message-ID: <1420458704.18512.6.camel@Euler>

Hi all,

I wrote a plugin which uses the CSVReader in order to import a text file
which contains numbers. These numbers are in double precision generated
by a Fortran program and therefore they look like:

           1   0.10000D+01   0.10000D+01   0.10000D+01   0.10000D+01
0.00000D+00   0.00000D+00   0.10000D+01   0.10000D+01   0.10000D+01
0.10000D+01   0.00000D+00   0.00000D+00
           2   0.88689D+00   0.88446D+00   0.29593D+00   0.30657D+00
0.00000D+00   0.00000D+00   0.76404D+00   0.56075D+00   0.84502D+00
0.83968D+00   0.00000D+00   0.00000D+00

The problem seems to be the character "D" used by Fortran to denote
numbers in double precision. So, if I read these numbers as shown above
then ParaView interprets them as strings. If I replace the "D" character
with "E" then it interprets them as floating point numbers.

Is there any way to make the ParaView CSVReader interpret the
"D"-formatted Fortran numbers as floating point numbers?

Thanks in advance,
Panos


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150105/f365b749/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Jan  5 13:00:26 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 5 Jan 2015 13:00:26 -0500
Subject: [Paraview-developers] Which signal to use when trying to
 register a change of the background color of a view?
In-Reply-To: <OF0CDD200A.7E5452D7-ON80257DC4.002E4333-80257DC4.002E4336@tessella.co.uk>
References: <OF0CDD200A.7E5452D7-ON80257DC4.002E4333-80257DC4.002E4336@tessella.co.uk>
Message-ID: <CADHSJjATFTzyQiRBknoOsfrBT4-Zx1RFvdueurtpPCba_BzxMQ@mail.gmail.com>

There's no Qt signal, but there are VTK events.

There are multiple ways:
+ Listen to vtkCommand::ModifiedEvent fired by the property itself.
+ Listen to vtkCommand::PropertyModifiedEvent fired by the view proxy. In
it's call data, the name of the modified property will be provided.
+ Listen to vtkCommand::PropertyModifiedEvent fired by
vtkSMSessionProxyManager. It's call data is an instance
of vtkSMProxyManager::ModifiedPropertyInformation which has reference to
the proxy that was modified and the name of the property that was modified.

Utkarsh


On Mon, Jan 5, 2015 at 3:25 AM, <Anton.Piccardo-Selg at tessella.com> wrote:

> Hi,
>
> I am currently working on a customization of the ParaView application. The
> app makes use of the *pqViewSettingsReaction *class to provide the user
> with the ability to change the background color of a view. This works well,
> but I would like to keep track of the newly selected color.
>
> Hence my question: What is the appropriate signal to register a newly
> applied background color by the user?  I would like to be notified when the
> user switches the background color and then retrieve the new background
> color.
>
> Thanks and best regards,
>
> Anton
>
> This message is commercial in confidence and may be privileged. It is
> intended for the
> addressee(s) only. Access to this message by anyone else is unauthorized
> and strictly prohibited.
> If you have received this message in error, please inform the sender
> immediately. Please note that
> messages sent or received by the Tessella e-mail system may be monitored
> and stored in an
> information retrieval system.
>
>
>
> _______________________________________________
> 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/20150105/4e4b999c/attachment.html>

From dwilches at gmail.com  Mon Jan  5 16:23:36 2015
From: dwilches at gmail.com (Daniel Wilches Maradey)
Date: Mon, 5 Jan 2015 14:23:36 -0700
Subject: [Paraview-developers] Dynamically generating GUI
Message-ID: <CAEbtaO3K2a2hb8=UyZ03TCVMHd4N_eGdxnVH=ufK5k6QDm5Mqg@mail.gmail.com>

Hello,

I'm creating a ProgrammableFilter to process a source that has several
arrays.
I would like to create a GUI for it in which I present a checkbox for each
data array, so I let the user decide upon which arrays the filter will be
run.
My problem is I'm not being able to find how to dynamically generate that
GUI.

Is there any way of accomplishing it ?

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150105/167f11be/attachment.html>

From dwilches at gmail.com  Mon Jan  5 19:34:23 2015
From: dwilches at gmail.com (Daniel Wilches Maradey)
Date: Mon, 5 Jan 2015 17:34:23 -0700
Subject: [Paraview-developers] servermanager XML
Message-ID: <CAEbtaO39EuXrnJLLPRvJs47BiGiH5jPjGwVe=H=38VESMkss1Q@mail.gmail.com>

Hello,

I'm facing the same problem, the documentation that I can find online
is very scarse, for example I don't see any page where they explain
which XML elements can go inside of the ServerManager configuration
file.

I checked those 2 files suggested by Sebastien but I don't find
helpful the documentation inside either file.

What I'm trying to do is also a plugin, and I have found examples like
this that don't work as expected:

<StringVectorProperty
name="xyz"
command="SetParameter"
number_of_elements="2"
default_values_delimiter=";"
default_values="length;2">
</StringVectorProperty>

When I put that in my XML it shows a field in the GUI, and my code
says that  the value of "length is 2", but if I change the value and
click "Apply" I see that the value of the parameter "length" is not
being updated.

Where can I find information as for why that doesn't work or how should be done?

Thanks.

> Hi Patrik,
>
>you can also find some documentation in the vtkSMProxyManager.h and
>vtkSMProxy.h files.
>
>Seb


On Fri, Apr 29, 2011 at 9:48 AM, pratik <pratik.mallya at gmail.com> wrote:
> Hi,
> Where can i find a good resource to learn server manager configuration XML?
> Currently, the paraview Guide seems to be the only source, but since it is
> currently beyond my means to obtain a copy, i was looking for an another
> place (a wiki or a tutorial?).
> I wanted this for the purpose of creating a user-plugin. The wiki (about
> plugins)is really good, but there is no detailed explanation of the syntax
> of the server manager xml.
>
> pratik
> _______________________________________________
> 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
>

From sebastien.jourdain at kitware.com  Mon Jan  5 23:22:57 2015
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Mon, 5 Jan 2015 23:22:57 -0500
Subject: [Paraview-developers] servermanager XML
In-Reply-To: <CAEbtaO39EuXrnJLLPRvJs47BiGiH5jPjGwVe=H=38VESMkss1Q@mail.gmail.com>
References: <CAEbtaO39EuXrnJLLPRvJs47BiGiH5jPjGwVe=H=38VESMkss1Q@mail.gmail.com>
Message-ID: <F7DF8675-0698-4219-B36B-B9AF4F6BE468@kitware.com>

What was the new value that you put for that property?

Seb

> On Jan 5, 2015, at 19:34, Daniel Wilches Maradey <dwilches at gmail.com> wrote:
> 
> Hello,
> 
> I'm facing the same problem, the documentation that I can find online
> is very scarse, for example I don't see any page where they explain
> which XML elements can go inside of the ServerManager configuration
> file.
> 
> I checked those 2 files suggested by Sebastien but I don't find
> helpful the documentation inside either file.
> 
> What I'm trying to do is also a plugin, and I have found examples like
> this that don't work as expected:
> 
> <StringVectorProperty
> name="xyz"
> command="SetParameter"
> number_of_elements="2"
> default_values_delimiter=";"
> default_values="length;2">
> </StringVectorProperty>
> 
> When I put that in my XML it shows a field in the GUI, and my code
> says that  the value of "length is 2", but if I change the value and
> click "Apply" I see that the value of the parameter "length" is not
> being updated.
> 
> Where can I find information as for why that doesn't work or how should be done?
> 
> Thanks.
> 
>> Hi Patrik,
>> 
>> you can also find some documentation in the vtkSMProxyManager.h and
>> vtkSMProxy.h files.
>> 
>> Seb
> 
> 
>> On Fri, Apr 29, 2011 at 9:48 AM, pratik <pratik.mallya at gmail.com> wrote:
>> Hi,
>> Where can i find a good resource to learn server manager configuration XML?
>> Currently, the paraview Guide seems to be the only source, but since it is
>> currently beyond my means to obtain a copy, i was looking for an another
>> place (a wiki or a tutorial?).
>> I wanted this for the purpose of creating a user-plugin. The wiki (about
>> plugins)is really good, but there is no detailed explanation of the syntax
>> of the server manager xml.
>> 
>> pratik
>> _______________________________________________
>> 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-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers

From dwilches at gmail.com  Mon Jan  5 23:24:58 2015
From: dwilches at gmail.com (Daniel Wilches Maradey)
Date: Mon, 5 Jan 2015 21:24:58 -0700
Subject: [Paraview-developers] servermanager XML
In-Reply-To: <F7DF8675-0698-4219-B36B-B9AF4F6BE468@kitware.com>
References: <CAEbtaO39EuXrnJLLPRvJs47BiGiH5jPjGwVe=H=38VESMkss1Q@mail.gmail.com>
 <F7DF8675-0698-4219-B36B-B9AF4F6BE468@kitware.com>
Message-ID: <CAEbtaO3OG5S1a8FF8HDPcRUUD3D9c_5ia2RKpAe3JkN4spXNog@mail.gmail.com>

Hi,

I tried with these values:
      33
and
      length;33

And in both cases when I did this in the script:
      print length
It continued to print the same "2" that was printing before.

Thanks.

--
Daniel Wilches



On Mon, Jan 5, 2015 at 9:22 PM, Sebastien Jourdain
<sebastien.jourdain at kitware.com> wrote:
> What was the new value that you put for that property?
>
> Seb
>
>> On Jan 5, 2015, at 19:34, Daniel Wilches Maradey <dwilches at gmail.com> wrote:
>>
>> Hello,
>>
>> I'm facing the same problem, the documentation that I can find online
>> is very scarse, for example I don't see any page where they explain
>> which XML elements can go inside of the ServerManager configuration
>> file.
>>
>> I checked those 2 files suggested by Sebastien but I don't find
>> helpful the documentation inside either file.
>>
>> What I'm trying to do is also a plugin, and I have found examples like
>> this that don't work as expected:
>>
>> <StringVectorProperty
>> name="xyz"
>> command="SetParameter"
>> number_of_elements="2"
>> default_values_delimiter=";"
>> default_values="length;2">
>> </StringVectorProperty>
>>
>> When I put that in my XML it shows a field in the GUI, and my code
>> says that  the value of "length is 2", but if I change the value and
>> click "Apply" I see that the value of the parameter "length" is not
>> being updated.
>>
>> Where can I find information as for why that doesn't work or how should be done?
>>
>> Thanks.
>>
>>> Hi Patrik,
>>>
>>> you can also find some documentation in the vtkSMProxyManager.h and
>>> vtkSMProxy.h files.
>>>
>>> Seb
>>
>>
>>> On Fri, Apr 29, 2011 at 9:48 AM, pratik <pratik.mallya at gmail.com> wrote:
>>> Hi,
>>> Where can i find a good resource to learn server manager configuration XML?
>>> Currently, the paraview Guide seems to be the only source, but since it is
>>> currently beyond my means to obtain a copy, i was looking for an another
>>> place (a wiki or a tutorial?).
>>> I wanted this for the purpose of creating a user-plugin. The wiki (about
>>> plugins)is really good, but there is no detailed explanation of the syntax
>>> of the server manager xml.
>>>
>>> pratik
>>> _______________________________________________
>>> 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-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers

From sebastien.jourdain at kitware.com  Tue Jan  6 01:24:00 2015
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Tue, 6 Jan 2015 01:24:00 -0500
Subject: [Paraview-developers] servermanager XML
In-Reply-To: <CAEbtaO3OG5S1a8FF8HDPcRUUD3D9c_5ia2RKpAe3JkN4spXNog@mail.gmail.com>
References: <CAEbtaO39EuXrnJLLPRvJs47BiGiH5jPjGwVe=H=38VESMkss1Q@mail.gmail.com>
 <F7DF8675-0698-4219-B36B-B9AF4F6BE468@kitware.com>
 <CAEbtaO3OG5S1a8FF8HDPcRUUD3D9c_5ia2RKpAe3JkN4spXNog@mail.gmail.com>
Message-ID: <DE4D28A2-A1C8-431E-9C5E-6658D7396581@kitware.com>

Don't know exactly your implementation, but you may need a clear command. Otherwise you can only grow and replace the existing set of values. 

Seb

Sent from my iPad

> On Jan 5, 2015, at 23:24, Daniel Wilches Maradey <dwilches at gmail.com> wrote:
> 
> Hi,
> 
> I tried with these values:
>      33
> and
>      length;33
> 
> And in both cases when I did this in the script:
>      print length
> It continued to print the same "2" that was printing before.
> 
> Thanks.
> 
> --
> Daniel Wilches
> 
> 
> 
> On Mon, Jan 5, 2015 at 9:22 PM, Sebastien Jourdain
> <sebastien.jourdain at kitware.com> wrote:
>> What was the new value that you put for that property?
>> 
>> Seb
>> 
>>> On Jan 5, 2015, at 19:34, Daniel Wilches Maradey <dwilches at gmail.com> wrote:
>>> 
>>> Hello,
>>> 
>>> I'm facing the same problem, the documentation that I can find online
>>> is very scarse, for example I don't see any page where they explain
>>> which XML elements can go inside of the ServerManager configuration
>>> file.
>>> 
>>> I checked those 2 files suggested by Sebastien but I don't find
>>> helpful the documentation inside either file.
>>> 
>>> What I'm trying to do is also a plugin, and I have found examples like
>>> this that don't work as expected:
>>> 
>>> <StringVectorProperty
>>> name="xyz"
>>> command="SetParameter"
>>> number_of_elements="2"
>>> default_values_delimiter=";"
>>> default_values="length;2">
>>> </StringVectorProperty>
>>> 
>>> When I put that in my XML it shows a field in the GUI, and my code
>>> says that  the value of "length is 2", but if I change the value and
>>> click "Apply" I see that the value of the parameter "length" is not
>>> being updated.
>>> 
>>> Where can I find information as for why that doesn't work or how should be done?
>>> 
>>> Thanks.
>>> 
>>>> Hi Patrik,
>>>> 
>>>> you can also find some documentation in the vtkSMProxyManager.h and
>>>> vtkSMProxy.h files.
>>>> 
>>>> Seb
>>> 
>>> 
>>>> On Fri, Apr 29, 2011 at 9:48 AM, pratik <pratik.mallya at gmail.com> wrote:
>>>> Hi,
>>>> Where can i find a good resource to learn server manager configuration XML?
>>>> Currently, the paraview Guide seems to be the only source, but since it is
>>>> currently beyond my means to obtain a copy, i was looking for an another
>>>> place (a wiki or a tutorial?).
>>>> I wanted this for the purpose of creating a user-plugin. The wiki (about
>>>> plugins)is really good, but there is no detailed explanation of the syntax
>>>> of the server manager xml.
>>>> 
>>>> pratik
>>>> _______________________________________________
>>>> 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-developers mailing list
>>> Paraview-developers at paraview.org
>>> http://public.kitware.com/mailman/listinfo/paraview-developers

From dwilches at gmail.com  Tue Jan  6 10:19:18 2015
From: dwilches at gmail.com (Daniel Wilches Maradey)
Date: Tue, 6 Jan 2015 08:19:18 -0700
Subject: [Paraview-developers] servermanager XML
In-Reply-To: <DE4D28A2-A1C8-431E-9C5E-6658D7396581@kitware.com>
References: <CAEbtaO39EuXrnJLLPRvJs47BiGiH5jPjGwVe=H=38VESMkss1Q@mail.gmail.com>
 <F7DF8675-0698-4219-B36B-B9AF4F6BE468@kitware.com>
 <CAEbtaO3OG5S1a8FF8HDPcRUUD3D9c_5ia2RKpAe3JkN4spXNog@mail.gmail.com>
 <DE4D28A2-A1C8-431E-9C5E-6658D7396581@kitware.com>
Message-ID: <CAEbtaO0_x_9w3qchJuOz0jM8jNZ_iXRrY6qSSbbeYp=EBve4ZA@mail.gmail.com>

Hello,

What do you mean by a clear command? In my case I'm using the command
is SetParameter from the class vtkPythonProgrammableFilter.

I'm actually starting my implementation from scratch, I have nothing
but the XML file based on the helix.xml of the
Examples/Plugins/HelixSource folder.
In that file there is this code:

     <!-- python script references a variable "numPts"
          we expose this as a property allowing the user to set it -->
     <StringVectorProperty
       name="NumberOfPoints"
       command="SetParameter"
       number_of_elements="2"
       default_values_delimiter=";"
       default_values="numPts;80">
     </StringVectorProperty>

I was hoping to use the same approach to set my own parameters for my filter.

But I'm not sure if I'm missing something as the parameter is set fine
at the beginning of the script, but later its value is not updated as
I update the GUI.

Thanks.

--
Daniel Wilches



On Mon, Jan 5, 2015 at 11:24 PM, Sebastien Jourdain
<sebastien.jourdain at kitware.com> wrote:
> Don't know exactly your implementation, but you may need a clear command. Otherwise you can only grow and replace the existing set of values.
>
> Seb
>
> Sent from my iPad
>
>> On Jan 5, 2015, at 23:24, Daniel Wilches Maradey <dwilches at gmail.com> wrote:
>>
>> Hi,
>>
>> I tried with these values:
>>      33
>> and
>>      length;33
>>
>> And in both cases when I did this in the script:
>>      print length
>> It continued to print the same "2" that was printing before.
>>
>> Thanks.
>>
>> --
>> Daniel Wilches
>>
>>
>>
>> On Mon, Jan 5, 2015 at 9:22 PM, Sebastien Jourdain
>> <sebastien.jourdain at kitware.com> wrote:
>>> What was the new value that you put for that property?
>>>
>>> Seb
>>>
>>>> On Jan 5, 2015, at 19:34, Daniel Wilches Maradey <dwilches at gmail.com> wrote:
>>>>
>>>> Hello,
>>>>
>>>> I'm facing the same problem, the documentation that I can find online
>>>> is very scarse, for example I don't see any page where they explain
>>>> which XML elements can go inside of the ServerManager configuration
>>>> file.
>>>>
>>>> I checked those 2 files suggested by Sebastien but I don't find
>>>> helpful the documentation inside either file.
>>>>
>>>> What I'm trying to do is also a plugin, and I have found examples like
>>>> this that don't work as expected:
>>>>
>>>> <StringVectorProperty
>>>> name="xyz"
>>>> command="SetParameter"
>>>> number_of_elements="2"
>>>> default_values_delimiter=";"
>>>> default_values="length;2">
>>>> </StringVectorProperty>
>>>>
>>>> When I put that in my XML it shows a field in the GUI, and my code
>>>> says that  the value of "length is 2", but if I change the value and
>>>> click "Apply" I see that the value of the parameter "length" is not
>>>> being updated.
>>>>
>>>> Where can I find information as for why that doesn't work or how should be done?
>>>>
>>>> Thanks.
>>>>
>>>>> Hi Patrik,
>>>>>
>>>>> you can also find some documentation in the vtkSMProxyManager.h and
>>>>> vtkSMProxy.h files.
>>>>>
>>>>> Seb
>>>>
>>>>
>>>>> On Fri, Apr 29, 2011 at 9:48 AM, pratik <pratik.mallya at gmail.com> wrote:
>>>>> Hi,
>>>>> Where can i find a good resource to learn server manager configuration XML?
>>>>> Currently, the paraview Guide seems to be the only source, but since it is
>>>>> currently beyond my means to obtain a copy, i was looking for an another
>>>>> place (a wiki or a tutorial?).
>>>>> I wanted this for the purpose of creating a user-plugin. The wiki (about
>>>>> plugins)is really good, but there is no detailed explanation of the syntax
>>>>> of the server manager xml.
>>>>>
>>>>> pratik
>>>>> _______________________________________________
>>>>> 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-developers mailing list
>>>> Paraview-developers at paraview.org
>>>> http://public.kitware.com/mailman/listinfo/paraview-developers

From sebastien.jourdain at kitware.com  Tue Jan  6 10:38:34 2015
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Tue, 6 Jan 2015 10:38:34 -0500
Subject: [Paraview-developers] servermanager XML
In-Reply-To: <CAEbtaO0_x_9w3qchJuOz0jM8jNZ_iXRrY6qSSbbeYp=EBve4ZA@mail.gmail.com>
References: <CAEbtaO39EuXrnJLLPRvJs47BiGiH5jPjGwVe=H=38VESMkss1Q@mail.gmail.com>
 <F7DF8675-0698-4219-B36B-B9AF4F6BE468@kitware.com>
 <CAEbtaO3OG5S1a8FF8HDPcRUUD3D9c_5ia2RKpAe3JkN4spXNog@mail.gmail.com>
 <DE4D28A2-A1C8-431E-9C5E-6658D7396581@kitware.com>
 <CAEbtaO0_x_9w3qchJuOz0jM8jNZ_iXRrY6qSSbbeYp=EBve4ZA@mail.gmail.com>
Message-ID: <CABObKxdyRnTWXUNgWeEtksHDsQkz+pQHu-JY+DqsOL9Zht481Q@mail.gmail.com>

Hi Daniel,

I miss read your intention of what you were trying to do.
I guess what you are doing seems to be correct.
I was thinking that you had a single property to set several parameters.

Looking at the code, I did not notice any particular/possible issue.

But maybe it is because, I don't see how and where you access those
parameters in your filter?

Sorry,

Seb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150106/06d86203/attachment.html>

From dwilches at gmail.com  Tue Jan  6 10:48:41 2015
From: dwilches at gmail.com (Daniel Wilches Maradey)
Date: Tue, 6 Jan 2015 08:48:41 -0700
Subject: [Paraview-developers] servermanager XML
In-Reply-To: <CABObKxdyRnTWXUNgWeEtksHDsQkz+pQHu-JY+DqsOL9Zht481Q@mail.gmail.com>
References: <CAEbtaO39EuXrnJLLPRvJs47BiGiH5jPjGwVe=H=38VESMkss1Q@mail.gmail.com>
 <F7DF8675-0698-4219-B36B-B9AF4F6BE468@kitware.com>
 <CAEbtaO3OG5S1a8FF8HDPcRUUD3D9c_5ia2RKpAe3JkN4spXNog@mail.gmail.com>
 <DE4D28A2-A1C8-431E-9C5E-6658D7396581@kitware.com>
 <CAEbtaO0_x_9w3qchJuOz0jM8jNZ_iXRrY6qSSbbeYp=EBve4ZA@mail.gmail.com>
 <CABObKxdyRnTWXUNgWeEtksHDsQkz+pQHu-JY+DqsOL9Zht481Q@mail.gmail.com>
Message-ID: <CAEbtaO3GbGwjy4Pc=PS9gHGPTx6hYA1mxkOuery-Ucr82eRu+A@mail.gmail.com>

Hi,

In my filter I just have one line:

print length

I have nothing more as I'm only checking how the parameters work.

Then when I apply the filter I can see in the output window the value
"2", which was the default value for "length", so far it is OK.
Then I go and change the value of the property, say to "33", and I
also change the script's text to force the filter to run again (I just
put an extra empty line, that's all), and then hit Apply. At this
point the value "2" is being printed again, instead of the expected
"33". So I don't get how to update the value at all.

(I have also tried setting the value to "length;33" in case the name
was necessary, but the same result, it's not updated)

Thanks for your help.

--
Daniel Wilches



On Tue, Jan 6, 2015 at 8:38 AM, Sebastien Jourdain
<sebastien.jourdain at kitware.com> wrote:
> Hi Daniel,
>
> I miss read your intention of what you were trying to do.
> I guess what you are doing seems to be correct.
> I was thinking that you had a single property to set several parameters.
>
> Looking at the code, I did not notice any particular/possible issue.
>
> But maybe it is because, I don't see how and where you access those
> parameters in your filter?
>
> Sorry,
>
> Seb

From cory.quammen at kitware.com  Tue Jan  6 12:02:55 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 6 Jan 2015 12:02:55 -0500
Subject: [Paraview-developers] Dynamically generating GUI
In-Reply-To: <CAEbtaO3K2a2hb8=UyZ03TCVMHd4N_eGdxnVH=ufK5k6QDm5Mqg@mail.gmail.com>
References: <CAEbtaO3K2a2hb8=UyZ03TCVMHd4N_eGdxnVH=ufK5k6QDm5Mqg@mail.gmail.com>
Message-ID: <CAB5Fpx6CrMmPftYoHydCEs-N2Z6Xk+A6B6egvJbD4WRtO+vuaQ@mail.gmail.com>

Hi Daniel,

It *may* be possible to do this with the ProgrammableFilter, but it's
not obvious to me how to do it. It would likely be easier to present a
combo box that lets you user pick one array on which to operate.

Alternatively, you could write a C++ plugin and follow what I've
sketched out in this archived message to present the interface you've
described:

http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/Servermanager-XML-Displaying-a-list-of-strings-along-with-selection-tp3134p3135.html

Hope that helps,
Cory

On Mon, Jan 5, 2015 at 4:23 PM, Daniel Wilches Maradey
<dwilches at gmail.com> wrote:
> Hello,
>
> I'm creating a ProgrammableFilter to process a source that has several
> arrays.
> I would like to create a GUI for it in which I present a checkbox for each
> data array, so I let the user decide upon which arrays the filter will be
> run.
> My problem is I'm not being able to find how to dynamically generate that
> GUI.
>
> Is there any way of accomplishing it ?
>
> Thanks.
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From utkarsh.ayachit at kitware.com  Tue Jan  6 12:16:52 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 6 Jan 2015 12:16:52 -0500
Subject: [Paraview-developers] Dynamically generating GUI
In-Reply-To: <CAB5Fpx6CrMmPftYoHydCEs-N2Z6Xk+A6B6egvJbD4WRtO+vuaQ@mail.gmail.com>
References: <CAEbtaO3K2a2hb8=UyZ03TCVMHd4N_eGdxnVH=ufK5k6QDm5Mqg@mail.gmail.com>
 <CAB5Fpx6CrMmPftYoHydCEs-N2Z6Xk+A6B6egvJbD4WRtO+vuaQ@mail.gmail.com>
Message-ID: <CADHSJjCVW7_c+qrrhkRUgo6cQpDRcq60Ni-HjK_S5SPomTq+iw@mail.gmail.com>

You may also want to check this post out:
http://www.kitware.com/blog/home/post/534

Utkarsh

On Tue, Jan 6, 2015 at 12:02 PM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Hi Daniel,
>
> It *may* be possible to do this with the ProgrammableFilter, but it's
> not obvious to me how to do it. It would likely be easier to present a
> combo box that lets you user pick one array on which to operate.
>
> Alternatively, you could write a C++ plugin and follow what I've
> sketched out in this archived message to present the interface you've
> described:
>
>
> http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/Servermanager-XML-Displaying-a-list-of-strings-along-with-selection-tp3134p3135.html
>
> Hope that helps,
> Cory
>
> On Mon, Jan 5, 2015 at 4:23 PM, Daniel Wilches Maradey
> <dwilches at gmail.com> wrote:
> > Hello,
> >
> > I'm creating a ProgrammableFilter to process a source that has several
> > arrays.
> > I would like to create a GUI for it in which I present a checkbox for
> each
> > data array, so I let the user decide upon which arrays the filter will be
> > run.
> > My problem is I'm not being able to find how to dynamically generate that
> > GUI.
> >
> > Is there any way of accomplishing it ?
> >
> > Thanks.
> >
> >
> > _______________________________________________
> > Paraview-developers mailing list
> > Paraview-developers at paraview.org
> > http://public.kitware.com/mailman/listinfo/paraview-developers
> >
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
> _______________________________________________
> 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/20150106/6bd6dd2f/attachment-0001.html>

From dwilches at gmail.com  Tue Jan  6 12:45:05 2015
From: dwilches at gmail.com (Daniel Wilches Maradey)
Date: Tue, 6 Jan 2015 10:45:05 -0700
Subject: [Paraview-developers] Dynamically generating GUI
In-Reply-To: <CAB5Fpx6CrMmPftYoHydCEs-N2Z6Xk+A6B6egvJbD4WRtO+vuaQ@mail.gmail.com>
References: <CAEbtaO3K2a2hb8=UyZ03TCVMHd4N_eGdxnVH=ufK5k6QDm5Mqg@mail.gmail.com>
 <CAB5Fpx6CrMmPftYoHydCEs-N2Z6Xk+A6B6egvJbD4WRtO+vuaQ@mail.gmail.com>
Message-ID: <CAEbtaO3tnekYXSjD09Vtf-xzNaEeSNgarvQqe1XDL8ZBoneWZQ@mail.gmail.com>

Hi Cory,

I think the 3rd point will solve my problem.

Thanks for the information!


On Tue, Jan 6, 2015 at 10:02 AM, Cory Quammen <cory.quammen at kitware.com> wrote:
> Hi Daniel,
>
> It *may* be possible to do this with the ProgrammableFilter, but it's
> not obvious to me how to do it. It would likely be easier to present a
> combo box that lets you user pick one array on which to operate.
>
> Alternatively, you could write a C++ plugin and follow what I've
> sketched out in this archived message to present the interface you've
> described:
>
> http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/Servermanager-XML-Displaying-a-list-of-strings-along-with-selection-tp3134p3135.html
>
> Hope that helps,
> Cory
>
> On Mon, Jan 5, 2015 at 4:23 PM, Daniel Wilches Maradey
> <dwilches at gmail.com> wrote:
>> Hello,
>>
>> I'm creating a ProgrammableFilter to process a source that has several
>> arrays.
>> I would like to create a GUI for it in which I present a checkbox for each
>> data array, so I let the user decide upon which arrays the filter will be
>> run.
>> My problem is I'm not being able to find how to dynamically generate that
>> GUI.
>>
>> Is there any way of accomplishing it ?
>>
>> Thanks.
>>
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.

From dwilches at gmail.com  Tue Jan  6 16:22:30 2015
From: dwilches at gmail.com (Daniel Wilches Maradey)
Date: Tue, 6 Jan 2015 14:22:30 -0700
Subject: [Paraview-developers] Dynamically generating GUI
In-Reply-To: <CAEbtaO3tnekYXSjD09Vtf-xzNaEeSNgarvQqe1XDL8ZBoneWZQ@mail.gmail.com>
References: <CAEbtaO3K2a2hb8=UyZ03TCVMHd4N_eGdxnVH=ufK5k6QDm5Mqg@mail.gmail.com>
 <CAB5Fpx6CrMmPftYoHydCEs-N2Z6Xk+A6B6egvJbD4WRtO+vuaQ@mail.gmail.com>
 <CAEbtaO3tnekYXSjD09Vtf-xzNaEeSNgarvQqe1XDL8ZBoneWZQ@mail.gmail.com>
Message-ID: <CAEbtaO0CS_91W9JrR=r=Cq27qb=7B-V30SBUdXp0xSngr6uDQg@mail.gmail.com>

Hello again,

I'll post here what solution worked for me so other people can find it
(I modified a bit what you sent me in your last mail).
I've also updated the wiki with this info (why is there so many info
here in the mailing-list that has not reached the Wiki?).

In my XML I put this:

      <StringVectorProperty command="SetCellArrayStatus"
                            element_types="2 0"
                            information_property="CellArrayInfo"
                            label="Cell Arrays"
                            name="CellArrayStatus"
                            number_of_elements="0"
                            number_of_elements_per_command="2"
                            repeat_command="1">
        <ArrayListDomain name="array_list"
                         attribute_type="Scalars"
                         input_domain_name="inputs_array">
          <RequiredProperties>
            <Property name="Input"
                      function="Input" />
          </RequiredProperties>
        </ArrayListDomain>
      </StringVectorProperty>

And now I see all the checkboxes next to the name of the arrays, and I
can select one or several of them.

Anyway, I haven't been able yet to get the list of checked arrays from
inside Python, but I'm starting to think I will need for that to make
a subclass of vtkProgrammableFilter in C++ to store the array in some
of its fields, Am I right about this?

Thanks


On Tue, Jan 6, 2015 at 10:45 AM, Daniel Wilches Maradey
<dwilches at gmail.com> wrote:
>
> Hi Cory,
>
> I think the 3rd point will solve my problem.
>
> Thanks for the information!
>
>
> On Tue, Jan 6, 2015 at 10:02 AM, Cory Quammen <cory.quammen at kitware.com> wrote:
> > Hi Daniel,
> >
> > It *may* be possible to do this with the ProgrammableFilter, but it's
> > not obvious to me how to do it. It would likely be easier to present a
> > combo box that lets you user pick one array on which to operate.
> >
> > Alternatively, you could write a C++ plugin and follow what I've
> > sketched out in this archived message to present the interface you've
> > described:
> >
> > http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/Servermanager-XML-Displaying-a-list-of-strings-along-with-selection-tp3134p3135.html
> >
> > Hope that helps,
> > Cory
> >
> > On Mon, Jan 5, 2015 at 4:23 PM, Daniel Wilches Maradey
> > <dwilches at gmail.com> wrote:
> >> Hello,
> >>
> >> I'm creating a ProgrammableFilter to process a source that has several
> >> arrays.
> >> I would like to create a GUI for it in which I present a checkbox for each
> >> data array, so I let the user decide upon which arrays the filter will be
> >> run.
> >> My problem is I'm not being able to find how to dynamically generate that
> >> GUI.
> >>
> >> Is there any way of accomplishing it ?
> >>
> >> Thanks.
> >>
> >>
> >> _______________________________________________
> >> Paraview-developers mailing list
> >> Paraview-developers at paraview.org
> >> http://public.kitware.com/mailman/listinfo/paraview-developers
> >>
> >
> >
> >
> > --
> > Cory Quammen
> > R&D Engineer
> > Kitware, Inc.

From cory.quammen at kitware.com  Tue Jan  6 20:20:11 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 6 Jan 2015 20:20:11 -0500
Subject: [Paraview-developers] Dynamically generating GUI
In-Reply-To: <CAEbtaO0CS_91W9JrR=r=Cq27qb=7B-V30SBUdXp0xSngr6uDQg@mail.gmail.com>
References: <CAEbtaO3K2a2hb8=UyZ03TCVMHd4N_eGdxnVH=ufK5k6QDm5Mqg@mail.gmail.com>
 <CAB5Fpx6CrMmPftYoHydCEs-N2Z6Xk+A6B6egvJbD4WRtO+vuaQ@mail.gmail.com>
 <CAEbtaO3tnekYXSjD09Vtf-xzNaEeSNgarvQqe1XDL8ZBoneWZQ@mail.gmail.com>
 <CAEbtaO0CS_91W9JrR=r=Cq27qb=7B-V30SBUdXp0xSngr6uDQg@mail.gmail.com>
Message-ID: <CAB5Fpx5LoreJZU+MzaUkVo_X_u28LLCFYpaRgAmBVzDiO=BEjA@mail.gmail.com>

> I've also updated the wiki with this info (why is there so many info
> here in the mailing-list that has not reached the Wiki?).

There are only so many hours in the day :-(

> In my XML I put this:
>
>       <StringVectorProperty command="SetCellArrayStatus"
>                             element_types="2 0"
>                             information_property="CellArrayInfo"
>                             label="Cell Arrays"
>                             name="CellArrayStatus"
>                             number_of_elements="0"
>                             number_of_elements_per_command="2"
>                             repeat_command="1">
>         <ArrayListDomain name="array_list"
>                          attribute_type="Scalars"
>                          input_domain_name="inputs_array">
>           <RequiredProperties>
>             <Property name="Input"
>                       function="Input" />
>           </RequiredProperties>
>         </ArrayListDomain>
>       </StringVectorProperty>
>
> And now I see all the checkboxes next to the name of the arrays, and I
> can select one or several of them.

Excellent.

> Anyway, I haven't been able yet to get the list of checked arrays from
> inside Python, but I'm starting to think I will need for that to make
> a subclass of vtkProgrammableFilter in C++ to store the array in some
> of its fields, Am I right about this?

Yes, this would definitely work. The accessor method
GetCellArrayStatus() should be wrapped in Python so that it is
available by calling

self.GetCellArrayStatus()

in your script.

- Cory

> Thanks
>
>
> On Tue, Jan 6, 2015 at 10:45 AM, Daniel Wilches Maradey
> <dwilches at gmail.com> wrote:
>>
>> Hi Cory,
>>
>> I think the 3rd point will solve my problem.
>>
>> Thanks for the information!
>>
>>
>> On Tue, Jan 6, 2015 at 10:02 AM, Cory Quammen <cory.quammen at kitware.com> wrote:
>> > Hi Daniel,
>> >
>> > It *may* be possible to do this with the ProgrammableFilter, but it's
>> > not obvious to me how to do it. It would likely be easier to present a
>> > combo box that lets you user pick one array on which to operate.
>> >
>> > Alternatively, you could write a C++ plugin and follow what I've
>> > sketched out in this archived message to present the interface you've
>> > described:
>> >
>> > http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/Servermanager-XML-Displaying-a-list-of-strings-along-with-selection-tp3134p3135.html
>> >
>> > Hope that helps,
>> > Cory
>> >
>> > On Mon, Jan 5, 2015 at 4:23 PM, Daniel Wilches Maradey
>> > <dwilches at gmail.com> wrote:
>> >> Hello,
>> >>
>> >> I'm creating a ProgrammableFilter to process a source that has several
>> >> arrays.
>> >> I would like to create a GUI for it in which I present a checkbox for each
>> >> data array, so I let the user decide upon which arrays the filter will be
>> >> run.
>> >> My problem is I'm not being able to find how to dynamically generate that
>> >> GUI.
>> >>
>> >> Is there any way of accomplishing it ?
>> >>
>> >> Thanks.
>> >>
>> >>
>> >> _______________________________________________
>> >> Paraview-developers mailing list
>> >> Paraview-developers at paraview.org
>> >> http://public.kitware.com/mailman/listinfo/paraview-developers
>> >>
>> >
>> >
>> >
>> > --
>> > Cory Quammen
>> > R&D Engineer
>> > Kitware, Inc.



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From dwilches at gmail.com  Tue Jan  6 20:39:16 2015
From: dwilches at gmail.com (Daniel Wilches Maradey)
Date: Tue, 6 Jan 2015 18:39:16 -0700
Subject: [Paraview-developers] Dynamically generating GUI
In-Reply-To: <CAB5Fpx5LoreJZU+MzaUkVo_X_u28LLCFYpaRgAmBVzDiO=BEjA@mail.gmail.com>
References: <CAEbtaO3K2a2hb8=UyZ03TCVMHd4N_eGdxnVH=ufK5k6QDm5Mqg@mail.gmail.com>
 <CAB5Fpx6CrMmPftYoHydCEs-N2Z6Xk+A6B6egvJbD4WRtO+vuaQ@mail.gmail.com>
 <CAEbtaO3tnekYXSjD09Vtf-xzNaEeSNgarvQqe1XDL8ZBoneWZQ@mail.gmail.com>
 <CAEbtaO0CS_91W9JrR=r=Cq27qb=7B-V30SBUdXp0xSngr6uDQg@mail.gmail.com>
 <CAB5Fpx5LoreJZU+MzaUkVo_X_u28LLCFYpaRgAmBVzDiO=BEjA@mail.gmail.com>
Message-ID: <CAEbtaO0NhdDm7u=3Z_NihH3O_dD+WQcc7Nz045T9GH8ifEzu1g@mail.gmail.com>

Hi,

I had't heard about wrapping the C++ methods in Python
("GetCellArrayStatus() should be wrapped in Python").
I was assuming the DLL was going to have all the necessary code for
being invoked by Python.

Do you have some resource where that process is explained?

Thanks.



On Tue, Jan 6, 2015 at 6:20 PM, Cory Quammen <cory.quammen at kitware.com> wrote:
>> I've also updated the wiki with this info (why is there so many info
>> here in the mailing-list that has not reached the Wiki?).
>
> There are only so many hours in the day :-(
>
>> In my XML I put this:
>>
>>       <StringVectorProperty command="SetCellArrayStatus"
>>                             element_types="2 0"
>>                             information_property="CellArrayInfo"
>>                             label="Cell Arrays"
>>                             name="CellArrayStatus"
>>                             number_of_elements="0"
>>                             number_of_elements_per_command="2"
>>                             repeat_command="1">
>>         <ArrayListDomain name="array_list"
>>                          attribute_type="Scalars"
>>                          input_domain_name="inputs_array">
>>           <RequiredProperties>
>>             <Property name="Input"
>>                       function="Input" />
>>           </RequiredProperties>
>>         </ArrayListDomain>
>>       </StringVectorProperty>
>>
>> And now I see all the checkboxes next to the name of the arrays, and I
>> can select one or several of them.
>
> Excellent.
>
>> Anyway, I haven't been able yet to get the list of checked arrays from
>> inside Python, but I'm starting to think I will need for that to make
>> a subclass of vtkProgrammableFilter in C++ to store the array in some
>> of its fields, Am I right about this?
>
> Yes, this would definitely work. The accessor method
> GetCellArrayStatus() should be wrapped in Python so that it is
> available by calling
>
> self.GetCellArrayStatus()
>
> in your script.
>
> - Cory
>
>> Thanks
>>
>>
>> On Tue, Jan 6, 2015 at 10:45 AM, Daniel Wilches Maradey
>> <dwilches at gmail.com> wrote:
>>>
>>> Hi Cory,
>>>
>>> I think the 3rd point will solve my problem.
>>>
>>> Thanks for the information!
>>>
>>>
>>> On Tue, Jan 6, 2015 at 10:02 AM, Cory Quammen <cory.quammen at kitware.com> wrote:
>>> > Hi Daniel,
>>> >
>>> > It *may* be possible to do this with the ProgrammableFilter, but it's
>>> > not obvious to me how to do it. It would likely be easier to present a
>>> > combo box that lets you user pick one array on which to operate.
>>> >
>>> > Alternatively, you could write a C++ plugin and follow what I've
>>> > sketched out in this archived message to present the interface you've
>>> > described:
>>> >
>>> > http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/Servermanager-XML-Displaying-a-list-of-strings-along-with-selection-tp3134p3135.html
>>> >
>>> > Hope that helps,
>>> > Cory
>>> >
>>> > On Mon, Jan 5, 2015 at 4:23 PM, Daniel Wilches Maradey
>>> > <dwilches at gmail.com> wrote:
>>> >> Hello,
>>> >>
>>> >> I'm creating a ProgrammableFilter to process a source that has several
>>> >> arrays.
>>> >> I would like to create a GUI for it in which I present a checkbox for each
>>> >> data array, so I let the user decide upon which arrays the filter will be
>>> >> run.
>>> >> My problem is I'm not being able to find how to dynamically generate that
>>> >> GUI.
>>> >>
>>> >> Is there any way of accomplishing it ?
>>> >>
>>> >> Thanks.
>>> >>
>>> >>
>>> >> _______________________________________________
>>> >> Paraview-developers mailing list
>>> >> Paraview-developers at paraview.org
>>> >> http://public.kitware.com/mailman/listinfo/paraview-developers
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Cory Quammen
>>> > R&D Engineer
>>> > Kitware, Inc.
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.

From cory.quammen at kitware.com  Tue Jan  6 22:45:28 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Tue, 6 Jan 2015 22:45:28 -0500
Subject: [Paraview-developers] Dynamically generating GUI
In-Reply-To: <CAEbtaO0NhdDm7u=3Z_NihH3O_dD+WQcc7Nz045T9GH8ifEzu1g@mail.gmail.com>
References: <CAEbtaO3K2a2hb8=UyZ03TCVMHd4N_eGdxnVH=ufK5k6QDm5Mqg@mail.gmail.com>
 <CAB5Fpx6CrMmPftYoHydCEs-N2Z6Xk+A6B6egvJbD4WRtO+vuaQ@mail.gmail.com>
 <CAEbtaO3tnekYXSjD09Vtf-xzNaEeSNgarvQqe1XDL8ZBoneWZQ@mail.gmail.com>
 <CAEbtaO0CS_91W9JrR=r=Cq27qb=7B-V30SBUdXp0xSngr6uDQg@mail.gmail.com>
 <CAB5Fpx5LoreJZU+MzaUkVo_X_u28LLCFYpaRgAmBVzDiO=BEjA@mail.gmail.com>
 <CAEbtaO0NhdDm7u=3Z_NihH3O_dD+WQcc7Nz045T9GH8ifEzu1g@mail.gmail.com>
Message-ID: <CAB5Fpx6qKa7eehu0JN4N9eUgArWqdncQiVaU90V9ACMmx7PFzQ@mail.gmail.com>

> I was assuming the DLL was going to have all the necessary code for
> being invoked by Python.

Yes, you are correct. What I meant was that GetCellArrayStatus()
should be wrapped automatically in the build process and will be
available to call in Python, not that you have to do anything to make
that possible.

> Do you have some resource where that process is explained?
>
> Thanks.
>
>
>
> On Tue, Jan 6, 2015 at 6:20 PM, Cory Quammen <cory.quammen at kitware.com> wrote:
>>> I've also updated the wiki with this info (why is there so many info
>>> here in the mailing-list that has not reached the Wiki?).
>>
>> There are only so many hours in the day :-(
>>
>>> In my XML I put this:
>>>
>>>       <StringVectorProperty command="SetCellArrayStatus"
>>>                             element_types="2 0"
>>>                             information_property="CellArrayInfo"
>>>                             label="Cell Arrays"
>>>                             name="CellArrayStatus"
>>>                             number_of_elements="0"
>>>                             number_of_elements_per_command="2"
>>>                             repeat_command="1">
>>>         <ArrayListDomain name="array_list"
>>>                          attribute_type="Scalars"
>>>                          input_domain_name="inputs_array">
>>>           <RequiredProperties>
>>>             <Property name="Input"
>>>                       function="Input" />
>>>           </RequiredProperties>
>>>         </ArrayListDomain>
>>>       </StringVectorProperty>
>>>
>>> And now I see all the checkboxes next to the name of the arrays, and I
>>> can select one or several of them.
>>
>> Excellent.
>>
>>> Anyway, I haven't been able yet to get the list of checked arrays from
>>> inside Python, but I'm starting to think I will need for that to make
>>> a subclass of vtkProgrammableFilter in C++ to store the array in some
>>> of its fields, Am I right about this?
>>
>> Yes, this would definitely work. The accessor method
>> GetCellArrayStatus() should be wrapped in Python so that it is
>> available by calling
>>
>> self.GetCellArrayStatus()
>>
>> in your script.
>>
>> - Cory
>>
>>> Thanks
>>>
>>>
>>> On Tue, Jan 6, 2015 at 10:45 AM, Daniel Wilches Maradey
>>> <dwilches at gmail.com> wrote:
>>>>
>>>> Hi Cory,
>>>>
>>>> I think the 3rd point will solve my problem.
>>>>
>>>> Thanks for the information!
>>>>
>>>>
>>>> On Tue, Jan 6, 2015 at 10:02 AM, Cory Quammen <cory.quammen at kitware.com> wrote:
>>>> > Hi Daniel,
>>>> >
>>>> > It *may* be possible to do this with the ProgrammableFilter, but it's
>>>> > not obvious to me how to do it. It would likely be easier to present a
>>>> > combo box that lets you user pick one array on which to operate.
>>>> >
>>>> > Alternatively, you could write a C++ plugin and follow what I've
>>>> > sketched out in this archived message to present the interface you've
>>>> > described:
>>>> >
>>>> > http://the-unofficial-paraview-developers-forum.34153.x6.nabble.com/Servermanager-XML-Displaying-a-list-of-strings-along-with-selection-tp3134p3135.html
>>>> >
>>>> > Hope that helps,
>>>> > Cory
>>>> >
>>>> > On Mon, Jan 5, 2015 at 4:23 PM, Daniel Wilches Maradey
>>>> > <dwilches at gmail.com> wrote:
>>>> >> Hello,
>>>> >>
>>>> >> I'm creating a ProgrammableFilter to process a source that has several
>>>> >> arrays.
>>>> >> I would like to create a GUI for it in which I present a checkbox for each
>>>> >> data array, so I let the user decide upon which arrays the filter will be
>>>> >> run.
>>>> >> My problem is I'm not being able to find how to dynamically generate that
>>>> >> GUI.
>>>> >>
>>>> >> Is there any way of accomplishing it ?
>>>> >>
>>>> >> Thanks.
>>>> >>
>>>> >>
>>>> >> _______________________________________________
>>>> >> Paraview-developers mailing list
>>>> >> Paraview-developers at paraview.org
>>>> >> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>> >>
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Cory Quammen
>>>> > R&D Engineer
>>>> > Kitware, Inc.
>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From wascott at sandia.gov  Wed Jan  7 21:40:38 2015
From: wascott at sandia.gov (Scott, W Alan)
Date: Thu, 8 Jan 2015 02:40:38 +0000
Subject: [Paraview-developers] CMake Version
Message-ID: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>

What is the correct cmake version to be using to build ParaView?  I am currently using 2.8.10, trying to complile hdf5-1.8.13, and it is asking for at least 2.8.10.2.  May I upgrade to cmake 3.0?

Note that the documentation at http://www.paraview.org/Wiki/ParaView_Binaries is not recording cmake version, which I wrote up on the bug tracker.

Thanks,

Alan

--------------------------------------------------------
W. Alan Scott
ParaView Support Manager

SAIC
Sandia National Laboratories, MS 0822
Org 9326 - Building 880 A1-C
(505) 284-0932   FAX (505) 284-5619
---------------------------------------------------------



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150108/7a12cab4/attachment-0001.html>

From dwilches at gmail.com  Wed Jan  7 22:40:36 2015
From: dwilches at gmail.com (Daniel Wilches Maradey)
Date: Wed, 7 Jan 2015 20:40:36 -0700
Subject: [Paraview-developers] CMake Version
In-Reply-To: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
Message-ID: <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>

Hello,

I'm using CMake 3.1.0 and it compiles fine.



On Wed, Jan 7, 2015 at 7:40 PM, Scott, W Alan <wascott at sandia.gov> wrote:
> What is the correct cmake version to be using to build ParaView?  I am
> currently using 2.8.10, trying to complile hdf5-1.8.13, and it is asking for
> at least 2.8.10.2.  May I upgrade to cmake 3.0?
>
> Note that the documentation at
> http://www.paraview.org/Wiki/ParaView_Binaries is not recording cmake
> version, which I wrote up on the bug tracker.
>
> Thanks,
>
> Alan
>
> --------------------------------------------------------
> W. Alan Scott
> ParaView Support Manager
>
> SAIC
> Sandia National Laboratories, MS 0822
> Org 9326 - Building 880 A1-C
> (505) 284-0932   FAX (505) 284-5619
> ---------------------------------------------------------
>
>
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>

From sur.chiranjib at gmail.com  Thu Jan  8 01:55:47 2015
From: sur.chiranjib at gmail.com (Chiranjib Sur)
Date: Thu, 8 Jan 2015 12:25:47 +0530
Subject: [Paraview-developers] CMake Version
In-Reply-To: <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
Message-ID: <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>

Hello,
For building Paraview 4.2, I am using cmake-3.0.2. Although the
paraview build prerequisite says it should work with cmake 2.8.8. My
experience says that higher version is a better choice. Same applies
for Qt ( am using Qt5.2.1 although the recoomended version Qt4.8).
Here is the pre-requisite page :
http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisites

Happy computing,
Chiranjib

On Thu, Jan 8, 2015 at 9:10 AM, Daniel Wilches Maradey
<dwilches at gmail.com> wrote:
> Hello,
>
> I'm using CMake 3.1.0 and it compiles fine.
>
>
>
> On Wed, Jan 7, 2015 at 7:40 PM, Scott, W Alan <wascott at sandia.gov> wrote:
>> What is the correct cmake version to be using to build ParaView?  I am
>> currently using 2.8.10, trying to complile hdf5-1.8.13, and it is asking for
>> at least 2.8.10.2.  May I upgrade to cmake 3.0?
>>
>> Note that the documentation at
>> http://www.paraview.org/Wiki/ParaView_Binaries is not recording cmake
>> version, which I wrote up on the bug tracker.
>>
>> Thanks,
>>
>> Alan
>>
>> --------------------------------------------------------
>> W. Alan Scott
>> ParaView Support Manager
>>
>> SAIC
>> Sandia National Laboratories, MS 0822
>> Org 9326 - Building 880 A1-C
>> (505) 284-0932   FAX (505) 284-5619
>> ---------------------------------------------------------
>>
>>
>>
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers

From Anton.Piccardo-Selg at tessella.com  Thu Jan  8 07:23:00 2015
From: Anton.Piccardo-Selg at tessella.com (Anton.Piccardo-Selg at tessella.com)
Date: Thu, 8 Jan 2015 12:23:00 +0000
Subject: [Paraview-developers] Which signal to use when trying to
 register a change of the background color of a view?
In-Reply-To: <CADHSJjATFTzyQiRBknoOsfrBT4-Zx1RFvdueurtpPCba_BzxMQ@mail.gmail.com>
References: <CADHSJjATFTzyQiRBknoOsfrBT4-Zx1RFvdueurtpPCba_BzxMQ@mail.gmail.com>, 
 <OF0CDD200A.7E5452D7-ON80257DC4.002E4333-80257DC4.002E4336@tessella.co.uk>
Message-ID: <OF92ECA1C1.46EC878F-ON80257DC7.0044063B-80257DC7.0044063E@tessella.co.uk>

An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150108/716f8b9c/attachment.html>

From Anton.Piccardo-Selg at tessella.com  Thu Jan  8 07:47:49 2015
From: Anton.Piccardo-Selg at tessella.com (Anton.Piccardo-Selg at tessella.com)
Date: Thu, 8 Jan 2015 12:47:49 +0000
Subject: [Paraview-developers] Is there a list with property keywords
	available?
Message-ID: <OF3FB445A7.CA4CE82F-ON80257DC7.003B05C0-80257DC7.00464BDB@tessella.co.uk>

An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150108/4519bf30/attachment.html>

From felipe.bordeu at ec-nantes.fr  Thu Jan  8 07:52:41 2015
From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu)
Date: Thu, 08 Jan 2015 13:52:41 +0100
Subject: [Paraview-developers] plugin filter icon/menu
Message-ID: <54AE7D99.1040806@ec-nantes.fr>


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

I'm porting my plugin into version 4.3 and I'm unable to set the icons
for my filters.
I tried : (http://www.paraview.org/Wiki/ParaView/Plugin_HowTo(

...
  <Hints>
    <ShowInMenu category="PXDMF" />
    <PipelineIcon name=":/PXDMFIcons/AnnotateFieldData.png"  />
  </Hints>
</SourceProxy>

...
but does not work. Searching for the keyword "PipelineIcon" in the
Paraview sources gives no results.

also :  the  ShowInMenu shows the filter in a new submenu but the is no
new toolbar as in the 4.2.

in the 4.2 version this was my GUI xml

<ParaViewFilters>
  <Category name="PXDMF" menu_label="&amp;PXDMF" show_in_toolbar="1">
      <!-- adds a new category and then adds our filter to it -->
      <Filter name="AnnotateFieldData"
icon=":/PXDMFIcons/AnnotateFieldData.png" />
  </Category>
</ParaViewFilters>

any ideas.

Thanks to all. And thanks for this new version.
Felipe

- -- 
Felipe Bordeu Weldt
Ing?nieur de Recherche
- -------------------------------------
T?l. : 33 (0)2 40 37 16 57
Fax. : 33 (0)2 40 74 74 06
Felipe.Bordeu at ec-nantes.fr
Institut GeM - UMR CNRS 6183
?cole Centrale Nantes
1 Rue de La No?, 44321 Nantes, FRANCE
- -------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUrn2UAAoJEE/fMfNgU9/DSGkH/RAeBk09VIE0GkBczr4B9SA7
leoSKUGBslzDj2sc4yMC163g/vzxK2k8OII4wn+swIdd1eluNTYjpqq0pT0EVDeX
7eqoiGfLnsOaQ322n0msOevXc4ZMJKMp7p9xR8sYsG+qiXxcfNXk7mrGv1u+l0oC
Pmpzj3WXm3NOlIZ03SNRbjWH79Py+gjzEinM3cjrGQTM0T224dhReahKefSlKiz0
ozc1JEMFDC6Dkq+KpMRmGwfnnqgLVnct/oe1Bgke3/zT7SW3zHiXEApfZ9bRiO3p
i5njtFIyIrsBs5CIYuv86jTuWVA6p/5B88NBS+OVHLH+uLqrqUt7aQ44XwUIpNw=
=KTUP
-----END PGP SIGNATURE-----



From utkarsh.ayachit at kitware.com  Thu Jan  8 08:01:45 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 8 Jan 2015 08:01:45 -0500
Subject: [Paraview-developers] Gatekeeper Review Summary
Message-ID: <CADHSJjDOLbxp46mvMWc+M8XW+GO30sCq3LEQkAkpHDf9r4pvPg@mail.gmail.com>

Topics merged into master (v4.3.0-RC1-28-gca67a44):
(VTK)   15022_fix_extract_subset
(VTK)   adios-update
        cgns_plugin_fixes
        pv-interactor-auto-render-optional
(VTK)   python-calc-15125
        render_on_settings_change
        return-codes-for-help-and-version
        server_without_mpi
(VTK)   update-vtk-20150106


---------------------------------------------
Topics reverted from next:
  fix_stereotype_view_property

From sebastien.jourdain at kitware.com  Thu Jan  8 08:17:33 2015
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Thu, 8 Jan 2015 08:17:33 -0500
Subject: [Paraview-developers] Facing Problem with Server in ParaView
	4.1 Web Version
In-Reply-To: <CAGCCciT-qi9cxdjObqUmSWh0EOZYLv2sC8iFv42S_3KVAWdXcQ@mail.gmail.com>
References: <CAGCCciSrGpkY8VJaJEwcCZzr-6RpLMEFxKeA9fCtzOcYM9ewyg@mail.gmail.com>
 <D71D4FAE-0D71-44FA-B472-2AEED6174824@kitware.com>
 <CAGCCciT-qi9cxdjObqUmSWh0EOZYLv2sC8iFv42S_3KVAWdXcQ@mail.gmail.com>
Message-ID: <CBD37F10-FA6B-4768-B6D7-A892F22313E8@kitware.com>

What happens when you load a dataset?

Remember those are samples that are meant to help you building your own application. 

Moreover Windows as a server and IE as the client, is probably the worst case scenario as both are not tested. 

Seb



> On Jan 8, 2015, at 08:09, Debanshu Saha <debanshu at 2pirad.com> wrote:
> 
> Hey Seb,
> 
> We are facing some problem in Data Prober Module. Whenever we start the Data Prober module with Jetty Launcher then the graph h in the lest left side does not load (Attached: Figure1). But when we start it without Jetty Launcher, it works fine. (Attached: Figure2).
> 
> With Jetty Launcher we are using the 9000 Port and without Jetty Launcher we are using the 8080 Port. But in both the cases the same set of resources are used. When we debug the problem (of Figure1), using debugger tool in IE, we are getting an error. (Attached: Figure3)
> 
>  Can you please help us to solve the problem?
> 
> 
> Regards
> Debanshu
> 2PiRad
> Contact: +91-8981409005
> 
>> On Tue, Jan 6, 2015 at 6:55 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>> 
>> 
>>> On Jan 6, 2015, at 03:33, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>> 
>>> Hi Seb,
>>> 
>>> Thanks for your help and advice. Everything is running fine now. 
>>> 
>>> But there are some concerns that we need to address:-
>>> 
>>> 1)  Whenever a new session is opened, a Visualization Tool-Kit WebGL Console Window is opened. Like, if 10 clients hit the ParaView Web URL, the 10 such window is opened. Can we avoid displaying that window, and run the same in background process?
>> 
>> Yes that's expected. This is the only way to leverage the gpu. Otherwise you can build ParaView with OSMesa but I'm not sure you can do such a thing on windows. 
>> 
>>> 
>>> 2)  Is there a limit to how many clients can be allowed to connect to a particular ParaView server? If yes, then where is it specified and how can we make sure that unlimited number of user can connect to a particular ParaView Server?
>> 
>> Yes there is a property in the launcher configure. 
>> 
>>> 
>>> Regards
>>> Debanshu
>>> 2PiRad
>>> Contact: +91-8981409005
>>> 
>>>> On Mon, Jan 5, 2015 at 7:51 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>> You are forcing each session to run on port 8080, hence the problem.
>>>> 
>>>> The documentation state:
>>>> 
>>>> --port PORT
>>>> And on your config you have "--port 8080" 
>>>> 
>>>> Should I assume you've read the documentation?
>>>> 
>>>> Seb
>>>> 
>>>> 
>>>>> On Mon, Jan 5, 2015 at 8:51 AM, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>>> Hi Seb,
>>>>> 
>>>>> We have gone through the documentation but we are facing issues while jetty is trying to access ParaViewWeb components. Though standalone ParaViewWeb is running fine.
>>>>> 
>>>>> Our Setup is as follows:-
>>>>> OS: Windows 7 64 Bit
>>>>> ParaViewWeb Folder: C:/Paraview/ParaView-4.1.0-Windows-64bit/
>>>>> Jetty Running Port: 9000
>>>>> ParaViewWeb Running Port: 8080
>>>>> 
>>>>> Files Attached:-
>>>>> pw-config.properties:  The config file for Jetty Session Manager
>>>>> fe04f1fa-02f1-4435-9ac2-d2c4b4203485.txt: Log File generated while running Jetty Server
>>>>> Client_Side_Error.txt:  Error showing in browser while loading ParaView Web on Jetty Server
>>>>> WebSocket Error.PNG:  Error showing in console while loading ParaView Web on Jetty Server
>>>>> 
>>>>> Kindly help us to solve this issue. 
>>>>> 
>>>>> One more thing Seb, if you are comfortable can we have a meeting in Skype to identify this issue? It can be solved quickly then.
>>>>> 
>>>>> 
>>>>> Regards
>>>>> Debanshu
>>>>> 2PiRad
>>>>> Contact: +91-8981409005
>>>>> 
>>>>>> On Mon, Jan 5, 2015 at 6:34 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>>>> The online documentation should be able to help. And please fix the path accordingly to your platform. 
>>>>>> 
>>>>>> Sent from my iPad
>>>>>> 
>>>>>>> On Jan 5, 2015, at 02:14, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>>>>> 
>>>>>>> Hi Seb,
>>>>>>> 
>>>>>>> Thanks for the info. I am now using Jetty Launcher in my computer. I have downloaded the JettySessionManager-Server-1.0.jar file and the sample pw-config.properties file. While running this jar we are getting this error:-
>>>>>>> 
>>>>>>> ==== Starting ParaViewWeb multi-user front-end ====
>>>>>>> Configuration: C:\pw-config.properties
>>>>>>> WebContent: /.../paraview-build/www
>>>>>>> Port: 9000
>>>>>>> ===================================================
>>>>>>> Jan 05, 2015 12:33:48 PM com.kitware.paraviewweb.util.Config getProxyConnectionAdapter
>>>>>>> INFO: No class defined for ProxyConnectionAdapter
>>>>>>> 2015-01-05 12:33:48.591:WARN:oejsh.ResourceHandler:java.net.MalformedURLException: no protocol: /.../paraview-build/www
>>>>>>> Exception in thread "main" java.lang.IllegalArgumentException: /.../paraview-build/www
>>>>>>>         at org.eclipse.jetty.server.handler.ResourceHandler.setResourceBase(ResourceHandler.java:194)
>>>>>>>         at com.kitware.paraviewweb.handler.ParaViewWebHandler.<init>(ParaViewWebHandler.java:57)
>>>>>>>         at com.kitware.paraviewweb.handler.WebSocketForwarderHandler.main(WebSocketForwarderHandler.java:104)
>>>>>>> 
>>>>>>> Also, while studying the configuration file I am seeing that file locations are as follows. I cannot find the files there.:-
>>>>>>> pw.data_prober.cmd=./bin/pvpython ../src/Web/Python/data_prober.py --data-dir /Data --port PORT -f --authKey SECRET
>>>>>>> pw.loader.cmd=./bin/pvpython ../src/Web/Python/file_loader.py --data-dir /Data --port PORT -f --authKey SECRET
>>>>>>> pw.pipeline.cmd=./bin/pvpython ../src/Web/Python/pipeline_manager.py --data-dir /Data --port PORT -f --authKey SECRET
>>>>>>> 
>>>>>>> Instead I found the below mentioned files:-
>>>>>>> /lib/site-packages/paraview/web/pv_web_visualizer.py
>>>>>>> /lib/site-packages/paraview/web/pv_web_data_prober.py
>>>>>>> /lib/site-packages/paraview/web/pv_web_file_loader.py
>>>>>>> 
>>>>>>> Also, in the configuration file, I found the following values blank. What should be the values of this file and where can I get that?:-
>>>>>>> pw.factory.proxy.adapter=
>>>>>>> pw.factory.proxy.adapter.file=
>>>>>>> 
>>>>>>> Please suggest!
>>>>>>> 
>>>>>>> Regards
>>>>>>> Debanshu
>>>>>>> 2PiRad
>>>>>>> Contact: +91-8981409005
>>>>>>> 
>>>>>>>> On Fri, Jan 2, 2015 at 9:55 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>>>>>> ..\share\paraview-4.1\www\index.html
>>>>>>>> 
>>>>>>>> it might b right if your plan is to have a single instance of Paraview for all the usage you want to do. Otherwise, you can achieve the same thing using the launcher but this time each user will have its own instance.
>>>>>>>> 
>>>>>>>> Seb
>>>>>>>> 
>>>>>>>>> On Thu, Jan 1, 2015 at 11:35 PM, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>>>>>>> Great then. 
>>>>>>>>> 
>>>>>>>>> Where can I find this Unload part of the HTML code? I mean in while file and directory?
>>>>>>>>> 
>>>>>>>>> We just want to invoke the ParaView Web from another Web Application. For this, I am just starting the ParaView Server along with the Server of the Web Application and giving a link of ParaView URL from the Web Application. Are we going the right way? 
>>>>>>>>> 
>>>>>>>>> Regards
>>>>>>>>> Debanshu
>>>>>>>>> 2PiRad
>>>>>>>>> Contact: +91-8981409005
>>>>>>>>> 
>>>>>>>>>> On Fri, Jan 2, 2015 at 11:59 AM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>>> On Jan 1, 2015, at 23:24, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> Hi Seb,
>>>>>>>>>>> 
>>>>>>>>>>> Can you please clarify the following points:-
>>>>>>>>>>> 
>>>>>>>>>>> 1) Then anybody hitting refresh(knowingly/unknowingly) after opening the server will make the server stop again. Is it an expected behavior?
>>>>>>>>>> 
>>>>>>>>>> Yes but if you comment the unload= part of the html code, that behavior will disappear. 
>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> 2) Is ParaView Web not supported in Windows? If No, then how can we make sure that it works on Windows? 
>>>>>>>>>> 
>>>>>>>>>> The issue was related to Python and some native api not available by default. But if you managed to get the server running, the ParaView side will just work. 
>>>>>>>>>> 
>>>>>>>>>> Seb
>>>>>>>>>> 
>>>>>>>>>> Ps: try to keep the mailing list in the loop
>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>> Regards
>>>>>>>>>>> Debanshu
>>>>>>>>>>> 2PiRad
>>>>>>>>>>> Contact: +91-8981409005
>>>>>>>>>>> 
>>>>>>>>>>>> On Fri, Jan 2, 2015 at 11:06 AM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>> Hi Debanshu,
>>>>>>>>>>>> 
>>>>>>>>>>>> what you are seeing is exactly expected. For multiple user, we expect to start one server per client. Hence we use a launcher to automate that task and use apache to serve everything on the same port. 
>>>>>>>>>>>> 
>>>>>>>>>>>> What you just did was to validate that ParaViewWeb does work on your computer.
>>>>>>>>>>>> (Which is impressive considering that Windows is not officially supported.)
>>>>>>>>>>>> 
>>>>>>>>>>>> You can read more here: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/multi_user_setup
>>>>>>>>>>>> 
>>>>>>>>>>>> Seb
>>>>>>>>>>>> 
>>>>>>>>>>>>> On Thu, Jan 1, 2015 at 10:08 PM, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>>>>>>>>>>> Hello,
>>>>>>>>>>>>> 
>>>>>>>>>>>>> I have followed the below mentioned steps while installing ParaView Web:-
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 1) We have downloaded the ParaView-4.1.0-Windows-64bit.zip from ParaView website.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 2) We have downloaded the same data like can.ex2 and disk_out_ref.ex2 from ParaView website. 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 3) Then we executed the below code in a batch file:-
>>>>>>>>>>>>> $ unzip ParaView-4.1.0-Windows-64bit.exe
>>>>>>>>>>>>> $ cd ParaView-4.1.0-Windows-64bit\bin
>>>>>>>>>>>>> $ pvpython.exe ..\lib\paraview-4.1\site-packages\paraview\web\pv_web_visualizer.py --content ..\share\paraview-4.1\www --data-dir .\path-to-share --port 8080
>>>>>>>>>>>>> So, the ParaView server is started.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 4) Started the application by hitting the URL http://localhost:8080/apps/Visualizer/
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Now, we facing the below problems:-
>>>>>>>>>>>>> 
>>>>>>>>>>>>> 1) When we again hit the same URL in the same browser window, the server stops. It does not happen when we hit the same URL in different browser.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Kindly advice what is wrong with it.
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Regards
>>>>>>>>>>>>> Debanshu
>>>>>>>>>>>>> 2PiRad
>>>>>>>>>>>>> Contact: +91-8981409005
>>>>>>>>>>>>> 
>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>> Paraview-developers mailing list
>>>>>>>>>>>>> Paraview-developers at paraview.org
>>>>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview-developers
> 
> <Figure1.jpg>
> <Figure2.jpg>
> <Figure3.jpg>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150108/31e75432/attachment-0001.html>

From sebastien.jourdain at kitware.com  Thu Jan  8 08:20:54 2015
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Thu, 8 Jan 2015 08:20:54 -0500
Subject: [Paraview-developers] Facing Problem with Server in ParaView
	4.1 Web Version
In-Reply-To: <CAGCCciRayv=z1EYegNnvjCFGsMUpzcNmJE3OEna5M1=uXW+AFg@mail.gmail.com>
References: <CAGCCciQqrmzheq5pvJmobiVDWGkcYaR_PrHp5EmN53DH2OhOxQ@mail.gmail.com>
 <89085397-4E39-43DE-BFDD-8D0AB7CBC2FE@kitware.com>
 <CAGCCciRayv=z1EYegNnvjCFGsMUpzcNmJE3OEna5M1=uXW+AFg@mail.gmail.com>
Message-ID: <1979062B-7E45-41E1-8F6B-E32E24677234@kitware.com>

Yes, but in 4.2 we bumped the version of twisted and autobahn which induced some weird native dependency on Windows.  

Hence we don't build that part by default on windows anymore. 


> On Jan 8, 2015, at 08:14, Debanshu Saha <debanshu at 2pirad.com> wrote:
> 
> Ok. ?But in 4.1 using integrated it in Web without rebuilding it.
> 
> Regards
> Debanshu
> 2PiRad
> Contact: +91-8981409005
> 
>> On Thu, Jan 8, 2015 at 6:40 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>> On windows you will need to build PV yourself to have the web part. 
>> 
>> Seb
>> 
>> 
>> 
>>> On Jan 8, 2015, at 00:55, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>> 
>>> Hey Seb,
>>> 
>>> Which version of ParaView is in the sample showcase (http://paraviewweb.kitware.com/apps/Visualizer/)? And how can we integrate the ParaView 4.2 or 4.3 in Web as there is no files like pv_web_data_prober.py, pv_web_file_loader.py or pv_web_visualizer.py in the package, which we need to mention in pw-config.properties file. Please suggest.
>>> 
>>> Regards
>>> Debanshu
>>> 2PiRad
>>> Contact: +91-8981409005
>>> 
>>> ---------- Forwarded message ----------
>>> From: Sebastien Jourdain <sebastien.jourdain at kitware.com>
>>> Date: Tue, Jan 6, 2015 at 6:55 PM
>>> Subject: Re: [Paraview-developers] Facing Problem with Server in ParaView 4.1 Web Version
>>> To: Debanshu Saha <debanshu at 2pirad.com>
>>> 
>>> 
>>> 
>>> 
>>>> On Jan 6, 2015, at 03:33, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>> 
>>>> Hi Seb,
>>>> 
>>>> Thanks for your help and advice. Everything is running fine now. 
>>>> 
>>>> But there are some concerns that we need to address:-
>>>> 
>>>> 1)  Whenever a new session is opened, a Visualization Tool-Kit WebGL Console Window is opened. Like, if 10 clients hit the ParaView Web URL, the 10 such window is opened. Can we avoid displaying that window, and run the same in background process?
>>> 
>>> Yes that's expected. This is the only way to leverage the gpu. Otherwise you can build ParaView with OSMesa but I'm not sure you can do such a thing on windows. 
>>> 
>>>> 
>>>> 2)  Is there a limit to how many clients can be allowed to connect to a particular ParaView server? If yes, then where is it specified and how can we make sure that unlimited number of user can connect to a particular ParaView Server?
>>> 
>>> Yes there is a property in the launcher configure. 
>>> 
>>>> 
>>>> Regards
>>>> Debanshu
>>>> 2PiRad
>>>> Contact: +91-8981409005
>>>> 
>>>>> On Mon, Jan 5, 2015 at 7:51 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>>> You are forcing each session to run on port 8080, hence the problem.
>>>>> 
>>>>> The documentation state:
>>>>> 
>>>>> --port PORT
>>>>> And on your config you have "--port 8080" 
>>>>> 
>>>>> Should I assume you've read the documentation?
>>>>> 
>>>>> Seb
>>>>> 
>>>>> 
>>>>>> On Mon, Jan 5, 2015 at 8:51 AM, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>>>> Hi Seb,
>>>>>> 
>>>>>> We have gone through the documentation but we are facing issues while jetty is trying to access ParaViewWeb components. Though standalone ParaViewWeb is running fine.
>>>>>> 
>>>>>> Our Setup is as follows:-
>>>>>> OS: Windows 7 64 Bit
>>>>>> ParaViewWeb Folder: C:/Paraview/ParaView-4.1.0-Windows-64bit/
>>>>>> Jetty Running Port: 9000
>>>>>> ParaViewWeb Running Port: 8080
>>>>>> 
>>>>>> Files Attached:-
>>>>>> pw-config.properties:  The config file for Jetty Session Manager
>>>>>> fe04f1fa-02f1-4435-9ac2-d2c4b4203485.txt: Log File generated while running Jetty Server
>>>>>> Client_Side_Error.txt:  Error showing in browser while loading ParaView Web on Jetty Server
>>>>>> WebSocket Error.PNG:  Error showing in console while loading ParaView Web on Jetty Server
>>>>>> 
>>>>>> Kindly help us to solve this issue. 
>>>>>> 
>>>>>> One more thing Seb, if you are comfortable can we have a meeting in Skype to identify this issue? It can be solved quickly then.
>>>>>> 
>>>>>> 
>>>>>> Regards
>>>>>> Debanshu
>>>>>> 2PiRad
>>>>>> Contact: +91-8981409005
>>>>>> 
>>>>>>> On Mon, Jan 5, 2015 at 6:34 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>>>>> The online documentation should be able to help. And please fix the path accordingly to your platform. 
>>>>>>> 
>>>>>>> Sent from my iPad
>>>>>>> 
>>>>>>>> On Jan 5, 2015, at 02:14, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>>>>>> 
>>>>>>>> Hi Seb,
>>>>>>>> 
>>>>>>>> Thanks for the info. I am now using Jetty Launcher in my computer. I have downloaded the JettySessionManager-Server-1.0.jar file and the sample pw-config.properties file. While running this jar we are getting this error:-
>>>>>>>> 
>>>>>>>> ==== Starting ParaViewWeb multi-user front-end ====
>>>>>>>> Configuration: C:\pw-config.properties
>>>>>>>> WebContent: /.../paraview-build/www
>>>>>>>> Port: 9000
>>>>>>>> ===================================================
>>>>>>>> Jan 05, 2015 12:33:48 PM com.kitware.paraviewweb.util.Config getProxyConnectionAdapter
>>>>>>>> INFO: No class defined for ProxyConnectionAdapter
>>>>>>>> 2015-01-05 12:33:48.591:WARN:oejsh.ResourceHandler:java.net.MalformedURLException: no protocol: /.../paraview-build/www
>>>>>>>> Exception in thread "main" java.lang.IllegalArgumentException: /.../paraview-build/www
>>>>>>>>         at org.eclipse.jetty.server.handler.ResourceHandler.setResourceBase(ResourceHandler.java:194)
>>>>>>>>         at com.kitware.paraviewweb.handler.ParaViewWebHandler.<init>(ParaViewWebHandler.java:57)
>>>>>>>>         at com.kitware.paraviewweb.handler.WebSocketForwarderHandler.main(WebSocketForwarderHandler.java:104)
>>>>>>>> 
>>>>>>>> Also, while studying the configuration file I am seeing that file locations are as follows. I cannot find the files there.:-
>>>>>>>> pw.data_prober.cmd=./bin/pvpython ../src/Web/Python/data_prober.py --data-dir /Data --port PORT -f --authKey SECRET
>>>>>>>> pw.loader.cmd=./bin/pvpython ../src/Web/Python/file_loader.py --data-dir /Data --port PORT -f --authKey SECRET
>>>>>>>> pw.pipeline.cmd=./bin/pvpython ../src/Web/Python/pipeline_manager.py --data-dir /Data --port PORT -f --authKey SECRET
>>>>>>>> 
>>>>>>>> Instead I found the below mentioned files:-
>>>>>>>> /lib/site-packages/paraview/web/pv_web_visualizer.py
>>>>>>>> /lib/site-packages/paraview/web/pv_web_data_prober.py
>>>>>>>> /lib/site-packages/paraview/web/pv_web_file_loader.py
>>>>>>>> 
>>>>>>>> Also, in the configuration file, I found the following values blank. What should be the values of this file and where can I get that?:-
>>>>>>>> pw.factory.proxy.adapter=
>>>>>>>> pw.factory.proxy.adapter.file=
>>>>>>>> 
>>>>>>>> Please suggest!
>>>>>>>> 
>>>>>>>> Regards
>>>>>>>> Debanshu
>>>>>>>> 2PiRad
>>>>>>>> Contact: +91-8981409005
>>>>>>>> 
>>>>>>>>> On Fri, Jan 2, 2015 at 9:55 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>>>>>>> ..\share\paraview-4.1\www\index.html
>>>>>>>>> 
>>>>>>>>> it might b right if your plan is to have a single instance of Paraview for all the usage you want to do. Otherwise, you can achieve the same thing using the launcher but this time each user will have its own instance.
>>>>>>>>> 
>>>>>>>>> Seb
>>>>>>>>> 
>>>>>>>>>> On Thu, Jan 1, 2015 at 11:35 PM, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>>>>>>>> Great then. 
>>>>>>>>>> 
>>>>>>>>>> Where can I find this Unload part of the HTML code? I mean in while file and directory?
>>>>>>>>>> 
>>>>>>>>>> We just want to invoke the ParaView Web from another Web Application. For this, I am just starting the ParaView Server along with the Server of the Web Application and giving a link of ParaView URL from the Web Application. Are we going the right way? 
>>>>>>>>>> 
>>>>>>>>>> Regards
>>>>>>>>>> Debanshu
>>>>>>>>>> 2PiRad
>>>>>>>>>> Contact: +91-8981409005
>>>>>>>>>> 
>>>>>>>>>>> On Fri, Jan 2, 2015 at 11:59 AM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>>>> On Jan 1, 2015, at 23:24, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>> Hi Seb,
>>>>>>>>>>>> 
>>>>>>>>>>>> Can you please clarify the following points:-
>>>>>>>>>>>> 
>>>>>>>>>>>> 1) Then anybody hitting refresh(knowingly/unknowingly) after opening the server will make the server stop again. Is it an expected behavior?
>>>>>>>>>>> 
>>>>>>>>>>> Yes but if you comment the unload= part of the html code, that behavior will disappear. 
>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> 2) Is ParaView Web not supported in Windows? If No, then how can we make sure that it works on Windows? 
>>>>>>>>>>> 
>>>>>>>>>>> The issue was related to Python and some native api not available by default. But if you managed to get the server running, the ParaView side will just work. 
>>>>>>>>>>> 
>>>>>>>>>>> Seb
>>>>>>>>>>> 
>>>>>>>>>>> Ps: try to keep the mailing list in the loop
>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> Regards
>>>>>>>>>>>> Debanshu
>>>>>>>>>>>> 2PiRad
>>>>>>>>>>>> Contact: +91-8981409005
>>>>>>>>>>>> 
>>>>>>>>>>>>> On Fri, Jan 2, 2015 at 11:06 AM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>> Hi Debanshu,
>>>>>>>>>>>>> 
>>>>>>>>>>>>> what you are seeing is exactly expected. For multiple user, we expect to start one server per client. Hence we use a launcher to automate that task and use apache to serve everything on the same port. 
>>>>>>>>>>>>> 
>>>>>>>>>>>>> What you just did was to validate that ParaViewWeb does work on your computer.
>>>>>>>>>>>>> (Which is impressive considering that Windows is not officially supported.)
>>>>>>>>>>>>> 
>>>>>>>>>>>>> You can read more here: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/multi_user_setup
>>>>>>>>>>>>> 
>>>>>>>>>>>>> Seb
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Thu, Jan 1, 2015 at 10:08 PM, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>>>>>>>>>>>> Hello,
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> I have followed the below mentioned steps while installing ParaView Web:-
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 1) We have downloaded the ParaView-4.1.0-Windows-64bit.zip from ParaView website.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 2) We have downloaded the same data like can.ex2 and disk_out_ref.ex2 from ParaView website. 
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 3) Then we executed the below code in a batch file:-
>>>>>>>>>>>>>> $ unzip ParaView-4.1.0-Windows-64bit.exe
>>>>>>>>>>>>>> $ cd ParaView-4.1.0-Windows-64bit\bin
>>>>>>>>>>>>>> $ pvpython.exe ..\lib\paraview-4.1\site-packages\paraview\web\pv_web_visualizer.py --content ..\share\paraview-4.1\www --data-dir .\path-to-share --port 8080
>>>>>>>>>>>>>> So, the ParaView server is started.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 4) Started the application by hitting the URL http://localhost:8080/apps/Visualizer/
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Now, we facing the below problems:-
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> 1) When we again hit the same URL in the same browser window, the server stops. It does not happen when we hit the same URL in different browser.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Kindly advice what is wrong with it.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Regards
>>>>>>>>>>>>>> Debanshu
>>>>>>>>>>>>>> 2PiRad
>>>>>>>>>>>>>> Contact: +91-8981409005
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> 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/20150108/7b9761a5/attachment-0001.html>

From debanshu at 2pirad.com  Thu Jan  8 09:07:36 2015
From: debanshu at 2pirad.com (Debanshu Saha)
Date: Thu, 08 Jan 2015 19:37:36 +0530
Subject: [Paraview-developers] Facing Problem with Server in ParaView
 4.1 Web Version
Message-ID: <54ae8f37.42be440a.12a2.ffffd40a@mx.google.com>

When we are not using the Jetty Launcher the Data samples also work fine. But when we are starting it with Jetty launcher the graph is not coming, but the rendering image on the right side is coming correctly.

Regards
Debanshu
2PiRad
Contact: +91-8981409005

On Jan 8, 2015 6:47 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>
> What happens when you load a dataset?
>
> Remember those are samples that are meant to help you building your own application.?
>
> Moreover Windows as a server and IE as the client, is probably the worst case scenario as both are not tested.?
>
> Seb
>
>
>
> On Jan 8, 2015, at 08:09, Debanshu Saha <debanshu at 2pirad.com> wrote:
>
>> Hey Seb,
>>
>> We are facing some problem in Data Prober Module. Whenever we start the Data Prober module with Jetty Launcher then the graph h in the lest left side does not load (Attached: Figure1). But when we start it without Jetty Launcher, it works fine. (Attached: Figure2).
>>
>> With Jetty Launcher we are using the 9000 Port and without Jetty Launcher we are using the 8080 Port. But in both the cases the same set of resources are used. When we debug the problem (of Figure1), using debugger tool in IE, we are getting an error. (Attached: Figure3)
>>
>> ?Can you please help us to solve the problem?
>>
>>
>> Regards
>> Debanshu
>> 2PiRad
>> Contact: +91-8981409005
>>
>> On Tue, Jan 6, 2015 at 6:55 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>
>>>
>>>
>>> On Jan 6, 2015, at 03:33, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>
>>>> Hi Seb,
>>>>
>>>> Thanks for your help and advice. Everything is running fine now.?
>>>>
>>>> But there are some concerns that we need to address:-
>>>>
>>>> 1) ?Whenever a new session is opened, a Visualization Tool-Kit WebGL Console Window is opened. Like, if 10 clients hit the ParaView Web URL, the 10 such window is opened. Can we avoid displaying that window, and run the same in background process?
>>>
>>>
>>> Yes that's expected. This is the only way to leverage the gpu. Otherwise you can build ParaView with OSMesa but I'm not sure you can do such a thing on windows.?
>>>
>>>>
>>>> 2) ?Is there a limit to how many clients can be allowed to connect to a particular ParaView server? If yes, then where is it specified and how can we make sure that unlimited number of user can connect to a particular ParaView Server?
>>>
>>>
>>> Yes there is a property in the launcher configure.?
>>>
>>>>
>>>> Regards
>>>> Debanshu
>>>> 2PiRad
>>>> Contact: +91-8981409005
>>>>
>>>> On Mon, Jan 5, 2015 at 7:51 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>>>
>>>>> You are forcing each session to run on port 8080, hence the problem.
>>>>>
>>>>> The documentation state:
>>>>>
>>>>> --port PORT
>>>>>
>>>>> And on your config you have "--port 8080"?
>>>>>
>>>>> Should I assume you've read the documentation?
>>>>>
>>>>> Seb
>>>>>
>>>>>
>>>>> On Mon, Jan 5, 2015 at 8:51 AM, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>>>>
>>>>>> Hi Seb,
>>>>>>
>>>>>> We have gone through the documentation but we are facing issues while jetty is trying to access ParaViewWeb components. Though standalone ParaViewWeb is running fine.
>>>>>>
>>>>>> Our Setup is as follows:-
>>>>>> OS: Windows 7 64 Bit
>>>>>> ParaViewWeb Folder:?C:/Paraview/ParaView-4.1.0-Windows-64bit/
>>>>>> Jetty Running Port: 9000
>>>>>> ParaViewWeb Running Port: 8080
>>>>>>
>>>>>> Files Attached:-
>>>>>> pw-config.properties: ?The config file for Jetty Session Manager
>>>>>> fe04f1fa-02f1-4435-9ac2-d2c4b4203485.txt: Log File generated while running Jetty Server
>>>>>> Client_Side_Error.txt: ?Error showing in browser while loading ParaView Web on Jetty Server
>>>>>> WebSocket Error.PNG: ?Error?showing in console?while loading ParaView Web on Jetty Server
>>>>>>
>>>>>> Kindly help us to solve this issue.?
>>>>>>
>>>>>> One more thing Seb, if you are comfortable can we have a meeting in Skype to identify this issue? It can be solved quickly then.
>>>>>>
>>>>>>
>>>>>> Regards
>>>>>> Debanshu
>>>>>> 2PiRad
>>>>>> Contact: +91-8981409005
>>>>>>
>>>>>> On Mon, Jan 5, 2015 at 6:34 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>>>>>
>>>>>>> The online documentation should be able to help. And please fix the path accordingly to your platform.?
>>>>>>>
>>>>>>> Sent from my iPad
>>>>>>>
>>>>>>> On Jan 5, 2015, at 02:14, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>>>>>
>>>>>>>> Hi Seb,
>>>>>>>>
>>>>>>>> Thanks for the info. I am now using Jetty Launcher in my computer. I have downloaded the JettySessionManager-Server-1.0.jar file and the sample pw-config.properties file. While running this jar we are getting this error:-
>>>>>>>>
>>>>>>>> ==== Starting ParaViewWeb multi-user front-end ====
>>>>>>>> Configuration: C:\pw-config.properties
>>>>>>>> WebContent: /.../paraview-build/www
>>>>>>>> Port: 9000
>>>>>>>> ===================================================
>>>>>>>> Jan 05, 2015 12:33:48 PM com.kitware.paraviewweb.util.Config getProxyConnectionAdapter
>>>>>>>> INFO: No class defined for ProxyConnectionAdapter
>>>>>>>> 2015-01-05 12:33:48.591:WARN:oejsh.ResourceHandler:java.net.MalformedURLException: no protocol: /.../paraview-build/www
>>>>>>>> Exception in thread "main" java.lang.IllegalArgumentException: /.../paraview-build/www
>>>>>>>> ? ? ? ? at org.eclipse.jetty.server.handler.ResourceHandler.setResourceBase(ResourceHandler.java:194)
>>>>>>>> ? ? ? ? at com.kitware.paraviewweb.handler.ParaViewWebHandler.<init>(ParaViewWebHandler.java:57)
>>>>>>>> ? ? ? ? at com.kitware.paraviewweb.handler.WebSocketForwarderHandler.main(WebSocketForwarderHandler.java:104)
>>>>>>>>
>>>>>>>> Also, while studying the configuration file I am seeing that file locations are as follows.?I cannot find the files there.:-
>>>>>>>> pw.data_prober.cmd=./bin/pvpython ../src/Web/Python/data_prober.py --data-dir /Data --port PORT -f --authKey SECRET
>>>>>>>> pw.loader.cmd=./bin/pvpython ../src/Web/Python/file_loader.py --data-dir /Data --port PORT -f --authKey SECRET
>>>>>>>> pw.pipeline.cmd=./bin/pvpython ../src/Web/Python/pipeline_manager.py --data-dir /Data --port PORT -f --authKey SECRET
>>>>>>>>
>>>>>>>> Instead I found the below mentioned files:-
>>>>>>>> /lib/site-packages/paraview/web/pv_web_visualizer.py
>>>>>>>> /lib/site-packages/paraview/web/pv_web_data_prober.py
>>>>>>>> /lib/site-packages/paraview/web/pv_web_file_loader.py
>>>>>>>>
>>>>>>>> Also, in the configuration file, I found the following values blank. What should be the values of this file and where can I get that?:-
>>>>>>>> pw.factory.proxy.adapter=
>>>>>>>> pw.factory.proxy.adapter.file=
>>>>>>>>
>>>>>>>> Please suggest!
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> Debanshu
>>>>>>>> 2PiRad
>>>>>>>> Contact: +91-8981409005
>>>>>>>>
>>>>>>>> On Fri, Jan 2, 2015 at 9:55 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>
>>>>>>>>> ..\share\paraview-4.1\www\index.html
>>>>>>>>>
>>>>>>>>> it might b right if your plan is to have a single instance of Paraview for all the usage you want to do. Otherwise, you can achieve the same thing using the launcher but this time each user will have its own instance.
>>>>>>>>>
>>>>>>>>> Seb
>>>>>>>>>
>>>>>>>>> On Thu, Jan 1, 2015 at 11:35 PM, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>>>>>>>>
>>>>>>>>>> Great then.?
>>>>>>>>>>
>>>>>>>>>> Where can I find this Unload part of the HTML code? I mean in while file and directory?
>>>>>>>>>>
>>>>>>>>>> We just want to invoke the ParaView Web from another Web Application. For this, I am just starting the ParaView Server along with the Server of the Web Application and giving a link of ParaView URL from the Web Application. Are we going the right way??
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>> Debanshu
>>>>>>>>>> 2PiRad
>>>>>>>>>> Contact: +91-8981409005
>>>>>>>>>>
>>>>>>>>>> On Fri, Jan 2, 2015 at 11:59 AM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Jan 1, 2015, at 23:24, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi Seb,
>>>>>>>>>>>>
>>>>>>>>>>>> Can you please clarify the following points:-
>>>>>>>>>>>>
>>>>>>>>>>>> 1) Then anybody hitting refresh(knowingly/unknowingly) after opening the server will make the server stop again. Is it an expected behavior?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Yes but if you comment the unload= part of the html code, that behavior will disappear.?
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 2) Is ParaView Web not supported in Windows? If No, then how can we make sure that it works on Windows??
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> The issue was related to Python and some native api not available by default. But if you managed to get the server running, the ParaView side will just work.?
>>>>>>>>>>>
>>>>>>>>>>> Seb
>>>>>>>>>>>
>>>>>>>>>>> Ps: try to keep the mailing list in the loop
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Regards
>>>>>>>>>>>> Debanshu
>>>>>>>>>>>> 2PiRad
>>>>>>>>>>>> Contact: +91-8981409005
>>>>>>>>>>>>
>>>>>>>>>>>> On Fri, Jan 2, 2015 at 11:06 AM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi?Debanshu,
>>>>>>>>>>>>>
>>>>>>>>>>>>> what you are seeing is exactly expected. For multiple user, we expect to start one server per client. Hence we use a launcher to automate that?task and use apache to serve everything on the same port.?
>>>>>>>>>>>>>
>>>>>>>>>>>>> What you just did was to validate that ParaViewWeb does work on your computer.
>>>>>>>>>>>>> (Which is impressive considering that Windows is not officially supported.)
>>>>>>>>>>>>>
>>>>>>>>>>>>> You can read more here:?http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/multi_user_setup
>>>>>>>>>>>>>
>>>>>>>>>>>>> Seb
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Jan 1, 2015 at 10:08 PM, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hello,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have followed the below mentioned steps while installing ParaView Web:-
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 1)?We have downloaded the ParaView-4.1.0-Windows-64bit.zip from ParaView website.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2) We have downloaded the same data like can.ex2 and disk_out_ref.ex2 from ParaView website.?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 3) Then we executed the below code in a batch file:-
>>>>>>>>>>>>>> $ unzip ParaView-4.1.0-Windows-64bit.exe
>>>>>>>>>>>>>> $ cd ParaView-4.1.0-Windows-64bit\bin
>>>>>>>>>>>>>> $ pvpython.exe ..\lib\paraview-4.1\site-packages\paraview\web\pv_web_visualizer.py --content ..\share\paraview-4.1\www --data-dir .\path-to-share --port 8080
>>>>>>>>>>>>>> So, the ParaView server is started.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 4) Started the application by hitting the URL?http://localhost:8080/apps/Visualizer/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Now, we facing the below problems:-
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 1) When we again hit the same URL in the same browser window, the server stops. It does not happen when we hit the same URL in different browser.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Kindly advice what is wrong with it.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Regards
>>>>>>>>>>>>>> Debanshu
>>>>>>>>>>>>>> 2PiRad
>>>>>>>>>>>>>> Contact: +91-8981409005
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> Paraview-developers mailing list
>>>>>>>>>>>>>> Paraview-developers at paraview.org
>>>>>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>
>>>>
>>
>> <Figure1.jpg>
>>
>> <Figure2.jpg>
>>
>> <Figure3.jpg>

From utkarsh.ayachit at kitware.com  Thu Jan  8 09:31:26 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 8 Jan 2015 09:31:26 -0500
Subject: [Paraview-developers] plugin filter icon/menu
In-Reply-To: <54AE7D99.1040806@ec-nantes.fr>
References: <54AE7D99.1040806@ec-nantes.fr>
Message-ID: <CADHSJjBYUbw4eFCTaj=-Yu+TWVbdKif2RsQ++tVv8hLMB_150Q@mail.gmail.com>

Good catch. I don't exactly know what the PipelineIcon hint is.
Looking at the code I don't think it was intended to be functional.
I'll track down the developer and figure that part out. I am adding
support to add a new attribute "icon" to the <ShowInMenu > element.

e.g.
   <Hints>
      <ShowInMenu icon="...." />
  </Hints>

Utkarsh

On Thu, Jan 8, 2015 at 7:52 AM, Felipe Bordeu
<felipe.bordeu at ec-nantes.fr> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> I'm porting my plugin into version 4.3 and I'm unable to set the icons
> for my filters.
> I tried : (http://www.paraview.org/Wiki/ParaView/Plugin_HowTo(
>
> ...
>   <Hints>
>     <ShowInMenu category="PXDMF" />
>     <PipelineIcon name=":/PXDMFIcons/AnnotateFieldData.png"  />
>   </Hints>
> </SourceProxy>
>
> ...
> but does not work. Searching for the keyword "PipelineIcon" in the
> Paraview sources gives no results.
>
> also :  the  ShowInMenu shows the filter in a new submenu but the is no
> new toolbar as in the 4.2.
>
> in the 4.2 version this was my GUI xml
>
> <ParaViewFilters>
>   <Category name="PXDMF" menu_label="&amp;PXDMF" show_in_toolbar="1">
>       <!-- adds a new category and then adds our filter to it -->
>       <Filter name="AnnotateFieldData"
> icon=":/PXDMFIcons/AnnotateFieldData.png" />
>   </Category>
> </ParaViewFilters>
>
> any ideas.
>
> Thanks to all. And thanks for this new version.
> Felipe
>
> - --
> Felipe Bordeu Weldt
> Ing?nieur de Recherche
> - -------------------------------------
> T?l. : 33 (0)2 40 37 16 57
> Fax. : 33 (0)2 40 74 74 06
> Felipe.Bordeu at ec-nantes.fr
> Institut GeM - UMR CNRS 6183
> ?cole Centrale Nantes
> 1 Rue de La No?, 44321 Nantes, FRANCE
> - -------------------------------------
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBAgAGBQJUrn2UAAoJEE/fMfNgU9/DSGkH/RAeBk09VIE0GkBczr4B9SA7
> leoSKUGBslzDj2sc4yMC163g/vzxK2k8OII4wn+swIdd1eluNTYjpqq0pT0EVDeX
> 7eqoiGfLnsOaQ322n0msOevXc4ZMJKMp7p9xR8sYsG+qiXxcfNXk7mrGv1u+l0oC
> Pmpzj3WXm3NOlIZ03SNRbjWH79Py+gjzEinM3cjrGQTM0T224dhReahKefSlKiz0
> ozc1JEMFDC6Dkq+KpMRmGwfnnqgLVnct/oe1Bgke3/zT7SW3zHiXEApfZ9bRiO3p
> i5njtFIyIrsBs5CIYuv86jTuWVA6p/5B88NBS+OVHLH+uLqrqUt7aQ44XwUIpNw=
> =KTUP
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers

From utkarsh.ayachit at kitware.com  Thu Jan  8 09:48:56 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 8 Jan 2015 09:48:56 -0500
Subject: [Paraview-developers] plugin filter icon/menu
In-Reply-To: <CADHSJjBYUbw4eFCTaj=-Yu+TWVbdKif2RsQ++tVv8hLMB_150Q@mail.gmail.com>
References: <54AE7D99.1040806@ec-nantes.fr>
 <CADHSJjBYUbw4eFCTaj=-Yu+TWVbdKif2RsQ++tVv8hLMB_150Q@mail.gmail.com>
Message-ID: <CADHSJjAYXhVAvJ5cmVEun7sL4MCOQVgLCyNj_zNesCtgo+fDyw@mail.gmail.com>

Here's the change:
   http://review.source.kitware.com/#/c/18740/

Should make it into the official release of 4.3.

Utkarsh

On Thu, Jan 8, 2015 at 9:31 AM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> Good catch. I don't exactly know what the PipelineIcon hint is.
> Looking at the code I don't think it was intended to be functional.
> I'll track down the developer and figure that part out. I am adding
> support to add a new attribute "icon" to the <ShowInMenu > element.
>
> e.g.
>    <Hints>
>       <ShowInMenu icon="...." />
>   </Hints>
>
> Utkarsh
>
> On Thu, Jan 8, 2015 at 7:52 AM, Felipe Bordeu
> <felipe.bordeu at ec-nantes.fr> wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hello,
>>
>> I'm porting my plugin into version 4.3 and I'm unable to set the icons
>> for my filters.
>> I tried : (http://www.paraview.org/Wiki/ParaView/Plugin_HowTo(
>>
>> ...
>>   <Hints>
>>     <ShowInMenu category="PXDMF" />
>>     <PipelineIcon name=":/PXDMFIcons/AnnotateFieldData.png"  />
>>   </Hints>
>> </SourceProxy>
>>
>> ...
>> but does not work. Searching for the keyword "PipelineIcon" in the
>> Paraview sources gives no results.
>>
>> also :  the  ShowInMenu shows the filter in a new submenu but the is no
>> new toolbar as in the 4.2.
>>
>> in the 4.2 version this was my GUI xml
>>
>> <ParaViewFilters>
>>   <Category name="PXDMF" menu_label="&amp;PXDMF" show_in_toolbar="1">
>>       <!-- adds a new category and then adds our filter to it -->
>>       <Filter name="AnnotateFieldData"
>> icon=":/PXDMFIcons/AnnotateFieldData.png" />
>>   </Category>
>> </ParaViewFilters>
>>
>> any ideas.
>>
>> Thanks to all. And thanks for this new version.
>> Felipe
>>
>> - --
>> Felipe Bordeu Weldt
>> Ing?nieur de Recherche
>> - -------------------------------------
>> T?l. : 33 (0)2 40 37 16 57
>> Fax. : 33 (0)2 40 74 74 06
>> Felipe.Bordeu at ec-nantes.fr
>> Institut GeM - UMR CNRS 6183
>> ?cole Centrale Nantes
>> 1 Rue de La No?, 44321 Nantes, FRANCE
>> - -------------------------------------
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1
>>
>> iQEcBAEBAgAGBQJUrn2UAAoJEE/fMfNgU9/DSGkH/RAeBk09VIE0GkBczr4B9SA7
>> leoSKUGBslzDj2sc4yMC163g/vzxK2k8OII4wn+swIdd1eluNTYjpqq0pT0EVDeX
>> 7eqoiGfLnsOaQ322n0msOevXc4ZMJKMp7p9xR8sYsG+qiXxcfNXk7mrGv1u+l0oC
>> Pmpzj3WXm3NOlIZ03SNRbjWH79Py+gjzEinM3cjrGQTM0T224dhReahKefSlKiz0
>> ozc1JEMFDC6Dkq+KpMRmGwfnnqgLVnct/oe1Bgke3/zT7SW3zHiXEApfZ9bRiO3p
>> i5njtFIyIrsBs5CIYuv86jTuWVA6p/5B88NBS+OVHLH+uLqrqUt7aQ44XwUIpNw=
>> =KTUP
>> -----END PGP SIGNATURE-----
>>
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers

From ben.boeckel at kitware.com  Thu Jan  8 10:03:23 2015
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Thu, 8 Jan 2015 10:03:23 -0500
Subject: [Paraview-developers] CMake Version
In-Reply-To: <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
Message-ID: <20150108150323.GA26903@megas.kitwarein.com>

On Thu, Jan 08, 2015 at 12:25:47 +0530, Chiranjib Sur wrote:
> For building Paraview 4.2, I am using cmake-3.0.2. Although the
> paraview build prerequisite says it should work with cmake 2.8.8.

Looking at VTK, the HDF5 we upgraded to now has 2.8.10 and 2.8.11
minimum requirements in it. This should probably be looked at to keep
VTK down to 2.8.8.

--Ben

From dan.lipsa at kitware.com  Thu Jan  8 11:04:58 2015
From: dan.lipsa at kitware.com (Dan Lipsa)
Date: Thu, 8 Jan 2015 11:04:58 -0500
Subject: [Paraview-developers] CMake Version
In-Reply-To: <20150108150323.GA26903@megas.kitwarein.com>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
 <20150108150323.GA26903@megas.kitwarein.com>
Message-ID: <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>

On Thu, Jan 8, 2015 at 10:03 AM, Ben Boeckel <ben.boeckel at kitware.com>
wrote:

> On Thu, Jan 08, 2015 at 12:25:47 +0530, Chiranjib Sur wrote:
> > For building Paraview 4.2, I am using cmake-3.0.2. Although the
> > paraview build prerequisite says it should work with cmake 2.8.8.
>
> Looking at VTK, the HDF5 we upgraded to now has 2.8.10 and 2.8.11
> minimum requirements in it. This should probably be looked at to keep
> VTK down to 2.8.8.
>

I'll look at this.
Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150108/93d2014c/attachment.html>

From dwilches at gmail.com  Thu Jan  8 13:05:56 2015
From: dwilches at gmail.com (Daniel Wilches Maradey)
Date: Thu, 8 Jan 2015 11:05:56 -0700
Subject: [Paraview-developers] Callback not being called when deselecting an
	item in the GUI of a plugin
Message-ID: <CAEbtaO2_ojmb1iPodSymGSTftuoRBns3YAaOgoLiSs3H4tj5DA@mail.gmail.com>

Hello,

I'm creating a plugin that shows a list of the avaiable inputs, and
allows the user to select which inputs should be processed. The
following is the part of my XML that generates the list of inputs,
each with a checkbox that allows me to select several of them:

<StringVectorProperty command="SetAttributeEnabled"
                            label="Enabled attributes"
                            name="CellArrayStatus"
                            number_of_elements="1"
                            repeat_command="1">
<ArrayListDomain name="array_list">
   <RequiredProperties>
   <Property name="Input" function="Input" />
   </RequiredProperties>
</ArrayListDomain>
</StringVectorProperty>

The problem I'm facing is that the callback "SetAttributeEnabled" is
only being called when I select an item, but not when I deselect it,
so I cannot know the actual state of the checkboxes in this way.

Do you know how to force the callback to be called when deselecting an
item? or how can I retrieve an array of all selected items from my C++
plugin?

If needed, this is my C++ callback:

public:
void SetAttributeEnabled(char* name);


Thanks.

From dan.lipsa at kitware.com  Thu Jan  8 13:13:27 2015
From: dan.lipsa at kitware.com (Dan Lipsa)
Date: Thu, 8 Jan 2015 13:13:27 -0500
Subject: [Paraview-developers] CMake Version
In-Reply-To: <CANjZAi-+bT4DiLs6DcT_5=3okWzuC2c547mRnMC6TxgdDstqZQ@mail.gmail.com>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
 <20150108150323.GA26903@megas.kitwarein.com>
 <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>
 <CANjZAi-+bT4DiLs6DcT_5=3okWzuC2c547mRnMC6TxgdDstqZQ@mail.gmail.com>
Message-ID: <CADwGrVokKwcrmo4moRvz-Lu6v0_ybqBBHHuoH9Kkoc1Tqoub_Q@mail.gmail.com>

>>>
>>> Looking at VTK, the HDF5 we upgraded to now has 2.8.10 and 2.8.11
>>> minimum requirements in it. This should probably be looked at to keep
>>> VTK down to 2.8.8.
>>>
>>
Looking at the code, hdf5 files that require higher version of cmake have
conflict markers in them, so they are obviously not used.
I will fix the conflict markers.

> What is the correct cmake version to be using to build ParaView?  I am
currently using 2.8.10, trying to complile hdf5-1.8.13, and it is asking
for at least 2.8.10.2.  May I upgrade to cmake 3.0?

Indeed, upgrading cmake is usually beneficial (unless is a version not
released). I use 3.1

Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150108/47df8b44/attachment.html>

From dave.demarle at kitware.com  Thu Jan  8 12:06:57 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Thu, 8 Jan 2015 12:06:57 -0500
Subject: [Paraview-developers] CMake Version
In-Reply-To: <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
 <20150108150323.GA26903@megas.kitwarein.com>
 <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>
Message-ID: <CANjZAi-+bT4DiLs6DcT_5=3okWzuC2c547mRnMC6TxgdDstqZQ@mail.gmail.com>

Is there any reason why we don't bump up the minimum cmake for VTK to keep
HDF5 happy rather than the other way around?

FYI:

Minimum cmake on the vtk dashboard right now is (from
./VTK/Utilities/Maintenance/vtk_submitter_summary.py /vtk_submitter_summary.py
| grep CMAKE_VERSION)

CMAKE_VERSION;2.8.8;;['karego-at.kitware', 'dash3.kitware',
'tarvalon.kitware']

Those do not have XDMF and thus HDF5 turned on, which is why we haven't
noticed this before now. ParaView by default turns HDF5 on, so it would be
more obvious there if.






David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, Jan 8, 2015 at 11:04 AM, Dan Lipsa <dan.lipsa at kitware.com> wrote:

>
> On Thu, Jan 8, 2015 at 10:03 AM, Ben Boeckel <ben.boeckel at kitware.com>
> wrote:
>
>> On Thu, Jan 08, 2015 at 12:25:47 +0530, Chiranjib Sur wrote:
>> > For building Paraview 4.2, I am using cmake-3.0.2. Although the
>> > paraview build prerequisite says it should work with cmake 2.8.8.
>>
>> Looking at VTK, the HDF5 we upgraded to now has 2.8.10 and 2.8.11
>> minimum requirements in it. This should probably be looked at to keep
>> VTK down to 2.8.8.
>>
>
> I'll look at this.
> Dan
>
>
> _______________________________________________
> 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/20150108/0a6cc2a9/attachment.html>

From cory.quammen at kitware.com  Thu Jan  8 13:47:24 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 8 Jan 2015 13:47:24 -0500
Subject: [Paraview-developers] Callback not being called when
 deselecting an item in the GUI of a plugin
In-Reply-To: <CAEbtaO2_ojmb1iPodSymGSTftuoRBns3YAaOgoLiSs3H4tj5DA@mail.gmail.com>
References: <CAEbtaO2_ojmb1iPodSymGSTftuoRBns3YAaOgoLiSs3H4tj5DA@mail.gmail.com>
Message-ID: <CAB5Fpx69yeoMJVWDwa8JkTo0C8cVog-kSO9hU8P6ccTLUWkOTQ@mail.gmail.com>

Daniel,

The signature for SetAttributeEnabled() should be

void SetAttributeEnabled(const char * name, int status)

The status argument tells whether the attribute is enabled or not.

Also, your XML should be

<StringVectorProperty command="SetAttributeEnabled"
                            element_types="2 0"
                            label="Enabled attributes"
                            name="CellArrayStatus"
                            number_of_elements="0"
                            number_of_elements_per_command="2"
                            repeat_command="1">
<ArrayListDomain name="array_list">
   <RequiredProperties>
   <Property name="Input" function="Input" />
   </RequiredProperties>
</ArrayListDomain>
</StringVectorProperty>

The element_types indicate the type of argument (2 for char string, 0 for int).

Please see ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml
lines 241 - 262 for more hints that might help you.

Hope that helps,
Cory

On Thu, Jan 8, 2015 at 1:05 PM, Daniel Wilches Maradey
<dwilches at gmail.com> wrote:
> Hello,
>
> I'm creating a plugin that shows a list of the avaiable inputs, and
> allows the user to select which inputs should be processed. The
> following is the part of my XML that generates the list of inputs,
> each with a checkbox that allows me to select several of them:
>
> <StringVectorProperty command="SetAttributeEnabled"
>                             label="Enabled attributes"
>                             name="CellArrayStatus"
>                             number_of_elements="1"
>                             repeat_command="1">
> <ArrayListDomain name="array_list">
>    <RequiredProperties>
>    <Property name="Input" function="Input" />
>    </RequiredProperties>
> </ArrayListDomain>
> </StringVectorProperty>
>
> The problem I'm facing is that the callback "SetAttributeEnabled" is
> only being called when I select an item, but not when I deselect it,
> so I cannot know the actual state of the checkboxes in this way.
>
> Do you know how to force the callback to be called when deselecting an
> item? or how can I retrieve an array of all selected items from my C++
> plugin?
>
> If needed, this is my C++ callback:
>
> public:
> void SetAttributeEnabled(char* name);
>
>
> Thanks.
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From dwilches at gmail.com  Thu Jan  8 14:05:58 2015
From: dwilches at gmail.com (Daniel Wilches Maradey)
Date: Thu, 8 Jan 2015 12:05:58 -0700
Subject: [Paraview-developers] Callback not being called when
 deselecting an item in the GUI of a plugin
In-Reply-To: <CAB5Fpx69yeoMJVWDwa8JkTo0C8cVog-kSO9hU8P6ccTLUWkOTQ@mail.gmail.com>
References: <CAEbtaO2_ojmb1iPodSymGSTftuoRBns3YAaOgoLiSs3H4tj5DA@mail.gmail.com>
 <CAB5Fpx69yeoMJVWDwa8JkTo0C8cVog-kSO9hU8P6ccTLUWkOTQ@mail.gmail.com>
Message-ID: <CAEbtaO2J==8dHZONgKvX_bcfzi1ive_td56rNjg_+RWoE3Qtng@mail.gmail.com>

Hello Cory,

At the beginning I was trying with the same XML and function prototype
you told me, with no good results, so I gave up on that way.
But well, as you suggest it I have tried again copying&pasting your
XML and function prototype and putting this implementation:

void vtkVSUIFilter::SetAttributeEnabled(const char * name, int status)
{
   char s[255];
   sprintf(s, "SetAttributeEnabled/2 was invoked %s %d\n", name, status);
   QMessageBox::information(NULL, "MyAction", s);
}

With these changes the problems I'm getting with it are:

* The callback is not being called when only one of my elements is
selected, I have to select two. And when I do so, the callback is
called just for the first element and the status == 0
* I see that for each 2 elements I select a single callback is
invoked, it seems it is ignoring each other selected element.
* Again, deselecting an element is not working, it doesn't generate a callback

My guess is that my function is not being passed the "status" but
instead the second selected element, converting it somehow from char*
to int (it always is 0 after that conversion). But this is just a wild
guess after seeing the consistent behaviour of ignoring the
even-numbered selected elements.

Maybe I'm missing something else?

--
Daniel Wilches



On Thu, Jan 8, 2015 at 11:47 AM, Cory Quammen <cory.quammen at kitware.com> wrote:
> Daniel,
>
> The signature for SetAttributeEnabled() should be
>
> void SetAttributeEnabled(const char * name, int status)
>
> The status argument tells whether the attribute is enabled or not.
>
> Also, your XML should be
>
> <StringVectorProperty command="SetAttributeEnabled"
>                             element_types="2 0"
>                             label="Enabled attributes"
>                             name="CellArrayStatus"
>                             number_of_elements="0"
>                             number_of_elements_per_command="2"
>                             repeat_command="1">
> <ArrayListDomain name="array_list">
>    <RequiredProperties>
>    <Property name="Input" function="Input" />
>    </RequiredProperties>
> </ArrayListDomain>
> </StringVectorProperty>
>
> The element_types indicate the type of argument (2 for char string, 0 for int).
>
> Please see ParaView/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml
> lines 241 - 262 for more hints that might help you.
>
> Hope that helps,
> Cory
>
> On Thu, Jan 8, 2015 at 1:05 PM, Daniel Wilches Maradey
> <dwilches at gmail.com> wrote:
>> Hello,
>>
>> I'm creating a plugin that shows a list of the avaiable inputs, and
>> allows the user to select which inputs should be processed. The
>> following is the part of my XML that generates the list of inputs,
>> each with a checkbox that allows me to select several of them:
>>
>> <StringVectorProperty command="SetAttributeEnabled"
>>                             label="Enabled attributes"
>>                             name="CellArrayStatus"
>>                             number_of_elements="1"
>>                             repeat_command="1">
>> <ArrayListDomain name="array_list">
>>    <RequiredProperties>
>>    <Property name="Input" function="Input" />
>>    </RequiredProperties>
>> </ArrayListDomain>
>> </StringVectorProperty>
>>
>> The problem I'm facing is that the callback "SetAttributeEnabled" is
>> only being called when I select an item, but not when I deselect it,
>> so I cannot know the actual state of the checkboxes in this way.
>>
>> Do you know how to force the callback to be called when deselecting an
>> item? or how can I retrieve an array of all selected items from my C++
>> plugin?
>>
>> If needed, this is my C++ callback:
>>
>> public:
>> void SetAttributeEnabled(char* name);
>>
>>
>> Thanks.
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.

From debanshu at 2pirad.com  Fri Jan  9 00:12:35 2015
From: debanshu at 2pirad.com (Debanshu Saha)
Date: Fri, 9 Jan 2015 10:42:35 +0530
Subject: [Paraview-developers] Facing Problem with Server in ParaView
 4.1 Web Version
In-Reply-To: <54ae8f37.42be440a.12a2.ffffd40a@mx.google.com>
References: <54ae8f37.42be440a.12a2.ffffd40a@mx.google.com>
Message-ID: <CAGCCciRZcpLR8ZrH7Aw9DqM_zHKd6Spx4VtUraE9-g2QLLco4A@mail.gmail.com>

Hi Seb,

Please reply on the below problem. We are stuck in this.

In Data Prober, when we are not using the Jetty Launcher the data samples
(provided with ParaView) also work fine. But when we are starting it with
Jetty launcher nothing is coming in the left side, but the rendering image
on the right side is coming correctly. We are using 4.1 version.

*Regards*
Debanshu
*2PiRad*
*Contact: *+91-8981409005

On Thu, Jan 8, 2015 at 7:37 PM, Debanshu Saha <debanshu at 2pirad.com> wrote:

> When we are not using the Jetty Launcher the Data samples also work fine.
> But when we are starting it with Jetty launcher the graph is not coming,
> but the rendering image on the right side is coming correctly.
>
> Regards
> Debanshu
> 2PiRad
> Contact: +91-8981409005
>
> On Jan 8, 2015 6:47 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com>
> wrote:
> >
> > What happens when you load a dataset?
> >
> > Remember those are samples that are meant to help you building your own
> application.
> >
> > Moreover Windows as a server and IE as the client, is probably the worst
> case scenario as both are not tested.
> >
> > Seb
> >
> >
> >
> > On Jan 8, 2015, at 08:09, Debanshu Saha <debanshu at 2pirad.com> wrote:
> >
> >> Hey Seb,
> >>
> >> We are facing some problem in Data Prober Module. Whenever we start the
> Data Prober module with Jetty Launcher then the graph h in the lest left
> side does not load (Attached: Figure1). But when we start it without Jetty
> Launcher, it works fine. (Attached: Figure2).
> >>
> >> With Jetty Launcher we are using the 9000 Port and without Jetty
> Launcher we are using the 8080 Port. But in both the cases the same set of
> resources are used. When we debug the problem (of Figure1), using debugger
> tool in IE, we are getting an error. (Attached: Figure3)
> >>
> >>  Can you please help us to solve the problem?
> >>
> >>
> >> Regards
> >> Debanshu
> >> 2PiRad
> >> Contact: +91-8981409005
> >>
> >> On Tue, Jan 6, 2015 at 6:55 PM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
> >>>
> >>>
> >>>
> >>> On Jan 6, 2015, at 03:33, Debanshu Saha <debanshu at 2pirad.com> wrote:
> >>>
> >>>> Hi Seb,
> >>>>
> >>>> Thanks for your help and advice. Everything is running fine now.
> >>>>
> >>>> But there are some concerns that we need to address:-
> >>>>
> >>>> 1)  Whenever a new session is opened, a Visualization Tool-Kit WebGL
> Console Window is opened. Like, if 10 clients hit the ParaView Web URL, the
> 10 such window is opened. Can we avoid displaying that window, and run the
> same in background process?
> >>>
> >>>
> >>> Yes that's expected. This is the only way to leverage the gpu.
> Otherwise you can build ParaView with OSMesa but I'm not sure you can do
> such a thing on windows.
> >>>
> >>>>
> >>>> 2)  Is there a limit to how many clients can be allowed to connect to
> a particular ParaView server? If yes, then where is it specified and how
> can we make sure that unlimited number of user can connect to a particular
> ParaView Server?
> >>>
> >>>
> >>> Yes there is a property in the launcher configure.
> >>>
> >>>>
> >>>> Regards
> >>>> Debanshu
> >>>> 2PiRad
> >>>> Contact: +91-8981409005
> >>>>
> >>>> On Mon, Jan 5, 2015 at 7:51 PM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
> >>>>>
> >>>>> You are forcing each session to run on port 8080, hence the problem.
> >>>>>
> >>>>> The documentation state:
> >>>>>
> >>>>> --port PORT
> >>>>>
> >>>>> And on your config you have "--port 8080"
> >>>>>
> >>>>> Should I assume you've read the documentation?
> >>>>>
> >>>>> Seb
> >>>>>
> >>>>>
> >>>>> On Mon, Jan 5, 2015 at 8:51 AM, Debanshu Saha <debanshu at 2pirad.com>
> wrote:
> >>>>>>
> >>>>>> Hi Seb,
> >>>>>>
> >>>>>> We have gone through the documentation but we are facing issues
> while jetty is trying to access ParaViewWeb components. Though standalone
> ParaViewWeb is running fine.
> >>>>>>
> >>>>>> Our Setup is as follows:-
> >>>>>> OS: Windows 7 64 Bit
> >>>>>> ParaViewWeb Folder: C:/Paraview/ParaView-4.1.0-Windows-64bit/
> >>>>>> Jetty Running Port: 9000
> >>>>>> ParaViewWeb Running Port: 8080
> >>>>>>
> >>>>>> Files Attached:-
> >>>>>> pw-config.properties:  The config file for Jetty Session Manager
> >>>>>> fe04f1fa-02f1-4435-9ac2-d2c4b4203485.txt: Log File generated while
> running Jetty Server
> >>>>>> Client_Side_Error.txt:  Error showing in browser while loading
> ParaView Web on Jetty Server
> >>>>>> WebSocket Error.PNG:  Error showing in console while loading
> ParaView Web on Jetty Server
> >>>>>>
> >>>>>> Kindly help us to solve this issue.
> >>>>>>
> >>>>>> One more thing Seb, if you are comfortable can we have a meeting in
> Skype to identify this issue? It can be solved quickly then.
> >>>>>>
> >>>>>>
> >>>>>> Regards
> >>>>>> Debanshu
> >>>>>> 2PiRad
> >>>>>> Contact: +91-8981409005
> >>>>>>
> >>>>>> On Mon, Jan 5, 2015 at 6:34 PM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
> >>>>>>>
> >>>>>>> The online documentation should be able to help. And please fix
> the path accordingly to your platform.
> >>>>>>>
> >>>>>>> Sent from my iPad
> >>>>>>>
> >>>>>>> On Jan 5, 2015, at 02:14, Debanshu Saha <debanshu at 2pirad.com>
> wrote:
> >>>>>>>
> >>>>>>>> Hi Seb,
> >>>>>>>>
> >>>>>>>> Thanks for the info. I am now using Jetty Launcher in my
> computer. I have downloaded the JettySessionManager-Server-1.0.jar file and
> the sample pw-config.properties file. While running this jar we are getting
> this error:-
> >>>>>>>>
> >>>>>>>> ==== Starting ParaViewWeb multi-user front-end ====
> >>>>>>>> Configuration: C:\pw-config.properties
> >>>>>>>> WebContent: /.../paraview-build/www
> >>>>>>>> Port: 9000
> >>>>>>>> ===================================================
> >>>>>>>> Jan 05, 2015 12:33:48 PM com.kitware.paraviewweb.util.Config
> getProxyConnectionAdapter
> >>>>>>>> INFO: No class defined for ProxyConnectionAdapter
> >>>>>>>> 2015-01-05
> 12:33:48.591:WARN:oejsh.ResourceHandler:java.net.MalformedURLException: no
> protocol: /.../paraview-build/www
> >>>>>>>> Exception in thread "main" java.lang.IllegalArgumentException:
> /.../paraview-build/www
> >>>>>>>>         at
> org.eclipse.jetty.server.handler.ResourceHandler.setResourceBase(ResourceHandler.java:194)
> >>>>>>>>         at
> com.kitware.paraviewweb.handler.ParaViewWebHandler.<init>(ParaViewWebHandler.java:57)
> >>>>>>>>         at
> com.kitware.paraviewweb.handler.WebSocketForwarderHandler.main(WebSocketForwarderHandler.java:104)
> >>>>>>>>
> >>>>>>>> Also, while studying the configuration file I am seeing that file
> locations are as follows. I cannot find the files there.:-
> >>>>>>>> pw.data_prober.cmd=./bin/pvpython
> ../src/Web/Python/data_prober.py --data-dir /Data --port PORT -f --authKey
> SECRET
> >>>>>>>> pw.loader.cmd=./bin/pvpython ../src/Web/Python/file_loader.py
> --data-dir /Data --port PORT -f --authKey SECRET
> >>>>>>>> pw.pipeline.cmd=./bin/pvpython
> ../src/Web/Python/pipeline_manager.py --data-dir /Data --port PORT -f
> --authKey SECRET
> >>>>>>>>
> >>>>>>>> Instead I found the below mentioned files:-
> >>>>>>>> /lib/site-packages/paraview/web/pv_web_visualizer.py
> >>>>>>>> /lib/site-packages/paraview/web/pv_web_data_prober.py
> >>>>>>>> /lib/site-packages/paraview/web/pv_web_file_loader.py
> >>>>>>>>
> >>>>>>>> Also, in the configuration file, I found the following values
> blank. What should be the values of this file and where can I get that?:-
> >>>>>>>> pw.factory.proxy.adapter=
> >>>>>>>> pw.factory.proxy.adapter.file=
> >>>>>>>>
> >>>>>>>> Please suggest!
> >>>>>>>>
> >>>>>>>> Regards
> >>>>>>>> Debanshu
> >>>>>>>> 2PiRad
> >>>>>>>> Contact: +91-8981409005
> >>>>>>>>
> >>>>>>>> On Fri, Jan 2, 2015 at 9:55 PM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
> >>>>>>>>>
> >>>>>>>>> ..\share\paraview-4.1\www\index.html
> >>>>>>>>>
> >>>>>>>>> it might b right if your plan is to have a single instance of
> Paraview for all the usage you want to do. Otherwise, you can achieve the
> same thing using the launcher but this time each user will have its own
> instance.
> >>>>>>>>>
> >>>>>>>>> Seb
> >>>>>>>>>
> >>>>>>>>> On Thu, Jan 1, 2015 at 11:35 PM, Debanshu Saha <
> debanshu at 2pirad.com> wrote:
> >>>>>>>>>>
> >>>>>>>>>> Great then.
> >>>>>>>>>>
> >>>>>>>>>> Where can I find this Unload part of the HTML code? I mean in
> while file and directory?
> >>>>>>>>>>
> >>>>>>>>>> We just want to invoke the ParaView Web from another Web
> Application. For this, I am just starting the ParaView Server along with
> the Server of the Web Application and giving a link of ParaView URL from
> the Web Application. Are we going the right way?
> >>>>>>>>>>
> >>>>>>>>>> Regards
> >>>>>>>>>> Debanshu
> >>>>>>>>>> 2PiRad
> >>>>>>>>>> Contact: +91-8981409005
> >>>>>>>>>>
> >>>>>>>>>> On Fri, Jan 2, 2015 at 11:59 AM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Jan 1, 2015, at 23:24, Debanshu Saha <debanshu at 2pirad.com>
> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> Hi Seb,
> >>>>>>>>>>>>
> >>>>>>>>>>>> Can you please clarify the following points:-
> >>>>>>>>>>>>
> >>>>>>>>>>>> 1) Then anybody hitting refresh(knowingly/unknowingly) after
> opening the server will make the server stop again. Is it an expected
> behavior?
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Yes but if you comment the unload= part of the html code, that
> behavior will disappear.
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> 2) Is ParaView Web not supported in Windows? If No, then how
> can we make sure that it works on Windows?
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> The issue was related to Python and some native api not
> available by default. But if you managed to get the server running, the
> ParaView side will just work.
> >>>>>>>>>>>
> >>>>>>>>>>> Seb
> >>>>>>>>>>>
> >>>>>>>>>>> Ps: try to keep the mailing list in the loop
> >>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Regards
> >>>>>>>>>>>> Debanshu
> >>>>>>>>>>>> 2PiRad
> >>>>>>>>>>>> Contact: +91-8981409005
> >>>>>>>>>>>>
> >>>>>>>>>>>> On Fri, Jan 2, 2015 at 11:06 AM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Hi Debanshu,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> what you are seeing is exactly expected. For multiple user,
> we expect to start one server per client. Hence we use a launcher to
> automate that task and use apache to serve everything on the same port.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> What you just did was to validate that ParaViewWeb does work
> on your computer.
> >>>>>>>>>>>>> (Which is impressive considering that Windows is not
> officially supported.)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> You can read more here:
> http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/multi_user_setup
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Seb
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Thu, Jan 1, 2015 at 10:08 PM, Debanshu Saha <
> debanshu at 2pirad.com> wrote:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Hello,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I have followed the below mentioned steps while installing
> ParaView Web:-
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> 1) We have downloaded the ParaView-4.1.0-Windows-64bit.zip
> from ParaView website.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> 2) We have downloaded the same data like can.ex2 and
> disk_out_ref.ex2 from ParaView website.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> 3) Then we executed the below code in a batch file:-
> >>>>>>>>>>>>>> $ unzip ParaView-4.1.0-Windows-64bit.exe
> >>>>>>>>>>>>>> $ cd ParaView-4.1.0-Windows-64bit\bin
> >>>>>>>>>>>>>> $ pvpython.exe
> ..\lib\paraview-4.1\site-packages\paraview\web\pv_web_visualizer.py
> --content ..\share\paraview-4.1\www --data-dir .\path-to-share --port 8080
> >>>>>>>>>>>>>> So, the ParaView server is started.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> 4) Started the application by hitting the URL
> http://localhost:8080/apps/Visualizer/
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Now, we facing the below problems:-
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> 1) When we again hit the same URL in the same browser
> window, the server stops. It does not happen when we hit the same URL in
> different browser.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Kindly advice what is wrong with it.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Regards
> >>>>>>>>>>>>>> Debanshu
> >>>>>>>>>>>>>> 2PiRad
> >>>>>>>>>>>>>> Contact: +91-8981409005
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> _______________________________________________
> >>>>>>>>>>>>>> Paraview-developers mailing list
> >>>>>>>>>>>>>> Paraview-developers at paraview.org
> >>>>>>>>>>>>>>
> http://public.kitware.com/mailman/listinfo/paraview-developers
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>
> >> <Figure1.jpg>
> >>
> >> <Figure2.jpg>
> >>
> >> <Figure3.jpg>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150109/b7c741ad/attachment-0001.html>

From felipe.bordeu at ec-nantes.fr  Fri Jan  9 05:08:13 2015
From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu)
Date: Fri, 09 Jan 2015 11:08:13 +0100
Subject: [Paraview-developers] plugin filter icon/menu
In-Reply-To: <CADHSJjAYXhVAvJ5cmVEun7sL4MCOQVgLCyNj_zNesCtgo+fDyw@mail.gmail.com>
References: <54AE7D99.1040806@ec-nantes.fr>	<CADHSJjBYUbw4eFCTaj=-Yu+TWVbdKif2RsQ++tVv8hLMB_150Q@mail.gmail.com>
 <CADHSJjAYXhVAvJ5cmVEun7sL4MCOQVgLCyNj_zNesCtgo+fDyw@mail.gmail.com>
Message-ID: <54AFA88D.5060408@ec-nantes.fr>


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

thanks I add the line (this->Internal->addProxy(group, name,
showInMenu->GetAttribute("icon"));) in my paraview sources and the icons
are visible again. thanks.

But what about the toolbar?. the "show_in_toolbar" option is also lost.

adding these lines(after the line 806 in your patch) make the
show_in_toolbar work again.

          int show_in_toolbar = 0;
          hint->GetScalarAttribute("show_in_toolbar", &show_in_toolbar);
          category.ShowInToolbar = category.ShowInToolbar ||
(show_in_toolbar == 1);

in this case we have to put a new tag in the xml hints.

       <ShowInMenu category="PXDMF"
icon=":/PXDMFIcons/AnnotateFieldData.png" show_in_toolbar="1" />


I don't know if this happens only in my 4.3-RC1 but the View->Toolbars
menu show  2 "VCR Controls" submenus. Can anyone confirm this.

thanks
Felipe




Le 08/01/2015 15:48, Utkarsh Ayachit a ??crit :
> Here's the change:
>? ? ?  http://review.source.kitware.com/#/c/18740/
>
> Should make it into the official release of 4.3.
>
> Utkarsh
>
> On Thu, Jan 8, 2015 at 9:31 AM, Utkarsh Ayachit
> <utkarsh.ayachit at kitware.com> wrote:
>> Good catch. I don't exactly know what the PipelineIcon hint is.
>> Looking at the code I don't think it was intended to be functional.
>> I'll track down the developer and figure that part out. I am adding
>> support to add a new attribute "icon" to the <ShowInMenu > element.
>>
>> e.g.
>>? ? ?  <Hints>
>>? ? ? ? ? ?  <ShowInMenu icon="...." />
>>? ?  </Hints>
>>
>> Utkarsh
>>
>> On Thu, Jan 8, 2015 at 7:52 AM, Felipe Bordeu
>> <felipe.bordeu at ec-nantes.fr> wrote:
>>>
> Hello,
>
> I'm porting my plugin into version 4.3 and I'm unable to set the icons
> for my filters.
> I tried : (http://www.paraview.org/Wiki/ParaView/Plugin_HowTo(
>
> ...
> ?  <Hints>
> ? ? ?  <ShowInMenu category="PXDMF" />
> ? ? ?  <PipelineIcon name=":/PXDMFIcons/AnnotateFieldData.png"?  />
> ?  </Hints>
> </SourceProxy>
>
> ...
> but does not work. Searching for the keyword "PipelineIcon" in the
> Paraview sources gives no results.
>
> also :?  the?  ShowInMenu shows the filter in a new submenu but the is no
> new toolbar as in the 4.2.
>
> in the 4.2 version this was my GUI xml
>
> <ParaViewFilters>
> ?  <Category name="PXDMF" menu_label="&amp;PXDMF" show_in_toolbar="1">
> ? ? ? ? ?  <!-- adds a new category and then adds our filter to it -->
> ? ? ? ? ?  <Filter name="AnnotateFieldData"
> icon=":/PXDMFIcons/AnnotateFieldData.png" />
> ?  </Category>
> </ParaViewFilters>
>
> any ideas.
>
> Thanks to all. And thanks for this new version.
> Felipe
>
>>>
>>>
>>> _______________________________________________
>>> Paraview-developers mailing list
>>> Paraview-developers at paraview.org
>>> http://public.kitware.com/mailman/listinfo/paraview-developers

- -- 
Felipe Bordeu Weldt
Ing??nieur de Recherche
- -------------------------------------
T??l. : 33 (0)2 40 37 16 57
Fax. : 33 (0)2 40 74 74 06
Felipe.Bordeu at ec-nantes.fr
Institut GeM - UMR CNRS 6183
??cole Centrale Nantes
1 Rue de La No??, 44321 Nantes, FRANCE
- -------------------------------------

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUr6iHAAoJEE/fMfNgU9/D/VUIAJKWqm+fIhqGckxda4bqrxZI
2ztfvVU8h9PbJN1LFpf8pSHTMETI4Lf6LN8YDuUH6F5YI/jEZHl7wF1N1ygaDHI4
6hllc1/lyJPd3n3LROoPNd9/A2eUv9oNZzW1u7LjHbKdq/M1yi1XKYUzFKJdgAlb
4W060OBKlalGcgasHxWa7+U5breML/3D11Why+HP/oTAA4p9HdRIyUxjpBjmYxRk
luS4bnEi9RlD1vDFzldYQm2fzNHJ4jllq35QbYcTzkOHSTNtRzwAqXGHc1J0z0V7
Wi9bUu1uKKfYC0pxHYrjYh1/PlJ5+cVoFW9+cPIOUwB0/Ex95Tr2TzyiO62ZLPI=
=ta6C
-----END PGP SIGNATURE-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150109/3f1641d5/attachment.html>

From sebastien.jourdain at kitware.com  Fri Jan  9 07:50:46 2015
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Fri, 9 Jan 2015 07:50:46 -0500
Subject: [Paraview-developers] Facing Problem with Server in ParaView
	4.1 Web Version
In-Reply-To: <CAGCCciRZcpLR8ZrH7Aw9DqM_zHKd6Spx4VtUraE9-g2QLLco4A@mail.gmail.com>
References: <54ae8f37.42be440a.12a2.ffffd40a@mx.google.com>
 <CAGCCciRZcpLR8ZrH7Aw9DqM_zHKd6Spx4VtUraE9-g2QLLco4A@mail.gmail.com>
Message-ID: <101A460E-D394-46DC-9A3D-7E11FD463CB3@kitware.com>


Hi Debanshu,

I have no idea. I'll have to investigate more to know better. But if you have deadlines or are in a hurry, you can always start a support contract with us. That will allow me to have dedicated time for you on this. 

Seb


> On Jan 9, 2015, at 00:12, Debanshu Saha <debanshu at 2pirad.com> wrote:
> 
> Hi Seb, 
> 
> Please reply on the below problem. We are stuck in this.
> 
> In Data Prober, when we are not using the Jetty Launcher the data samples (provided with ParaView) also work fine. But when we are starting it with Jetty launcher nothing is coming in the left side, but the rendering image on the right side is coming correctly. We are using 4.1 version. 
> 
> Regards
> Debanshu
> 2PiRad
> Contact: +91-8981409005
> 
>> On Thu, Jan 8, 2015 at 7:37 PM, Debanshu Saha <debanshu at 2pirad.com> wrote:
>> When we are not using the Jetty Launcher the Data samples also work fine. But when we are starting it with Jetty launcher the graph is not coming, but the rendering image on the right side is coming correctly.
>> 
>> Regards
>> Debanshu
>> 2PiRad
>> Contact: +91-8981409005
>> 
>> On Jan 8, 2015 6:47 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>> >
>> > What happens when you load a dataset?
>> >
>> > Remember those are samples that are meant to help you building your own application. 
>> >
>> > Moreover Windows as a server and IE as the client, is probably the worst case scenario as both are not tested. 
>> >
>> > Seb
>> >
>> >
>> >
>> > On Jan 8, 2015, at 08:09, Debanshu Saha <debanshu at 2pirad.com> wrote:
>> >
>> >> Hey Seb,
>> >>
>> >> We are facing some problem in Data Prober Module. Whenever we start the Data Prober module with Jetty Launcher then the graph h in the lest left side does not load (Attached: Figure1). But when we start it without Jetty Launcher, it works fine. (Attached: Figure2).
>> >>
>> >> With Jetty Launcher we are using the 9000 Port and without Jetty Launcher we are using the 8080 Port. But in both the cases the same set of resources are used. When we debug the problem (of Figure1), using debugger tool in IE, we are getting an error. (Attached: Figure3)
>> >>
>> >>  Can you please help us to solve the problem?
>> >>
>> >>
>> >> Regards
>> >> Debanshu
>> >> 2PiRad
>> >> Contact: +91-8981409005
>> >>
>> >> On Tue, Jan 6, 2015 at 6:55 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>> >>>
>> >>>
>> >>>
>> >>> On Jan 6, 2015, at 03:33, Debanshu Saha <debanshu at 2pirad.com> wrote:
>> >>>
>> >>>> Hi Seb,
>> >>>>
>> >>>> Thanks for your help and advice. Everything is running fine now. 
>> >>>>
>> >>>> But there are some concerns that we need to address:-
>> >>>>
>> >>>> 1)  Whenever a new session is opened, a Visualization Tool-Kit WebGL Console Window is opened. Like, if 10 clients hit the ParaView Web URL, the 10 such window is opened. Can we avoid displaying that window, and run the same in background process?
>> >>>
>> >>>
>> >>> Yes that's expected. This is the only way to leverage the gpu. Otherwise you can build ParaView with OSMesa but I'm not sure you can do such a thing on windows. 
>> >>>
>> >>>>
>> >>>> 2)  Is there a limit to how many clients can be allowed to connect to a particular ParaView server? If yes, then where is it specified and how can we make sure that unlimited number of user can connect to a particular ParaView Server?
>> >>>
>> >>>
>> >>> Yes there is a property in the launcher configure. 
>> >>>
>> >>>>
>> >>>> Regards
>> >>>> Debanshu
>> >>>> 2PiRad
>> >>>> Contact: +91-8981409005
>> >>>>
>> >>>> On Mon, Jan 5, 2015 at 7:51 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>> >>>>>
>> >>>>> You are forcing each session to run on port 8080, hence the problem.
>> >>>>>
>> >>>>> The documentation state:
>> >>>>>
>> >>>>> --port PORT
>> >>>>>
>> >>>>> And on your config you have "--port 8080" 
>> >>>>>
>> >>>>> Should I assume you've read the documentation?
>> >>>>>
>> >>>>> Seb
>> >>>>>
>> >>>>>
>> >>>>> On Mon, Jan 5, 2015 at 8:51 AM, Debanshu Saha <debanshu at 2pirad.com> wrote:
>> >>>>>>
>> >>>>>> Hi Seb,
>> >>>>>>
>> >>>>>> We have gone through the documentation but we are facing issues while jetty is trying to access ParaViewWeb components. Though standalone ParaViewWeb is running fine.
>> >>>>>>
>> >>>>>> Our Setup is as follows:-
>> >>>>>> OS: Windows 7 64 Bit
>> >>>>>> ParaViewWeb Folder: C:/Paraview/ParaView-4.1.0-Windows-64bit/
>> >>>>>> Jetty Running Port: 9000
>> >>>>>> ParaViewWeb Running Port: 8080
>> >>>>>>
>> >>>>>> Files Attached:-
>> >>>>>> pw-config.properties:  The config file for Jetty Session Manager
>> >>>>>> fe04f1fa-02f1-4435-9ac2-d2c4b4203485.txt: Log File generated while running Jetty Server
>> >>>>>> Client_Side_Error.txt:  Error showing in browser while loading ParaView Web on Jetty Server
>> >>>>>> WebSocket Error.PNG:  Error showing in console while loading ParaView Web on Jetty Server
>> >>>>>>
>> >>>>>> Kindly help us to solve this issue. 
>> >>>>>>
>> >>>>>> One more thing Seb, if you are comfortable can we have a meeting in Skype to identify this issue? It can be solved quickly then.
>> >>>>>>
>> >>>>>>
>> >>>>>> Regards
>> >>>>>> Debanshu
>> >>>>>> 2PiRad
>> >>>>>> Contact: +91-8981409005
>> >>>>>>
>> >>>>>> On Mon, Jan 5, 2015 at 6:34 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>> >>>>>>>
>> >>>>>>> The online documentation should be able to help. And please fix the path accordingly to your platform. 
>> >>>>>>>
>> >>>>>>> Sent from my iPad
>> >>>>>>>
>> >>>>>>> On Jan 5, 2015, at 02:14, Debanshu Saha <debanshu at 2pirad.com> wrote:
>> >>>>>>>
>> >>>>>>>> Hi Seb,
>> >>>>>>>>
>> >>>>>>>> Thanks for the info. I am now using Jetty Launcher in my computer. I have downloaded the JettySessionManager-Server-1.0.jar file and the sample pw-config.properties file. While running this jar we are getting this error:-
>> >>>>>>>>
>> >>>>>>>> ==== Starting ParaViewWeb multi-user front-end ====
>> >>>>>>>> Configuration: C:\pw-config.properties
>> >>>>>>>> WebContent: /.../paraview-build/www
>> >>>>>>>> Port: 9000
>> >>>>>>>> ===================================================
>> >>>>>>>> Jan 05, 2015 12:33:48 PM com.kitware.paraviewweb.util.Config getProxyConnectionAdapter
>> >>>>>>>> INFO: No class defined for ProxyConnectionAdapter
>> >>>>>>>> 2015-01-05 12:33:48.591:WARN:oejsh.ResourceHandler:java.net.MalformedURLException: no protocol: /.../paraview-build/www
>> >>>>>>>> Exception in thread "main" java.lang.IllegalArgumentException: /.../paraview-build/www
>> >>>>>>>>         at org.eclipse.jetty.server.handler.ResourceHandler.setResourceBase(ResourceHandler.java:194)
>> >>>>>>>>         at com.kitware.paraviewweb.handler.ParaViewWebHandler.<init>(ParaViewWebHandler.java:57)
>> >>>>>>>>         at com.kitware.paraviewweb.handler.WebSocketForwarderHandler.main(WebSocketForwarderHandler.java:104)
>> >>>>>>>>
>> >>>>>>>> Also, while studying the configuration file I am seeing that file locations are as follows. I cannot find the files there.:-
>> >>>>>>>> pw.data_prober.cmd=./bin/pvpython ../src/Web/Python/data_prober.py --data-dir /Data --port PORT -f --authKey SECRET
>> >>>>>>>> pw.loader.cmd=./bin/pvpython ../src/Web/Python/file_loader.py --data-dir /Data --port PORT -f --authKey SECRET
>> >>>>>>>> pw.pipeline.cmd=./bin/pvpython ../src/Web/Python/pipeline_manager.py --data-dir /Data --port PORT -f --authKey SECRET
>> >>>>>>>>
>> >>>>>>>> Instead I found the below mentioned files:-
>> >>>>>>>> /lib/site-packages/paraview/web/pv_web_visualizer.py
>> >>>>>>>> /lib/site-packages/paraview/web/pv_web_data_prober.py
>> >>>>>>>> /lib/site-packages/paraview/web/pv_web_file_loader.py
>> >>>>>>>>
>> >>>>>>>> Also, in the configuration file, I found the following values blank. What should be the values of this file and where can I get that?:-
>> >>>>>>>> pw.factory.proxy.adapter=
>> >>>>>>>> pw.factory.proxy.adapter.file=
>> >>>>>>>>
>> >>>>>>>> Please suggest!
>> >>>>>>>>
>> >>>>>>>> Regards
>> >>>>>>>> Debanshu
>> >>>>>>>> 2PiRad
>> >>>>>>>> Contact: +91-8981409005
>> >>>>>>>>
>> >>>>>>>> On Fri, Jan 2, 2015 at 9:55 PM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>> >>>>>>>>>
>> >>>>>>>>> ..\share\paraview-4.1\www\index.html
>> >>>>>>>>>
>> >>>>>>>>> it might b right if your plan is to have a single instance of Paraview for all the usage you want to do. Otherwise, you can achieve the same thing using the launcher but this time each user will have its own instance.
>> >>>>>>>>>
>> >>>>>>>>> Seb
>> >>>>>>>>>
>> >>>>>>>>> On Thu, Jan 1, 2015 at 11:35 PM, Debanshu Saha <debanshu at 2pirad.com> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>> Great then. 
>> >>>>>>>>>>
>> >>>>>>>>>> Where can I find this Unload part of the HTML code? I mean in while file and directory?
>> >>>>>>>>>>
>> >>>>>>>>>> We just want to invoke the ParaView Web from another Web Application. For this, I am just starting the ParaView Server along with the Server of the Web Application and giving a link of ParaView URL from the Web Application. Are we going the right way? 
>> >>>>>>>>>>
>> >>>>>>>>>> Regards
>> >>>>>>>>>> Debanshu
>> >>>>>>>>>> 2PiRad
>> >>>>>>>>>> Contact: +91-8981409005
>> >>>>>>>>>>
>> >>>>>>>>>> On Fri, Jan 2, 2015 at 11:59 AM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> On Jan 1, 2015, at 23:24, Debanshu Saha <debanshu at 2pirad.com> wrote:
>> >>>>>>>>>>>
>> >>>>>>>>>>>> Hi Seb,
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Can you please clarify the following points:-
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> 1) Then anybody hitting refresh(knowingly/unknowingly) after opening the server will make the server stop again. Is it an expected behavior?
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> Yes but if you comment the unload= part of the html code, that behavior will disappear. 
>> >>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> 2) Is ParaView Web not supported in Windows? If No, then how can we make sure that it works on Windows? 
>> >>>>>>>>>>>
>> >>>>>>>>>>>
>> >>>>>>>>>>> The issue was related to Python and some native api not available by default. But if you managed to get the server running, the ParaView side will just work. 
>> >>>>>>>>>>>
>> >>>>>>>>>>> Seb
>> >>>>>>>>>>>
>> >>>>>>>>>>> Ps: try to keep the mailing list in the loop
>> >>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> Regards
>> >>>>>>>>>>>> Debanshu
>> >>>>>>>>>>>> 2PiRad
>> >>>>>>>>>>>> Contact: +91-8981409005
>> >>>>>>>>>>>>
>> >>>>>>>>>>>> On Fri, Jan 2, 2015 at 11:06 AM, Sebastien Jourdain <sebastien.jourdain at kitware.com> wrote:
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Hi Debanshu,
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> what you are seeing is exactly expected. For multiple user, we expect to start one server per client. Hence we use a launcher to automate that task and use apache to serve everything on the same port. 
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> What you just did was to validate that ParaViewWeb does work on your computer.
>> >>>>>>>>>>>>> (Which is impressive considering that Windows is not officially supported.)
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> You can read more here: http://www.paraview.org/ParaView3/Doc/Nightly/www/js-doc/index.html#!/guide/multi_user_setup
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> Seb
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>> On Thu, Jan 1, 2015 at 10:08 PM, Debanshu Saha <debanshu at 2pirad.com> wrote:
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Hello,
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> I have followed the below mentioned steps while installing ParaView Web:-
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> 1) We have downloaded the ParaView-4.1.0-Windows-64bit.zip from ParaView website.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> 2) We have downloaded the same data like can.ex2 and disk_out_ref.ex2 from ParaView website. 
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> 3) Then we executed the below code in a batch file:-
>> >>>>>>>>>>>>>> $ unzip ParaView-4.1.0-Windows-64bit.exe
>> >>>>>>>>>>>>>> $ cd ParaView-4.1.0-Windows-64bit\bin
>> >>>>>>>>>>>>>> $ pvpython.exe ..\lib\paraview-4.1\site-packages\paraview\web\pv_web_visualizer.py --content ..\share\paraview-4.1\www --data-dir .\path-to-share --port 8080
>> >>>>>>>>>>>>>> So, the ParaView server is started.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> 4) Started the application by hitting the URL http://localhost:8080/apps/Visualizer/
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Now, we facing the below problems:-
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> 1) When we again hit the same URL in the same browser window, the server stops. It does not happen when we hit the same URL in different browser.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Kindly advice what is wrong with it.
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> Regards
>> >>>>>>>>>>>>>> Debanshu
>> >>>>>>>>>>>>>> 2PiRad
>> >>>>>>>>>>>>>> Contact: +91-8981409005
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>> _______________________________________________
>> >>>>>>>>>>>>>> Paraview-developers mailing list
>> >>>>>>>>>>>>>> Paraview-developers at paraview.org
>> >>>>>>>>>>>>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>> >>>>>>>>>>>>>>
>> >>>>>>>>>>>>>
>> >>>>>>>>>>>>
>> >>>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>
>> >> <Figure1.jpg>
>> >>
>> >> <Figure2.jpg>
>> >>
>> >> <Figure3.jpg>
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150109/3ce025f2/attachment-0001.html>

From marcus.hanwell at kitware.com  Fri Jan  9 10:40:23 2015
From: marcus.hanwell at kitware.com (Marcus D. Hanwell)
Date: Fri, 9 Jan 2015 10:40:23 -0500
Subject: [Paraview-developers] CMake Version
In-Reply-To: <CADwGrVokKwcrmo4moRvz-Lu6v0_ybqBBHHuoH9Kkoc1Tqoub_Q@mail.gmail.com>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
 <20150108150323.GA26903@megas.kitwarein.com>
 <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>
 <CANjZAi-+bT4DiLs6DcT_5=3okWzuC2c547mRnMC6TxgdDstqZQ@mail.gmail.com>
 <CADwGrVokKwcrmo4moRvz-Lu6v0_ybqBBHHuoH9Kkoc1Tqoub_Q@mail.gmail.com>
Message-ID: <CAMkPkZWtwr7qvj+BWYD=FQowOwRQBuTbJAt-W3Cuz2Lfx=r_xw@mail.gmail.com>

On Thu, Jan 8, 2015 at 1:13 PM, Dan Lipsa <dan.lipsa at kitware.com> wrote:
>>>>
>>>> Looking at VTK, the HDF5 we upgraded to now has 2.8.10 and 2.8.11
>>>> minimum requirements in it. This should probably be looked at to keep
>>>> VTK down to 2.8.8.
>
>
> Looking at the code, hdf5 files that require higher version of cmake have
> conflict markers in them, so they are obviously not used.
> I will fix the conflict markers.
>
>> What is the correct cmake version to be using to build ParaView?  I am
>> currently using 2.8.10, trying to complile hdf5-1.8.13, and it is asking for
>> at least 2.8.10.2.  May I upgrade to cmake 3.0?
>
> Indeed, upgrading cmake is usually beneficial (unless is a version not
> released). I use 3.1
>
As VTK is a basis for a number of codes, and is used across quite a
few distros, we tend to be a little more conservative on bumping
requirements. I would ask if HDF5 really needs a newer version, or did
they just bump it to what they had installed at the time?

If there isn't a compelling reason I think we should remain
conservative, and it sounds like there is not in this case (especially
for a dependency that is pretty optional for many of our users). You
can generally always use the latest CMake if you choose, but making
that the minimum makes it harder for others to compile and use our
code (often using the packaged CMake).

Marcus

From utkarsh.ayachit at kitware.com  Fri Jan  9 10:44:02 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 9 Jan 2015 10:44:02 -0500
Subject: [Paraview-developers] Gatekeeper Review Summary
Message-ID: <CADHSJjB+6hFDQLiCLsHL5otC14MPWXkWLHfXE3aF07J2escK=w@mail.gmail.com>

Topics merged into master (v4.3.0-RC1-38-g47da2d3):
        active_values_from_visible_objects
        fix_showinmenu_hints
        fix_stereotype_view_property
        libpng-warnings
        pvweb-request-interactive-render

From utkarsh.ayachit at kitware.com  Fri Jan  9 10:51:03 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 9 Jan 2015 10:51:03 -0500
Subject: [Paraview-developers] plugin filter icon/menu
In-Reply-To: <54AFA88D.5060408@ec-nantes.fr>
References: <54AE7D99.1040806@ec-nantes.fr>
 <CADHSJjBYUbw4eFCTaj=-Yu+TWVbdKif2RsQ++tVv8hLMB_150Q@mail.gmail.com>
 <CADHSJjAYXhVAvJ5cmVEun7sL4MCOQVgLCyNj_zNesCtgo+fDyw@mail.gmail.com>
 <54AFA88D.5060408@ec-nantes.fr>
Message-ID: <CADHSJjBHEvVZ0jvSJJxVJmz3oyaSM-zGT0hAENO9ZMz2fnLqWg@mail.gmail.com>

Yup...fixed merged that change as well. Thanks!
BTW, I don't see the duplicate VCR controls in my build.

Utkarsh

On Fri, Jan 9, 2015 at 5:08 AM, Felipe Bordeu
<felipe.bordeu at ec-nantes.fr> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> thanks I add the line (this->Internal->addProxy(group, name,
> showInMenu->GetAttribute("icon"));) in my paraview sources and the icons are
> visible again. thanks.
>
> But what about the toolbar?. the "show_in_toolbar" option is also lost.
>
> adding these lines(after the line 806 in your patch) make the
> show_in_toolbar work again.
>
>           int show_in_toolbar = 0;
>           hint->GetScalarAttribute("show_in_toolbar", &show_in_toolbar);
>           category.ShowInToolbar = category.ShowInToolbar ||
> (show_in_toolbar == 1);
>
> in this case we have to put a new tag in the xml hints.
>
>        <ShowInMenu category="PXDMF"
> icon=":/PXDMFIcons/AnnotateFieldData.png" show_in_toolbar="1" />
>
>
> I don't know if this happens only in my 4.3-RC1 but the View->Toolbars menu
> show  2 "VCR Controls" submenus. Can anyone confirm this.
>
> thanks
> Felipe
>
>
>
>
> Le 08/01/2015 15:48, Utkarsh Ayachit a ??crit :
>> Here's the change:
>>? ? ?  http://review.source.kitware.com/#/c/18740/
>>
>> Should make it into the official release of 4.3.
>>
>> Utkarsh
>>
>> On Thu, Jan 8, 2015 at 9:31 AM, Utkarsh Ayachit
>> <utkarsh.ayachit at kitware.com> wrote:
>>> Good catch. I don't exactly know what the PipelineIcon hint is.
>>> Looking at the code I don't think it was intended to be functional.
>>> I'll track down the developer and figure that part out. I am adding
>>> support to add a new attribute "icon" to the <ShowInMenu > element.
>>>
>>> e.g.
>>>? ? ?  <Hints>
>>>? ? ? ? ? ?  <ShowInMenu icon="...." />
>>>? ?  </Hints>
>>>
>>> Utkarsh
>>>
>>> On Thu, Jan 8, 2015 at 7:52 AM, Felipe Bordeu
>>> <felipe.bordeu at ec-nantes.fr> wrote:
>>>>
>> Hello,
>>
>> I'm porting my plugin into version 4.3 and I'm unable to set the icons
>> for my filters.
>> I tried : (http://www.paraview.org/Wiki/ParaView/Plugin_HowTo(
>>
>> ...
>> ?  <Hints>
>> ? ? ?  <ShowInMenu category="PXDMF" />
>> ? ? ?  <PipelineIcon name=":/PXDMFIcons/AnnotateFieldData.png"?  />
>> ?  </Hints>
>> </SourceProxy>
>>
>> ...
>> but does not work. Searching for the keyword "PipelineIcon" in the
>> Paraview sources gives no results.
>>
>> also :?  the?  ShowInMenu shows the filter in a new submenu but the is no
>> new toolbar as in the 4.2.
>>
>> in the 4.2 version this was my GUI xml
>>
>> <ParaViewFilters>
>> ?  <Category name="PXDMF" menu_label="&amp;PXDMF" show_in_toolbar="1">
>> ? ? ? ? ?  <!-- adds a new category and then adds our filter to it -->
>> ? ? ? ? ?  <Filter name="AnnotateFieldData"
>> icon=":/PXDMFIcons/AnnotateFieldData.png" />
>> ?  </Category>
>> </ParaViewFilters>
>>
>> any ideas.
>>
>> Thanks to all. And thanks for this new version.
>> Felipe
>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Paraview-developers mailing list
>>>> Paraview-developers at paraview.org
>>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>
> - --
> Felipe Bordeu Weldt
> Ing??nieur de Recherche
> - -------------------------------------
> T??l. : 33 (0)2 40 37 16 57
> Fax. : 33 (0)2 40 74 74 06
> Felipe.Bordeu at ec-nantes.fr
> Institut GeM - UMR CNRS 6183
> ??cole Centrale Nantes
> 1 Rue de La No??, 44321 Nantes, FRANCE
> - -------------------------------------
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBAgAGBQJUr6iHAAoJEE/fMfNgU9/D/VUIAJKWqm+fIhqGckxda4bqrxZI
> 2ztfvVU8h9PbJN1LFpf8pSHTMETI4Lf6LN8YDuUH6F5YI/jEZHl7wF1N1ygaDHI4
> 6hllc1/lyJPd3n3LROoPNd9/A2eUv9oNZzW1u7LjHbKdq/M1yi1XKYUzFKJdgAlb
> 4W060OBKlalGcgasHxWa7+U5breML/3D11Why+HP/oTAA4p9HdRIyUxjpBjmYxRk
> luS4bnEi9RlD1vDFzldYQm2fzNHJ4jllq35QbYcTzkOHSTNtRzwAqXGHc1J0z0V7
> Wi9bUu1uKKfYC0pxHYrjYh1/PlJ5+cVoFW9+cPIOUwB0/Ex95Tr2TzyiO62ZLPI=
> =ta6C
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>

From dave.demarle at kitware.com  Fri Jan  9 10:53:00 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Fri, 9 Jan 2015 10:53:00 -0500
Subject: [Paraview-developers] CMake Version
In-Reply-To: <CAMkPkZWtwr7qvj+BWYD=FQowOwRQBuTbJAt-W3Cuz2Lfx=r_xw@mail.gmail.com>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
 <20150108150323.GA26903@megas.kitwarein.com>
 <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>
 <CANjZAi-+bT4DiLs6DcT_5=3okWzuC2c547mRnMC6TxgdDstqZQ@mail.gmail.com>
 <CADwGrVokKwcrmo4moRvz-Lu6v0_ybqBBHHuoH9Kkoc1Tqoub_Q@mail.gmail.com>
 <CAMkPkZWtwr7qvj+BWYD=FQowOwRQBuTbJAt-W3Cuz2Lfx=r_xw@mail.gmail.com>
Message-ID: <CANjZAi98_=qEpfoARjmPn2u_fpKOCRSefZZFha=2A+Sdk=j-Gw@mail.gmail.com>

>
> If there isn't a compelling reason I think we should remain
> conservative, and it sounds like there is not in this case (especially
> for a dependency that is pretty optional for many of our users).


Agreed. One factor in the minimum required decision is what the popular
Linux distros have readily on hand.


> You
> can generally always use the latest CMake if you choose, but making
> that the minimum makes it harder for others to compile and use our
> code (often using the packaged CMake).
>
>
Agreed again. The "faraway" submission in the dependencies track of the vtk
dashboard exists to verity that CMake master works for VTK. Unfortunately
it didn't submit today so someone needs to shove it.


> Marcus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150109/eb9164d8/attachment.html>

From wascott at sandia.gov  Fri Jan  9 12:10:07 2015
From: wascott at sandia.gov (Scott, W Alan)
Date: Fri, 9 Jan 2015 17:10:07 +0000
Subject: [Paraview-developers] [EXTERNAL] Re:  CMake Version
In-Reply-To: <CANjZAi98_=qEpfoARjmPn2u_fpKOCRSefZZFha=2A+Sdk=j-Gw@mail.gmail.com>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
 <20150108150323.GA26903@megas.kitwarein.com>
 <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>
 <CANjZAi-+bT4DiLs6DcT_5=3okWzuC2c547mRnMC6TxgdDstqZQ@mail.gmail.com>
 <CADwGrVokKwcrmo4moRvz-Lu6v0_ybqBBHHuoH9Kkoc1Tqoub_Q@mail.gmail.com>
 <CAMkPkZWtwr7qvj+BWYD=FQowOwRQBuTbJAt-W3Cuz2Lfx=r_xw@mail.gmail.com>
 <CANjZAi98_=qEpfoARjmPn2u_fpKOCRSefZZFha=2A+Sdk=j-Gw@mail.gmail.com>
Message-ID: <cc184e1a76ef4f23a73a09fb9f2da781@ES05AMSNLNT.srn.sandia.gov>

I am hearing that it makes sense to leave current minimum cmake version for VTK.  That is OK with me.  It is also always good to know that you can always use latest/ greatest Cmake.  But, that isn?t true for all packages (and I believe latest Cmake has been incompatible in the past).  Let?s update the ParaView wiki to show what Cmake version is used for the builds?  Surprisingly, upgrading Cmake versions isn?t trivial for some of us that build somewhere around a dozen platforms, and I don?t like having to guess what version to use...

Thanks all!

Alan


From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of David E DeMarle
Sent: Friday, January 09, 2015 8:53 AM
To: Marcus D. Hanwell
Cc: paraview-developers at paraview.org
Subject: [EXTERNAL] Re: [Paraview-developers] CMake Version

If there isn't a compelling reason I think we should remain
conservative, and it sounds like there is not in this case (especially
for a dependency that is pretty optional for many of our users).

Agreed. One factor in the minimum required decision is what the popular Linux distros have readily on hand.

You
can generally always use the latest CMake if you choose, but making
that the minimum makes it harder for others to compile and use our
code (often using the packaged CMake).

Agreed again. The "faraway" submission in the dependencies track of the vtk dashboard exists to verity that CMake master works for VTK. Unfortunately it didn't submit today so someone needs to shove it.

Marcus

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150109/a682800c/attachment-0001.html>

From utkarsh.ayachit at kitware.com  Sat Jan 10 08:19:41 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sat, 10 Jan 2015 08:19:41 -0500
Subject: [Paraview-developers] Gatekeeper Review Summary
Message-ID: <CADHSJjDgrVhaZsFeHTtd9nq7WhVB_SRAnSZg8B0WunGWwnbsEg@mail.gmail.com>

Topics merged into master (v4.3.0-RC1-46-g4b7a696):
(VTK)   15020_fix_OpenGL-1.2_issues
        fix_showinmenu_hints
        help-15203
        visit-gl2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150110/d39a36e9/attachment.html>

From utkarsh.ayachit at kitware.com  Sat Jan 10 20:44:06 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sat, 10 Jan 2015 20:44:06 -0500
Subject: [Paraview-developers] plugin filter icon/menu
In-Reply-To: <CADHSJjBHEvVZ0jvSJJxVJmz3oyaSM-zGT0hAENO9ZMz2fnLqWg@mail.gmail.com>
References: <54AE7D99.1040806@ec-nantes.fr>
 <CADHSJjBYUbw4eFCTaj=-Yu+TWVbdKif2RsQ++tVv8hLMB_150Q@mail.gmail.com>
 <CADHSJjAYXhVAvJ5cmVEun7sL4MCOQVgLCyNj_zNesCtgo+fDyw@mail.gmail.com>
 <54AFA88D.5060408@ec-nantes.fr>
 <CADHSJjBHEvVZ0jvSJJxVJmz3oyaSM-zGT0hAENO9ZMz2fnLqWg@mail.gmail.com>
Message-ID: <CADHSJjCxX3cc5S7KBpfWiUG0fWrKYrR5pGWYd4-TEOWS_o-oAQ@mail.gmail.com>

Felipe,

Just detected the duplicate VCR controls issue...a fix is on its way.

Utkarsh

On Fri, Jan 9, 2015 at 10:51 AM, Utkarsh Ayachit
<utkarsh.ayachit at kitware.com> wrote:
> Yup...fixed merged that change as well. Thanks!
> BTW, I don't see the duplicate VCR controls in my build.
>
> Utkarsh
>
> On Fri, Jan 9, 2015 at 5:08 AM, Felipe Bordeu
> <felipe.bordeu at ec-nantes.fr> wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> thanks I add the line (this->Internal->addProxy(group, name,
>> showInMenu->GetAttribute("icon"));) in my paraview sources and the icons are
>> visible again. thanks.
>>
>> But what about the toolbar?. the "show_in_toolbar" option is also lost.
>>
>> adding these lines(after the line 806 in your patch) make the
>> show_in_toolbar work again.
>>
>>           int show_in_toolbar = 0;
>>           hint->GetScalarAttribute("show_in_toolbar", &show_in_toolbar);
>>           category.ShowInToolbar = category.ShowInToolbar ||
>> (show_in_toolbar == 1);
>>
>> in this case we have to put a new tag in the xml hints.
>>
>>        <ShowInMenu category="PXDMF"
>> icon=":/PXDMFIcons/AnnotateFieldData.png" show_in_toolbar="1" />
>>
>>
>> I don't know if this happens only in my 4.3-RC1 but the View->Toolbars menu
>> show  2 "VCR Controls" submenus. Can anyone confirm this.
>>
>> thanks
>> Felipe
>>
>>
>>
>>
>> Le 08/01/2015 15:48, Utkarsh Ayachit a ??crit :
>>> Here's the change:
>>>? ? ?  http://review.source.kitware.com/#/c/18740/
>>>
>>> Should make it into the official release of 4.3.
>>>
>>> Utkarsh
>>>
>>> On Thu, Jan 8, 2015 at 9:31 AM, Utkarsh Ayachit
>>> <utkarsh.ayachit at kitware.com> wrote:
>>>> Good catch. I don't exactly know what the PipelineIcon hint is.
>>>> Looking at the code I don't think it was intended to be functional.
>>>> I'll track down the developer and figure that part out. I am adding
>>>> support to add a new attribute "icon" to the <ShowInMenu > element.
>>>>
>>>> e.g.
>>>>? ? ?  <Hints>
>>>>? ? ? ? ? ?  <ShowInMenu icon="...." />
>>>>? ?  </Hints>
>>>>
>>>> Utkarsh
>>>>
>>>> On Thu, Jan 8, 2015 at 7:52 AM, Felipe Bordeu
>>>> <felipe.bordeu at ec-nantes.fr> wrote:
>>>>>
>>> Hello,
>>>
>>> I'm porting my plugin into version 4.3 and I'm unable to set the icons
>>> for my filters.
>>> I tried : (http://www.paraview.org/Wiki/ParaView/Plugin_HowTo(
>>>
>>> ...
>>> ?  <Hints>
>>> ? ? ?  <ShowInMenu category="PXDMF" />
>>> ? ? ?  <PipelineIcon name=":/PXDMFIcons/AnnotateFieldData.png"?  />
>>> ?  </Hints>
>>> </SourceProxy>
>>>
>>> ...
>>> but does not work. Searching for the keyword "PipelineIcon" in the
>>> Paraview sources gives no results.
>>>
>>> also :?  the?  ShowInMenu shows the filter in a new submenu but the is no
>>> new toolbar as in the 4.2.
>>>
>>> in the 4.2 version this was my GUI xml
>>>
>>> <ParaViewFilters>
>>> ?  <Category name="PXDMF" menu_label="&amp;PXDMF" show_in_toolbar="1">
>>> ? ? ? ? ?  <!-- adds a new category and then adds our filter to it -->
>>> ? ? ? ? ?  <Filter name="AnnotateFieldData"
>>> icon=":/PXDMFIcons/AnnotateFieldData.png" />
>>> ?  </Category>
>>> </ParaViewFilters>
>>>
>>> any ideas.
>>>
>>> Thanks to all. And thanks for this new version.
>>> Felipe
>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Paraview-developers mailing list
>>>>> Paraview-developers at paraview.org
>>>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>> - --
>> Felipe Bordeu Weldt
>> Ing??nieur de Recherche
>> - -------------------------------------
>> T??l. : 33 (0)2 40 37 16 57
>> Fax. : 33 (0)2 40 74 74 06
>> Felipe.Bordeu at ec-nantes.fr
>> Institut GeM - UMR CNRS 6183
>> ??cole Centrale Nantes
>> 1 Rue de La No??, 44321 Nantes, FRANCE
>> - -------------------------------------
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1
>>
>> iQEcBAEBAgAGBQJUr6iHAAoJEE/fMfNgU9/D/VUIAJKWqm+fIhqGckxda4bqrxZI
>> 2ztfvVU8h9PbJN1LFpf8pSHTMETI4Lf6LN8YDuUH6F5YI/jEZHl7wF1N1ygaDHI4
>> 6hllc1/lyJPd3n3LROoPNd9/A2eUv9oNZzW1u7LjHbKdq/M1yi1XKYUzFKJdgAlb
>> 4W060OBKlalGcgasHxWa7+U5breML/3D11Why+HP/oTAA4p9HdRIyUxjpBjmYxRk
>> luS4bnEi9RlD1vDFzldYQm2fzNHJ4jllq35QbYcTzkOHSTNtRzwAqXGHc1J0z0V7
>> Wi9bUu1uKKfYC0pxHYrjYh1/PlJ5+cVoFW9+cPIOUwB0/Ex95Tr2TzyiO62ZLPI=
>> =ta6C
>> -----END PGP SIGNATURE-----
>>
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>

From utkarsh.ayachit at kitware.com  Sun Jan 11 08:10:55 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Sun, 11 Jan 2015 08:10:55 -0500
Subject: [Paraview-developers] Gatekeeper Review Summary
Message-ID: <CADHSJjCUmXPibFEZsciL_SSz93OHnKRmF6GzXGi92ZAXk1J7cA@mail.gmail.com>

Topics merged into master (v4.3.0-RC1-50-g81dbfe2):
        15247_fix_wheel

From sebastien.jourdain at kitware.com  Mon Jan 12 09:05:55 2015
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Mon, 12 Jan 2015 07:05:55 -0700
Subject: [Paraview-developers] ParaViewWeb 4.1 Data Prober not working
	in Linux
In-Reply-To: <CAGCCciQ-H3eLMaCC8aNHVDwzGhixFXpwxTChFQYp5dZ0qfeCWw@mail.gmail.com>
References: <CAGCCciQ-H3eLMaCC8aNHVDwzGhixFXpwxTChFQYp5dZ0qfeCWw@mail.gmail.com>
Message-ID: <E2CAD5F6-2619-4903-93FE-9B72860F9DE9@kitware.com>

Since you are on Ubuntu now. Can you try 4.2?



> On Jan 12, 2015, at 01:05, Debanshu Saha <debanshu at 2pirad.com> wrote:
> 
> Hi Seb,
> 
> As per your advice I have installed Ubuntu and tried starting ParaView Web here. Please find the screenshots below.
> 
> 1. Directory Structure:
> Logs: For ParaView Logs, path mentioned in pw-config.properties.
> ParaView-4.1.0-Linux-64bit: Binary Files for ParaView.
> JettySessionManager-Server-1.0.jar: Jar file of Jetty Session Manager.
> pw-config.properties: Property file for starting Jetty Session Manager.
> StartJettyParaview.sh: Shell Script for starting Jetty Session Manager. Command used in the script is as follows
> java -jar JettySerssionManager-Server-1.0.jar pw-config.properties
>     
> <image.png>
> 
> 2. Directory structure of ParaView-4.1.0-Linux-64bit as downloaded from ParaView Website:-
> 
> <image.png>
> 
> 3. Starting ParaViewWeb with Jetty Session Manager:-
> Please see the error message in the developer tool. The graph in the left side is not coming. Even when we are selecting any mesh file to display, the 3D image is coming but the graph is still not displayed. 
> <image.png>
> 
> 4. Error pointing to the JavaScript code:-
> <image.png>
> 
> Please find the attached properties file. Kindly note that visualizer module is working fine with this configuration. 
> 
> As discussed with you previously, we were using Windows to run ParaView where we got same error. After your suggestion, we shifted it to Linux(Ubuntu 14.10 x64), but still facing the same problem. Kindly tell us what is the problem and where are we going wrong.
> 
> 
> Regards
> Debanshu
> 2PiRad
> Contact: +91-8981409005
> <pw-config.properties>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150112/a7eade8c/attachment.html>

From debanshu at 2pirad.com  Mon Jan 12 13:09:00 2015
From: debanshu at 2pirad.com (Debanshu Saha)
Date: Mon, 12 Jan 2015 23:39:00 +0530
Subject: [Paraview-developers] ParaViewWeb 4.1 Data Prober not working
	in Linux
In-Reply-To: <E2CAD5F6-2619-4903-93FE-9B72860F9DE9@kitware.com>
References: <CAGCCciQ-H3eLMaCC8aNHVDwzGhixFXpwxTChFQYp5dZ0qfeCWw@mail.gmail.com>
 <E2CAD5F6-2619-4903-93FE-9B72860F9DE9@kitware.com>
Message-ID: <CAGCCciTEa4nOxHfw91uoUrUV-KuP0CZtAPS9-g52Qvmht6iVog@mail.gmail.com>

Hi Seb,

We had tried that too. But we could not find the files
pv_web_data_prober.py, pv_web_file_loader.py and pv_web_visualizer.py in
4.2 version, as were in 4.1. Then what would we mention in the
pw-config.properties file?

*Regards*
Debanshu
*2PiRad*
*Contact: *+91-8981409005

On Mon, Jan 12, 2015 at 7:35 PM, Sebastien Jourdain <
sebastien.jourdain at kitware.com> wrote:

> Since you are on Ubuntu now. Can you try 4.2?
>
>
>
> On Jan 12, 2015, at 01:05, Debanshu Saha <debanshu at 2pirad.com> wrote:
>
> Hi Seb,
>
> As per your advice I have installed Ubuntu and tried starting ParaView Web
> here. Please find the screenshots below.
>
> 1. Directory Structure:
> Logs: For ParaView Logs, path mentioned in pw-config.properties.
> ParaView-4.1.0-Linux-64bit: Binary Files for ParaView.
> JettySessionManager-Server-1.0.jar: Jar file of Jetty Session Manager.
> pw-config.properties: Property file for starting Jetty Session Manager.
> StartJettyParaview.sh: Shell Script for starting Jetty Session Manager.
> Command used in the script is as follows
> *java -jar JettySerssionManager-Server-1.0.jar pw-config.properties*
>
> <image.png>
>
> 2. Directory structure of ParaView-4.1.0-Linux-64bit as downloaded from
> ParaView Website:-
>
> <image.png>
>
> 3. Starting ParaViewWeb with Jetty Session Manager:-
> Please see the error message in the developer tool. The graph in the left
> side is not coming. Even when we are selecting any mesh file to display,
> the 3D image is coming but the graph is still not displayed.
> <image.png>
>
> 4. Error pointing to the JavaScript code:-
> <image.png>
>
> Please find the attached properties file. Kindly note that visualizer
> module is working fine with this configuration.
>
> As discussed with you previously, we were using Windows to run ParaView
> where we got same error. After your suggestion, we shifted it to
> Linux(Ubuntu 14.10 x64), but still facing the same problem. Kindly tell us
> what is the problem and where are we going wrong.
>
>
> *Regards*
> Debanshu
> *2PiRad*
> *Contact: *+91-8981409005
>
> <pw-config.properties>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150112/2f1a883b/attachment-0001.html>

From sebastien.jourdain at kitware.com  Mon Jan 12 13:09:26 2015
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Mon, 12 Jan 2015 11:09:26 -0700
Subject: [Paraview-developers] ParaViewWeb 4.1 Data Prober not working
	in Linux
In-Reply-To: <CAGCCciTEa4nOxHfw91uoUrUV-KuP0CZtAPS9-g52Qvmht6iVog@mail.gmail.com>
References: <CAGCCciQ-H3eLMaCC8aNHVDwzGhixFXpwxTChFQYp5dZ0qfeCWw@mail.gmail.com>
 <E2CAD5F6-2619-4903-93FE-9B72860F9DE9@kitware.com>
 <CAGCCciTEa4nOxHfw91uoUrUV-KuP0CZtAPS9-g52Qvmht6iVog@mail.gmail.com>
Message-ID: <CABObKxdhD-oeNgEBZZeALh9w25tjExGiHEgxpG9UV3U9o8TMpg@mail.gmail.com>

They should be there on Linux.

On Mon, Jan 12, 2015 at 11:09 AM, Debanshu Saha <debanshu at 2pirad.com> wrote:

> Hi Seb,
>
> We had tried that too. But we could not find the files
> pv_web_data_prober.py, pv_web_file_loader.py and pv_web_visualizer.py in
> 4.2 version, as were in 4.1. Then what would we mention in the
> pw-config.properties file?
>
> *Regards*
> Debanshu
> *2PiRad*
> *Contact: *+91-8981409005
>
> On Mon, Jan 12, 2015 at 7:35 PM, Sebastien Jourdain <
> sebastien.jourdain at kitware.com> wrote:
>
>> Since you are on Ubuntu now. Can you try 4.2?
>>
>>
>>
>> On Jan 12, 2015, at 01:05, Debanshu Saha <debanshu at 2pirad.com> wrote:
>>
>> Hi Seb,
>>
>> As per your advice I have installed Ubuntu and tried starting ParaView
>> Web here. Please find the screenshots below.
>>
>> 1. Directory Structure:
>> Logs: For ParaView Logs, path mentioned in pw-config.properties.
>> ParaView-4.1.0-Linux-64bit: Binary Files for ParaView.
>> JettySessionManager-Server-1.0.jar: Jar file of Jetty Session Manager.
>> pw-config.properties: Property file for starting Jetty Session Manager.
>> StartJettyParaview.sh: Shell Script for starting Jetty Session Manager.
>> Command used in the script is as follows
>> *java -jar JettySerssionManager-Server-1.0.jar pw-config.properties*
>>
>> <image.png>
>>
>> 2. Directory structure of ParaView-4.1.0-Linux-64bit as downloaded from
>> ParaView Website:-
>>
>> <image.png>
>>
>> 3. Starting ParaViewWeb with Jetty Session Manager:-
>> Please see the error message in the developer tool. The graph in the left
>> side is not coming. Even when we are selecting any mesh file to display,
>> the 3D image is coming but the graph is still not displayed.
>> <image.png>
>>
>> 4. Error pointing to the JavaScript code:-
>> <image.png>
>>
>> Please find the attached properties file. Kindly note that visualizer
>> module is working fine with this configuration.
>>
>> As discussed with you previously, we were using Windows to run ParaView
>> where we got same error. After your suggestion, we shifted it to
>> Linux(Ubuntu 14.10 x64), but still facing the same problem. Kindly tell us
>> what is the problem and where are we going wrong.
>>
>>
>> *Regards*
>> Debanshu
>> *2PiRad*
>> *Contact: *+91-8981409005
>>
>> <pw-config.properties>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150112/8a92cc11/attachment.html>

From dan.lipsa at kitware.com  Mon Jan 12 22:57:18 2015
From: dan.lipsa at kitware.com (Dan Lipsa)
Date: Mon, 12 Jan 2015 22:57:18 -0500
Subject: [Paraview-developers] [EXTERNAL] Re: CMake Version
In-Reply-To: <cc184e1a76ef4f23a73a09fb9f2da781@ES05AMSNLNT.srn.sandia.gov>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
 <20150108150323.GA26903@megas.kitwarein.com>
 <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>
 <CANjZAi-+bT4DiLs6DcT_5=3okWzuC2c547mRnMC6TxgdDstqZQ@mail.gmail.com>
 <CADwGrVokKwcrmo4moRvz-Lu6v0_ybqBBHHuoH9Kkoc1Tqoub_Q@mail.gmail.com>
 <CAMkPkZWtwr7qvj+BWYD=FQowOwRQBuTbJAt-W3Cuz2Lfx=r_xw@mail.gmail.com>
 <CANjZAi98_=qEpfoARjmPn2u_fpKOCRSefZZFha=2A+Sdk=j-Gw@mail.gmail.com>
 <cc184e1a76ef4f23a73a09fb9f2da781@ES05AMSNLNT.srn.sandia.gov>
Message-ID: <CADwGrVrGj0+3hx8rXEpgWZJexA0Naco2f2pqW1zOF2DS34G8qQ@mail.gmail.com>

http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisites

has the correct minimum version required for cmake 2.8.8.

Dan


On Fri, Jan 9, 2015 at 12:10 PM, Scott, W Alan <wascott at sandia.gov> wrote:

>  I am hearing that it makes sense to leave current minimum cmake version
> for VTK.  That is OK with me.  It is also always good to know that you can
> always use latest/ greatest Cmake.  But, that isn?t true for all packages
> (and I believe latest Cmake has been incompatible in the past).  Let?s
> update the ParaView wiki to show what Cmake version is used for the
> builds?  Surprisingly, upgrading Cmake versions isn?t trivial for some of
> us that build somewhere around a dozen platforms, and I don?t like having
> to guess what version to use...
>
>
>
> Thanks all!
>
>
>
> Alan
>
>
>
>
>
> *From:* Paraview-developers [mailto:
> paraview-developers-bounces at paraview.org] *On Behalf Of *David E DeMarle
> *Sent:* Friday, January 09, 2015 8:53 AM
> *To:* Marcus D. Hanwell
> *Cc:* paraview-developers at paraview.org
> *Subject:* [EXTERNAL] Re: [Paraview-developers] CMake Version
>
>
>
> If there isn't a compelling reason I think we should remain
> conservative, and it sounds like there is not in this case (especially
> for a dependency that is pretty optional for many of our users).
>
>
>
> Agreed. One factor in the minimum required decision is what the popular
> Linux distros have readily on hand.
>
>
>
>  You
> can generally always use the latest CMake if you choose, but making
> that the minimum makes it harder for others to compile and use our
> code (often using the packaged CMake).
>
>
>
> Agreed again. The "faraway" submission in the dependencies track of the
> vtk dashboard exists to verity that CMake master works for VTK.
> Unfortunately it didn't submit today so someone needs to shove it.
>
>
>
> Marcus
>
>
>
> _______________________________________________
> 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/20150112/b149142b/attachment.html>

From jfavre at cscs.ch  Tue Jan 13 07:17:44 2015
From: jfavre at cscs.ch (Favre  Jean)
Date: Tue, 13 Jan 2015 12:17:44 +0000
Subject: [Paraview-developers] reader crashing when default timestep is set
	to last_timestep
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F682AEC8AD0@MBX111.d.ethz.ch>

Hello all

I have a reader for an internal file format which is not time-aware (no timestep value is provided). Thus I store one timestep per file. The XML description makes my reader inherit from vtkFileSeriesReader with the following property.

     <DoubleVectorProperty 
        name="TimestepValues"
        repeatable="1"
        information_only="1">
        <TimeStepsInformationHelper/>
     </DoubleVectorProperty>

if my default timestep is set to "go to first timestep", everything is good and I can animate and read any file in my file series.
If instead the default is set to "go to last timestep", paraview crashes in UpdateInformation in pqDataTimeStepBehavior.cxx line 81

scene->setAnimationTime(timesteps[newTimeStep]);

because newTimeStep has a huge value. My own code is not time-aware, so I have no source code specific to time.

Further, paraview also crashes  if I have a single file, instead of a file series. 
I don't know if I need to give another XML hint, or if my RequestInformation() code should have anything special.

I'd appreciate any clue. (this is the latest git pull)
-----------------
Jean
CSCS

From utkarsh.ayachit at kitware.com  Tue Jan 13 08:15:59 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 13 Jan 2015 05:15:59 -0800
Subject: [Paraview-developers] reader crashing when default timestep is
 set to last_timestep
In-Reply-To: <0EB9B6375711A04B820E6B6F5CCA9F682AEC8AD0@MBX111.d.ethz.ch>
References: <0EB9B6375711A04B820E6B6F5CCA9F682AEC8AD0@MBX111.d.ethz.ch>
Message-ID: <CADHSJjDEFs4OfzttFTOeeu+daHy0E6dv9ySMT3CtE6ZczWYjHg@mail.gmail.com>

A fix is on its way: http://review.source.kitware.com/#/t/5274/

Utkarsh

On Tue, Jan 13, 2015 at 4:17 AM, Favre  Jean <jfavre at cscs.ch> wrote:
> Hello all
>
> I have a reader for an internal file format which is not time-aware (no timestep value is provided). Thus I store one timestep per file. The XML description makes my reader inherit from vtkFileSeriesReader with the following property.
>
>      <DoubleVectorProperty
>         name="TimestepValues"
>         repeatable="1"
>         information_only="1">
>         <TimeStepsInformationHelper/>
>      </DoubleVectorProperty>
>
> if my default timestep is set to "go to first timestep", everything is good and I can animate and read any file in my file series.
> If instead the default is set to "go to last timestep", paraview crashes in UpdateInformation in pqDataTimeStepBehavior.cxx line 81
>
> scene->setAnimationTime(timesteps[newTimeStep]);
>
> because newTimeStep has a huge value. My own code is not time-aware, so I have no source code specific to time.
>
> Further, paraview also crashes  if I have a single file, instead of a file series.
> I don't know if I need to give another XML hint, or if my RequestInformation() code should have anything special.
>
> I'd appreciate any clue. (this is the latest git pull)
> -----------------
> Jean
> CSCS
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers

From jfavre at cscs.ch  Tue Jan 13 08:30:42 2015
From: jfavre at cscs.ch (Favre  Jean)
Date: Tue, 13 Jan 2015 13:30:42 +0000
Subject: [Paraview-developers] reader crashing when default timestep is
 set to last_timestep
In-Reply-To: <CADHSJjDEFs4OfzttFTOeeu+daHy0E6dv9ySMT3CtE6ZczWYjHg@mail.gmail.com>
References: <0EB9B6375711A04B820E6B6F5CCA9F682AEC8AD0@MBX111.d.ethz.ch>,
 <CADHSJjDEFs4OfzttFTOeeu+daHy0E6dv9ySMT3CtE6ZczWYjHg@mail.gmail.com>
Message-ID: <0EB9B6375711A04B820E6B6F5CCA9F682AEC8AF7@MBX111.d.ethz.ch>


Indeed. I applied the fix and it is working great.

Thanks Kitware.

From utkarsh.ayachit at kitware.com  Tue Jan 13 22:50:18 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 13 Jan 2015 19:50:18 -0800
Subject: [Paraview-developers] ANN: ParaView 4.3.1 Tagged!
Message-ID: <CADHSJjA8L1QMqoF2ULBG9pD=Kzz+wxioA0ZVrxeVQzt2x9Ujgg@mail.gmail.com>

Folks!

ParaView 4.3.1 has been tagged.

git tag name: v4.3.1
Binaries will be available within the next few days.

p.s. there will be no 4.3.0 as a bug was detected and fixed soon after
the tag was made.

From felipe.bordeu at ec-nantes.fr  Wed Jan 14 10:41:13 2015
From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu)
Date: Wed, 14 Jan 2015 16:41:13 +0100
Subject: [Paraview-developers] ParaView crash saving data in xdmf with an
	stringArray
Message-ID: <54B68E19.4090009@ec-nantes.fr>


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

bug reported in

http://public.kitware.com/Bug/view.php?id=15350

When the new xdmf (xdmf3) implementation will be shipped with ParaView?

Felipe

- -- 
Felipe Bordeu Weldt
Ing?nieur de Recherche
- -------------------------------------
T?l. : 33 (0)2 40 37 16 57
Fax. : 33 (0)2 40 74 74 06
Felipe.Bordeu at ec-nantes.fr
Institut GeM - UMR CNRS 6183
?cole Centrale Nantes
1 Rue de La No?, 44321 Nantes, FRANCE
- -------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUto4TAAoJEE/fMfNgU9/Dh14IAMEsUpFH6PVuwAeuUVSvCxx3
Dy36vBkGeNfsO2dPzj6lyUHc4kV0FFAn1EAV6F8uDwNIQWoh35jB892m48sHkOwS
UGxw9QXvTYGWVAJ3dppnSHt6JCnlv14pDq1hP//fNyRAUgNe8tXEpg3ysMtBjk2Y
ib8+Y5C9gkQNZmDiDs2myhfRB9W9uHo/s1g2BCVlT9DXyxq+64TNEaA8RvQUiuda
lv7+MD7h9HvJTscJu5ZePaV+fZ/1cI/gO8tmdYgZmDU12zMArJuBK6e/vTkRfvBJ
Cl5iFvyp9P6AAfnMAgDWPcw1er7sVoSWHQrI7Za5UdTrOWnZM6L9UoH7irwaFrg=
=kpby
-----END PGP SIGNATURE-----


From Joshua.Murphy at lasp.colorado.edu  Wed Jan 14 15:05:39 2015
From: Joshua.Murphy at lasp.colorado.edu (Joshua Murphy)
Date: Wed, 14 Jan 2015 13:05:39 -0700
Subject: [Paraview-developers] Super build issues on Yellowstone
Message-ID: <100E56F4-B2A6-47BF-874C-A1FD59342D2F@lasp.colorado.edu>

Hi all,

Has anyone successfully built the superbuild of Paraview on Yellowstone (actually, caldera)?  I am attempting to compile, and I keep getting a freetype build failure.

Here is the failure:

/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/libtool --mode=compile gcc -pedantic -ansi -fPIC -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/builds/unix -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/include -c -Wall -fPIC -DFT_CONFIG_OPTION_SYSTEM_ZLIB -DFT_CONFIG_OPTION_USE_BZIP2 -DFT_CONFIG_CONFIG_H="<ftconfig.h>" -DFT2_BUILD_LIBRARY -DFT_CONFIG_MODULES_H="<ftmodule.h>"  -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base -o /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/ftbase.lo /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base/ftbase.c
libtool: compile:  gcc -pedantic -ansi -fPIC -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/builds/unix -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/include -c -Wall -fPIC -DFT_CONFIG_OPTION_SYSTEM_ZLIB -DFT_CONFIG_OPTION_USE_BZIP2 "-DFT_CONFIG_CONFIG_H=<ftconfig.h>" -DFT2_BUILD_LIBRARY "-DFT_CONFIG_MODULES_H=<ftmodule.h>" -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base/ftbase.c  -fPIC -DPIC -o /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/.libs/ftbase.o
/glade/apps/opt/modulefiles/ys/cmpwrappers/gcc[52]: eval[1]: -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base: cannot create [No such file or directory]
make: *** [/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/ftbase.lo] Error 1

=====

If anyone has had any luck with this, could you please let me know the trick?

Thanks,
Josh


From Gerald.Lodron at joanneum.at  Thu Jan 15 03:51:12 2015
From: Gerald.Lodron at joanneum.at (Lodron, Gerald)
Date: Thu, 15 Jan 2015 08:51:12 +0000
Subject: [Paraview-developers] Changes from PV4.1 to PV4.3 - color
Message-ID: <ff5173d8c9394a428752c49b953331d3@RZJMBX2.jr1.local>

Hello

I successfully updated paraview and my plugins from 4.1 with qt4 to 4.3 with qt5. But now my personal polydata meshes were not colored correctly. In paraview 4.1 I added Point Attribute based field data to my triangles (vtkPolydata object) with a 3 component RGB unsigned char array named color to color the meshes. Now in PV4.3 only the magnitude is displayed. Am I doing something wrong?

Thanks for help and tips

Gerald



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150115/4a774b0a/attachment.html>

From Gerald.Lodron at joanneum.at  Thu Jan 15 04:04:38 2015
From: Gerald.Lodron at joanneum.at (Lodron, Gerald)
Date: Thu, 15 Jan 2015 09:04:38 +0000
Subject: [Paraview-developers] WG: Changes from PV4.1 to PV4.3 - color
In-Reply-To: <ff5173d8c9394a428752c49b953331d3@RZJMBX2.jr1.local>
References: <ff5173d8c9394a428752c49b953331d3@RZJMBX2.jr1.local>
Message-ID: <efd9046f9ea34bc1afcacc81214ac179@RZJMBX2.jr1.local>

Hello

My fault/blame/shame. Forgot disabling MapScalars in Advanced settings..... arg

Thanks/Sorry for disturbing....

Von: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] Im Auftrag von Lodron, Gerald
Gesendet: Donnerstag, 15. J?nner 2015 09:51
An: Paraview Developer (Paraview-developers at paraview.org); Paraview User (paraview at paraview.org)
Betreff: [Paraview-developers] Changes from PV4.1 to PV4.3 - color

Hello

I successfully updated paraview and my plugins from 4.1 with qt4 to 4.3 with qt5. But now my personal polydata meshes were not colored correctly. In paraview 4.1 I added Point Attribute based field data to my triangles (vtkPolydata object) with a 3 component RGB unsigned char array named color to color the meshes. Now in PV4.3 only the magnitude is displayed. Am I doing something wrong?

Thanks for help and tips

Gerald



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150115/75ed5074/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150115/75ed5074/attachment.txt>

From utkarsh.ayachit at kitware.com  Thu Jan 15 17:40:47 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 15 Jan 2015 14:40:47 -0800
Subject: [Paraview-developers] ParaView User's Guide
Message-ID: <CADHSJjDCv12E-8PqTZ=na4KgwqehAo15pKMU8XhfkPZbz7GHKA@mail.gmail.com>

Folks,

The ParaView User's Guide is very close to being ready for the public.
As several of you know, it has now moved to LaTeX files. Now the next
question is where do these live? Our original plan was to include the
files in the ParaView source repository itself. That would make it
easier to enforce that developer document UI changes along with the
commits that change the UI/Python API etc. However, the source files
(and high resolution images) are close to 500 MB, hence not ideal for
inclusion in the ParaView source.

Another option is to put that in a separate repository. Then, to
enforce the "document as you go" requirement, we won't approve merge
requests (once we move to gitlab, or topics on gerrit until then)
unless the commit log references a commit in the documentation
repository.

Any other suggestions? What are people's thoughts?

Utkarsh

From david.thompson at kitware.com  Thu Jan 15 17:46:55 2015
From: david.thompson at kitware.com (David Thompson)
Date: Thu, 15 Jan 2015 17:46:55 -0500
Subject: [Paraview-developers] ParaView User's Guide
In-Reply-To: <CADHSJjDCv12E-8PqTZ=na4KgwqehAo15pKMU8XhfkPZbz7GHKA@mail.gmail.com>
References: <CADHSJjDCv12E-8PqTZ=na4KgwqehAo15pKMU8XhfkPZbz7GHKA@mail.gmail.com>
Message-ID: <2C11C5BD-8579-40C2-AD7D-72EB5C4851CD@kitware.com>

> The ParaView User's Guide is very close to being ready for the public.
> ... the next question is where do these [LaTeX files] live? ... the
> source files (and high resolution images) are close to 500 MB, hence
> not ideal for inclusion in the ParaView source. ...
> Any other suggestions? What are people's thoughts?

I think the ExternalData implementation is too opaque, but the strategy (store images and binary files outside of version control) would be useful. Are even the LaTeX files too large for the ParaView repo, or could they be stored with the source and rely on images being downloaded?

	2?,
	David

From utkarsh.ayachit at kitware.com  Thu Jan 15 17:52:16 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 15 Jan 2015 14:52:16 -0800
Subject: [Paraview-developers] ParaView User's Guide
In-Reply-To: <2C11C5BD-8579-40C2-AD7D-72EB5C4851CD@kitware.com>
References: <CADHSJjDCv12E-8PqTZ=na4KgwqehAo15pKMU8XhfkPZbz7GHKA@mail.gmail.com>
 <2C11C5BD-8579-40C2-AD7D-72EB5C4851CD@kitware.com>
Message-ID: <CADHSJjAQnZAtgJmzB4eCo9=dupyUUZcotToG-mNEHNkeQNMF+g@mail.gmail.com>

That's a good idea (I agree, it's too opaque indeed). No, the LaTeX
files themselves are not an issue, size-wise, much smaller than the
code itself, in any case.

I think I like this idea. Unless there are any other opinions, maybe
we'll stick with this one.

Utkarsh


On Thu, Jan 15, 2015 at 2:46 PM, David Thompson
<david.thompson at kitware.com> wrote:
>> The ParaView User's Guide is very close to being ready for the public.
>> ... the next question is where do these [LaTeX files] live? ... the
>> source files (and high resolution images) are close to 500 MB, hence
>> not ideal for inclusion in the ParaView source. ...
>> Any other suggestions? What are people's thoughts?
>
> I think the ExternalData implementation is too opaque, but the strategy (store images and binary files outside of version control) would be useful. Are even the LaTeX files too large for the ParaView repo, or could they be stored with the source and rely on images being downloaded?
>
>         2?,
>         David

From david.thompson at kitware.com  Thu Jan 15 17:56:34 2015
From: david.thompson at kitware.com (David Thompson)
Date: Thu, 15 Jan 2015 17:56:34 -0500
Subject: [Paraview-developers] ParaView User's Guide
In-Reply-To: <CADHSJjAQnZAtgJmzB4eCo9=dupyUUZcotToG-mNEHNkeQNMF+g@mail.gmail.com>
References: <CADHSJjDCv12E-8PqTZ=na4KgwqehAo15pKMU8XhfkPZbz7GHKA@mail.gmail.com>
 <2C11C5BD-8579-40C2-AD7D-72EB5C4851CD@kitware.com>
 <CADHSJjAQnZAtgJmzB4eCo9=dupyUUZcotToG-mNEHNkeQNMF+g@mail.gmail.com>
Message-ID: <05475E36-30D8-4AD7-8F6D-077791E9F93D@kitware.com>

> That's a good idea (I agree, it's too opaque indeed). No, the LaTeX
> files themselves are not an issue, size-wise, much smaller than the
> code itself, in any case.
> 
> I think I like this idea. Unless there are any other opinions, maybe
> we'll stick with this one.

My only other concern would be for the LaTeX stuff to be a whole separate CMake project inside the ParaView repo so that people without a developer toolchain installed would have a chance at building it and thus contributing to it. Or will those people just stick to editing things on Github?

	David

From joachim.pouderoux at kitware.com  Fri Jan 16 08:04:43 2015
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Fri, 16 Jan 2015 14:04:43 +0100
Subject: [Paraview-developers] ANN: VTK and ParaView Training Courses in
	Lyon, France, February 3-4, 2015
Message-ID: <CACJ=gTiFThZUg1Td6T=ph=j=FMQ_8g3g4c67U9RAkOebwUK11A@mail.gmail.com>

Kitware will be holding VTK and ParaView courses on February 3-4,
2015 in Lyon, France.

Please visit our web site for more information and registration details at
either:

http://training.kitware.fr/browse/83 <http://training.kitware.fr/browse/48>
http://training.kitware.fr/browse/84 <http://training.kitware.fr/browse/48>
or in French:
http://formations.kitware.fr/browse/83
<http://formations.kitware.fr/browse/48>
http://formations.kitware.fr/browse/84
<http://formations.kitware.fr/browse/48>

Note that the course will be taught in English. If you have any question,
please contact us at formations at http://www.kitware.fr

Thank you,

*Joachim Pouderoux*

*PhD, Technical Expert*
*Kitware SAS <http://www.kitware.fr>*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150116/ec48845d/attachment.html>

From utkarsh.ayachit at kitware.com  Fri Jan 16 09:45:38 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 16 Jan 2015 06:45:38 -0800
Subject: [Paraview-developers] ParaView User's Guide
In-Reply-To: <05475E36-30D8-4AD7-8F6D-077791E9F93D@kitware.com>
References: <CADHSJjDCv12E-8PqTZ=na4KgwqehAo15pKMU8XhfkPZbz7GHKA@mail.gmail.com>
 <2C11C5BD-8579-40C2-AD7D-72EB5C4851CD@kitware.com>
 <CADHSJjAQnZAtgJmzB4eCo9=dupyUUZcotToG-mNEHNkeQNMF+g@mail.gmail.com>
 <05475E36-30D8-4AD7-8F6D-077791E9F93D@kitware.com>
Message-ID: <CADHSJjD3tQVtNngBKrUCqZV5w1rdYy3m6852p++cF6DL9wd4ZQ@mail.gmail.com>

> My only other concern would be for the LaTeX stuff to be a whole separate CMake project inside the ParaView repo so that people without a developer toolchain installed would have a chance at building it and thus contributing to it. Or will those people just stick to editing things on Github?

We could do it similar to Examples -- you can build it as part of the
regular ParaView build or separately. I don't think too many
non-ParaView deveopers (besides the Comm/Editing team) will be
contributing a whole lot, however.

From sebastien.jourdain at kitware.com  Fri Jan 16 12:12:42 2015
From: sebastien.jourdain at kitware.com (Sebastien Jourdain)
Date: Fri, 16 Jan 2015 10:12:42 -0700
Subject: [Paraview-developers] ANN: ParaView GateKeeper Review Summary
Message-ID: <CABObKxcT95ifn4GeFB8VozOm-K9XVtTmdQnTDDcEpsDKey9gPw@mail.gmail.com>

SUMMARY
---------------------------------------------
Topics merged into master (v4.3.1-18-g04df19f):
        colormap_editor_display_array_name
        fix-headertest-failure
        fix-windows-path-escaping
        fix_add_active_values
(VTK)   pvw-fix-lod-rerender
(VTK)   pvweb-add-scalar-opacity-widget
        pvweb-allow-single-datadir-with-key


---------------------------------------------
Topics reverted from next:
  help-15203
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150116/df138ff9/attachment.html>

From mickey.phy at gmail.com  Fri Jan 16 13:50:52 2015
From: mickey.phy at gmail.com (Mickael Philit)
Date: Fri, 16 Jan 2015 19:50:52 +0100
Subject: [Paraview-developers] Merge a cgns plugin fix
Message-ID: <54B95D8C.6050008@gmail.com>

Hello

Would it be possible for a developer to merge the cgns-plugin-string-fix 
topic from gerrit into the "next" branch of ParaView ?
Many thanks for considering my request.


Mickael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150116/d8297210/attachment.html>

From robert.maynard at kitware.com  Fri Jan 16 15:37:42 2015
From: robert.maynard at kitware.com (Robert Maynard)
Date: Fri, 16 Jan 2015 15:37:42 -0500
Subject: [Paraview-developers] Merge a cgns plugin fix
In-Reply-To: <54B95D8C.6050008@gmail.com>
References: <54B95D8C.6050008@gmail.com>
Message-ID: <CAFzjYVqmVS_zBSWpTadDFm-tfckkFEkQNdcnT3KLjBnPsXWipA@mail.gmail.com>

Done.

On Fri, Jan 16, 2015 at 1:50 PM, Mickael Philit <mickey.phy at gmail.com> wrote:
> Hello
>
> Would it be possible for a developer to merge the cgns-plugin-string-fix
> topic from gerrit into the "next" branch of ParaView ?
> Many thanks for considering my request.
>
>
> Mickael
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>

From biddisco at cscs.ch  Mon Jan 19 05:28:15 2015
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Mon, 19 Jan 2015 10:28:15 +0000
Subject: [Paraview-developers] 4.3 build error
Message-ID: <50320452A334BD42A5EC72BAD21450991E5B8A06@MBX210.d.ethz.ch>

I upgraded my source tree to 4.3 and got this build error

Error      12504    error C2039: 'getWidgetEventPlayer' : is not a member of 'pqEventPlayer'            pqApplicationComponents                D:\Code\ParaView\Qt\ApplicationComponents\pqParaViewBehaviors.cxx         106

I poked around and couldn't see an easy way to fix it.  The offending code introduced in commit 3f6e30bb324a343acf345abe8fe98176813a7eeb
commit 3f6e30bb324a343acf345abe8fe98176813a7eeb
Author: Yumin Yuan <yumin.yuan at kitware.com>
Date:   Tue Dec 2 10:44:50 2014 -0500

    Separated out EventPlayer from pqViewStreamingBehavior

    The pqViewStreamingBehavior contains and instantiates its own event
    player to play back its recorded event. The new QtTesting flow does
    not support this. The players have to be registered first before
    recorded event can be dispatched to the player. So the internal
    event class is moved out to be a new class and registerd on its own.

    Change-Id: I8c4b48a492a0088a6dcdf8de82313bee8185ec54

seems like this would affect everyone - no? Has something gone wrong with my source tree?

ta

JB


--
John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
http://www.cscs.ch/
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150119/4df07e90/attachment-0001.html>

From yumin.yuan at kitware.com  Mon Jan 19 07:53:26 2015
From: yumin.yuan at kitware.com (Yumin Yuan)
Date: Mon, 19 Jan 2015 07:53:26 -0500
Subject: [Paraview-developers] 4.3 build error
In-Reply-To: <50320452A334BD42A5EC72BAD21450991E5B8A06@MBX210.d.ethz.ch>
References: <50320452A334BD42A5EC72BAD21450991E5B8A06@MBX210.d.ethz.ch>
Message-ID: <CAKkFzuemtsetQBRrnGtGYOKS3Tb-15-1Rrg5ssA55OC-Jg3HXQ@mail.gmail.com>

Hi John,

The qttesting submodule in paraview was updated to bring in fixes. I assume
you did not do "git submodule update" ?

Yumin

On Mon, Jan 19, 2015 at 5:28 AM, Biddiscombe, John A. <biddisco at cscs.ch>
wrote:

>  I upgraded my source tree to 4.3 and got this build error
>
>
>
> Error      12504    error C2039: 'getWidgetEventPlayer' : is not a member
> of 'pqEventPlayer'            pqApplicationComponents
> D:\Code\ParaView\Qt\ApplicationComponents\pqParaViewBehaviors.cxx
> 106
>
>
>
> I poked around and couldn?t see an easy way to fix it.  The offending code
> introduced in commit 3f6e30bb324a343acf345abe8fe98176813a7eeb
>
> commit 3f6e30bb324a343acf345abe8fe98176813a7eeb
>
> Author: Yumin Yuan <yumin.yuan at kitware.com>
>
> Date:   Tue Dec 2 10:44:50 2014 -0500
>
>
>
>     Separated out EventPlayer from pqViewStreamingBehavior
>
>
>
>     The pqViewStreamingBehavior contains and instantiates its own event
>
>     player to play back its recorded event. The new QtTesting flow does
>
>     not support this. The players have to be registered first before
>
>     recorded event can be dispatched to the player. So the internal
>
>     event class is moved out to be a new class and registerd on its own.
>
>
>
>     Change-Id: I8c4b48a492a0088a6dcdf8de82313bee8185ec54
>
>
>
> seems like this would affect everyone - no? Has something gone wrong with
> my source tree?
>
>
>
> ta
>
>
>
> JB
>
>
>
>
>
> --
>
> John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
>
> http://www.cscs.ch/
>
> CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
>
> Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150119/6cd91a44/attachment.html>

From biddisco at cscs.ch  Mon Jan 19 08:25:46 2015
From: biddisco at cscs.ch (Biddiscombe, John A.)
Date: Mon, 19 Jan 2015 13:25:46 +0000
Subject: [Paraview-developers] 4.3 build error
In-Reply-To: <CAKkFzuemtsetQBRrnGtGYOKS3Tb-15-1Rrg5ssA55OC-Jg3HXQ@mail.gmail.com>
References: <50320452A334BD42A5EC72BAD21450991E5B8A06@MBX210.d.ethz.ch>
 <CAKkFzuemtsetQBRrnGtGYOKS3Tb-15-1Rrg5ssA55OC-Jg3HXQ@mail.gmail.com>
Message-ID: <50320452A334BD42A5EC72BAD21450991E5B90F6@MBX210.d.ethz.ch>

Yumin

>>The qttesting submodule in paraview was updated to bring in fixes. I assume you did not do "git submodule update" ?

aaarrghh! Sorry, completely forgot about that stuff. I always do the vtk submodule manually to rebase my patches onto it and forgot completely about the other ones.

It?s compiling now...

cheers and apologies for the time wasting.

JB


On Mon, Jan 19, 2015 at 5:28 AM, Biddiscombe, John A. <biddisco at cscs.ch<mailto:biddisco at cscs.ch>> wrote:
I upgraded my source tree to 4.3 and got this build error

Error      12504    error C2039: 'getWidgetEventPlayer' : is not a member of 'pqEventPlayer'            pqApplicationComponents                D:\Code\ParaView\Qt\ApplicationComponents\pqParaViewBehaviors.cxx         106

I poked around and couldn?t see an easy way to fix it.  The offending code introduced in commit 3f6e30bb324a343acf345abe8fe98176813a7eeb
commit 3f6e30bb324a343acf345abe8fe98176813a7eeb
Author: Yumin Yuan <yumin.yuan at kitware.com<mailto:yumin.yuan at kitware.com>>
Date:   Tue Dec 2 10:44:50 2014 -0500

    Separated out EventPlayer from pqViewStreamingBehavior

    The pqViewStreamingBehavior contains and instantiates its own event
    player to play back its recorded event. The new QtTesting flow does
    not support this. The players have to be registered first before
    recorded event can be dispatched to the player. So the internal
    event class is moved out to be a new class and registerd on its own.

    Change-Id: I8c4b48a492a0088a6dcdf8de82313bee8185ec54

seems like this would affect everyone - no? Has something gone wrong with my source tree?

ta

JB


--
John Biddiscombe,                        email:biddisco @.at.@ cscs.ch<http://cscs.ch>
http://www.cscs.ch/
CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07<tel:%2B41%20%2891%29%20610.82.07>
Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82<tel:%2B41%20%2891%29%20610.82.82>


_______________________________________________
Powered by www.kitware.com<http://www.kitware.com>

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

Search the list archives at: http://markmail.org/search/?q=Paraview-developers

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview-developers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150119/fdf7fa72/attachment.html>

From yumin.yuan at kitware.com  Mon Jan 19 08:41:56 2015
From: yumin.yuan at kitware.com (Yumin Yuan)
Date: Mon, 19 Jan 2015 08:41:56 -0500
Subject: [Paraview-developers] 4.3 build error
In-Reply-To: <50320452A334BD42A5EC72BAD21450991E5B90F6@MBX210.d.ethz.ch>
References: <50320452A334BD42A5EC72BAD21450991E5B8A06@MBX210.d.ethz.ch>
 <CAKkFzuemtsetQBRrnGtGYOKS3Tb-15-1Rrg5ssA55OC-Jg3HXQ@mail.gmail.com>
 <50320452A334BD42A5EC72BAD21450991E5B90F6@MBX210.d.ethz.ch>
Message-ID: <CAKkFzuc7seDWWO5a125k_EX9UXh81JSuPLWqx0r=rySx--Xvww@mail.gmail.com>

No worries. It happens to many of us sometimes :)

On Mon, Jan 19, 2015 at 8:25 AM, Biddiscombe, John A. <biddisco at cscs.ch>
wrote:

>  Yumin
>
>
>
> >>The qttesting submodule in paraview was updated to bring in fixes. I
> assume you did not do "git submodule update" ?
>
>
>
> aaarrghh! Sorry, completely forgot about that stuff. I always do the vtk
> submodule manually to rebase my patches onto it and forgot completely about
> the other ones.
>
>
>
> It?s compiling now...
>
>
>
> cheers and apologies for the time wasting.
>
>
>
> JB
>
>
>
>
>
> On Mon, Jan 19, 2015 at 5:28 AM, Biddiscombe, John A. <biddisco at cscs.ch>
> wrote:
>
> I upgraded my source tree to 4.3 and got this build error
>
>
>
> Error      12504    error C2039: 'getWidgetEventPlayer' : is not a member
> of 'pqEventPlayer'            pqApplicationComponents
> D:\Code\ParaView\Qt\ApplicationComponents\pqParaViewBehaviors.cxx
> 106
>
>
>
> I poked around and couldn?t see an easy way to fix it.  The offending code
> introduced in commit 3f6e30bb324a343acf345abe8fe98176813a7eeb
>
> commit 3f6e30bb324a343acf345abe8fe98176813a7eeb
>
> Author: Yumin Yuan <yumin.yuan at kitware.com>
>
> Date:   Tue Dec 2 10:44:50 2014 -0500
>
>
>
>     Separated out EventPlayer from pqViewStreamingBehavior
>
>
>
>     The pqViewStreamingBehavior contains and instantiates its own event
>
>     player to play back its recorded event. The new QtTesting flow does
>
>     not support this. The players have to be registered first before
>
>     recorded event can be dispatched to the player. So the internal
>
>     event class is moved out to be a new class and registerd on its own.
>
>
>
>     Change-Id: I8c4b48a492a0088a6dcdf8de82313bee8185ec54
>
>
>
> seems like this would affect everyone - no? Has something gone wrong with
> my source tree?
>
>
>
> ta
>
>
>
> JB
>
>
>
>
>
> --
>
> John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
>
> http://www.cscs.ch/
>
> CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
>
> Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150119/7c844359/attachment-0001.html>

From dan.lipsa at kitware.com  Mon Jan 19 11:42:46 2015
From: dan.lipsa at kitware.com (Dan Lipsa)
Date: Mon, 19 Jan 2015 11:42:46 -0500
Subject: [Paraview-developers] Output Window Redesign
Message-ID: <CADwGrVrYmyV3ZpyWzg_EwxbvqqSGHZ022XmmQBdgfwQSO-JHMw@mail.gmail.com>

Hi all,
We are redesigning the output window for ParaView and we would like your
feedback.
Here is (roughly) how we see the new output window.

http://www.paraview.org/Wiki/Output_Messages_Window

Thanks,
Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150119/ee13987b/attachment.html>

From joachim.pouderoux at kitware.com  Mon Jan 19 11:42:42 2015
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Mon, 19 Jan 2015 17:42:42 +0100
Subject: [Paraview-developers] ANN: VTK and ParaView Training Courses in
 Lyon, France, February 3-4, 2015
In-Reply-To: <CACJ=gTiFThZUg1Td6T=ph=j=FMQ_8g3g4c67U9RAkOebwUK11A@mail.gmail.com>
References: <CACJ=gTiFThZUg1Td6T=ph=j=FMQ_8g3g4c67U9RAkOebwUK11A@mail.gmail.com>
Message-ID: <CACJ=gTihO9CE-6gJ1e-WfhckKRgw4wDvwwKWWqN7fGbGBJvQZQ@mail.gmail.com>

Errata: the previous links were bad, here are the correct one:

http://training.kitware.fr/browse/83
http://training.kitware.fr/browse/84
or in French:
http://formations.kitware.fr/browse/83
http://formations.kitware.fr/browse/84

Best regards,


*Joachim Pouderoux*

*PhD, Technical Expert*
*Kitware SAS <http://www.kitware.fr>*


2015-01-16 14:04 GMT+01:00 Joachim Pouderoux <joachim.pouderoux at kitware.com>
:

> Kitware will be holding VTK and ParaView courses on February 3-4,
> 2015 in Lyon, France.
>
> Please visit our web site for more information and registration details at
> either:
>
> http://training.kitware.fr/browse/83
> <http://training.kitware.fr/browse/48>
> http://training.kitware.fr/browse/84
> <http://training.kitware.fr/browse/48>
> or in French:
> http://formations.kitware.fr/browse/83
> <http://formations.kitware.fr/browse/48>
> http://formations.kitware.fr/browse/84
> <http://formations.kitware.fr/browse/48>
>
> Note that the course will be taught in English. If you have any question,
> please contact us at formations at http://www.kitware.fr
>
> Thank you,
>
> *Joachim Pouderoux*
>
> *PhD, Technical Expert*
> *Kitware SAS <http://www.kitware.fr>*
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150119/56f1c78e/attachment.html>

From cory.quammen at kitware.com  Mon Jan 19 12:03:50 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Mon, 19 Jan 2015 12:03:50 -0500
Subject: [Paraview-developers] Output Window Redesign
In-Reply-To: <CADwGrVrYmyV3ZpyWzg_EwxbvqqSGHZ022XmmQBdgfwQSO-JHMw@mail.gmail.com>
References: <CADwGrVrYmyV3ZpyWzg_EwxbvqqSGHZ022XmmQBdgfwQSO-JHMw@mail.gmail.com>
Message-ID: <CAB5Fpx4JH_MGyH1Q5TcNwq33FxumqEcx0xKRw_175bPLe_2sHQ@mail.gmail.com>

Dan,

This looks really nice. FYI, Slicer has a nice error message interface
that is similar to what you have devised. It also includes the
data/time of the message and the source, e.g., Qt, VTK, ParaView, etc,
as a column as well as a column showing the severity of the error. It
might be nice to include those.

Also, maybe instead of a separate Details column, have a plus/minus
sign to show the long/short message.

Thanks,
Cory

On Mon, Jan 19, 2015 at 11:42 AM, Dan Lipsa <dan.lipsa at kitware.com> wrote:
> Hi all,
> We are redesigning the output window for ParaView and we would like your
> feedback.
> Here is (roughly) how we see the new output window.
>
> http://www.paraview.org/Wiki/Output_Messages_Window
>
> Thanks,
> Dan
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.

From kmorel at sandia.gov  Mon Jan 19 12:36:50 2015
From: kmorel at sandia.gov (Moreland, Kenneth)
Date: Mon, 19 Jan 2015 17:36:50 +0000
Subject: [Paraview-developers] Output Window Redesign
Message-ID: <D0E28734.1FD34%kmorel@sandia.gov>

This looks like a much better design. Here are some further suggestions.

  *   I am worried that only combining messages that are reported one after another (with no error in between) will not be aggressive enough. A lot of errant events span two or more error messages, and these messages may be in a loop. You won't catch the duplicates if you are only looking for similar errors spawned one after the other. Perhaps the output window can listen to the undo/redo stack and combine all similar messages issued between events in the undo/redo stack.
  *   The filter mechanism does not make much sense to me. It's too complicated, too different from every other application I've ever used, and doesn't seem to have much value. My recommendation is on the first pass to simply not implement any filtering. Once the verbosity improvements are made, I expect the output list to be short enough to be not worthwhile to filter. If you do want to implement filtering, I would change the "Filter All" pulldown menu with a simple toggle button that turns warning and debug message on and off. I would change the right-click functionality with a line edit widget that, when text was typed in, to show only messages that match the given text.
  *   There should be a way to easily export errors to text with details so users can post them to the mailing list. One or more of the following should be available: select rows of the table and copy-paste to text; have a text view that shows the output in the old text verbosity; have an export button that saves the errors to a file.

-Ken

From: Dan Lipsa <dan.lipsa at kitware.com<mailto:dan.lipsa at kitware.com>>
Date: Monday, January 19, 2015 at 9:42 AM
To: ParaView Developers List <paraview-developers at paraview.org<mailto:paraview-developers at paraview.org>>
Subject: [EXTERNAL] [Paraview-developers] Output Window Redesign

Hi all,
We are redesigning the output window for ParaView and we would like your feedback.
Here is (roughly) how we see the new output window.

http://www.paraview.org/Wiki/Output_Messages_Window

Thanks,
Dan


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150119/da7fb8a4/attachment.html>

From wascott at sandia.gov  Mon Jan 19 13:13:23 2015
From: wascott at sandia.gov (Scott, W Alan)
Date: Mon, 19 Jan 2015 18:13:23 +0000
Subject: [Paraview-developers] [EXTERNAL] Re:  Output Window Redesign
In-Reply-To: <D0E28734.1FD34%kmorel@sandia.gov>
References: <D0E28734.1FD34%kmorel@sandia.gov>
Message-ID: <cbfa62930870436ebc0706c53a3539ff@ES05AMSNLNT.srn.sandia.gov>

I also like the design proposed.  Also, the ability to combine messages will be a godsend, and is exactly what we need.

Regarding Kens comments below, I wouldn't change one word.  Perfect.  Especially regarding his first bullet.

Alan

From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Moreland, Kenneth
Sent: Monday, January 19, 2015 10:37 AM
To: Dan Lipsa; ParaView Developers List
Subject: [EXTERNAL] Re: [Paraview-developers] Output Window Redesign

This looks like a much better design. Here are some further suggestions.
*         I am worried that only combining messages that are reported one after another (with no error in between) will not be aggressive enough. A lot of errant events span two or more error messages, and these messages may be in a loop. You won't catch the duplicates if you are only looking for similar errors spawned one after the other. Perhaps the output window can listen to the undo/redo stack and combine all similar messages issued between events in the undo/redo stack.
*         The filter mechanism does not make much sense to me. It's too complicated, too different from every other application I've ever used, and doesn't seem to have much value. My recommendation is on the first pass to simply not implement any filtering. Once the verbosity improvements are made, I expect the output list to be short enough to be not worthwhile to filter. If you do want to implement filtering, I would change the "Filter All" pulldown menu with a simple toggle button that turns warning and debug message on and off. I would change the right-click functionality with a line edit widget that, when text was typed in, to show only messages that match the given text.
*         There should be a way to easily export errors to text with details so users can post them to the mailing list. One or more of the following should be available: select rows of the table and copy-paste to text; have a text view that shows the output in the old text verbosity; have an export button that saves the errors to a file.
-Ken

From: Dan Lipsa <dan.lipsa at kitware.com<mailto:dan.lipsa at kitware.com>>
Date: Monday, January 19, 2015 at 9:42 AM
To: ParaView Developers List <paraview-developers at paraview.org<mailto:paraview-developers at paraview.org>>
Subject: [EXTERNAL] [Paraview-developers] Output Window Redesign

Hi all,
We are redesigning the output window for ParaView and we would like your feedback.
Here is (roughly) how we see the new output window.

http://www.paraview.org/Wiki/Output_Messages_Window

Thanks,
Dan


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150119/d5b097ab/attachment-0001.html>

From felipe.bordeu at ec-nantes.fr  Tue Jan 20 03:34:11 2015
From: felipe.bordeu at ec-nantes.fr (Felipe Bordeu)
Date: Tue, 20 Jan 2015 09:34:11 +0100
Subject: [Paraview-developers] [EXTERNAL] Re:  Output Window Redesign
In-Reply-To: <cbfa62930870436ebc0706c53a3539ff@ES05AMSNLNT.srn.sandia.gov>
References: <D0E28734.1FD34%kmorel@sandia.gov>
 <cbfa62930870436ebc0706c53a3539ff@ES05AMSNLNT.srn.sandia.gov>
Message-ID: <54BE1303.6050804@ec-nantes.fr>


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

it is possible to have a dockable panel? And if you hide the panel and
new messages are printed a warning icon will blink in the corner of the
main window of paraview.

see attached image.

Felipe

Le 19/01/2015 19:13, Scott, W Alan a ?crit :
>
> I also like the design proposed.  Also, the ability to combine
messages will be a godsend, and is exactly what we need.
>
> 
>
> Regarding Kens comments below, I wouldn?t change one word.  Perfect. 
Especially regarding his first bullet.
>
> 
>
> Alan
>
> 
>
> *From:*Paraview-developers
[mailto:paraview-developers-bounces at paraview.org] *On Behalf Of
*Moreland, Kenneth
> *Sent:* Monday, January 19, 2015 10:37 AM
> *To:* Dan Lipsa; ParaView Developers List
> *Subject:* [EXTERNAL] Re: [Paraview-developers] Output Window Redesign
>
> 
>
> This looks like a much better design. Here are some further suggestions.
>
> ?         I am worried that only combining messages that are reported
one after another (with no error in between) will not be aggressive
enough. A lot of errant events span two or more error messages, and
these messages may be in a loop. You won't catch the duplicates if you
are only looking for similar errors spawned one after the other. Perhaps
the output window can listen to the undo/redo stack and combine all
similar messages issued between events in the undo/redo stack.
>
> ?         The filter mechanism does not make much sense to me. It's
too complicated, too different from every other application I've ever
used, and doesn't seem to have much value. My recommendation is on the
first pass to simply not implement any filtering. Once the verbosity
improvements are made, I expect the output list to be short enough to be
not worthwhile to filter. If you do want to implement filtering, I would
change the "Filter All" pulldown menu with a simple toggle button that
turns warning and debug message on and off. I would change the
right-click functionality with a line edit widget that, when text was
typed in, to show only messages that match the given text.
>
> ?         There should be a way to easily export errors to text with
details so users can post them to the mailing list. One or more of the
following should be available: select rows of the table and copy-paste
to text; have a text view that shows the output in the old text
verbosity; have an export button that saves the errors to a file.
>
> -Ken
>
> 
>
> *From: *Dan Lipsa <dan.lipsa at kitware.com <mailto:dan.lipsa at kitware.com>>
> *Date: *Monday, January 19, 2015 at 9:42 AM
> *To: *ParaView Developers List <paraview-developers at paraview.org
<mailto:paraview-developers at paraview.org>>
> *Subject: *[EXTERNAL] [Paraview-developers] Output Window Redesign
>
> 
>
> Hi all,
>
> We are redesigning the output window for ParaView and we would like
your feedback.
>
> Here is (roughly) how we see the new output window.
>
> 
>
> http://www.paraview.org/Wiki/Output_Messages_Window
>
> 
>
> Thanks,
>
> Dan
>
> 
>
> 
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers


- -- 
Felipe Bordeu Weldt
Ing?nieur de Recherche
- -------------------------------------
T?l. : 33 (0)2 40 37 16 57
Fax. : 33 (0)2 40 74 74 06
Felipe.Bordeu at ec-nantes.fr
Institut GeM - UMR CNRS 6183
?cole Centrale Nantes
1 Rue de La No?, 44321 Nantes, FRANCE
- -------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUvhL+AAoJEE/fMfNgU9/D0CcIAKS3VcLDrr0T7UyDnbWYhElx
6Ey2yywjzUJC+htgmTNUxbKVdzuHrGuG6Tya7DVNWZdE0ofjS18cEgR7vI8/JJfd
EwQIbKl/qKKQbiPKNXW/BBB+bI4XJrlfgys2+cAv4jXSisBA2QeAtNxaNI27Abxs
hqIbDxe1G9bEhqze6L+BtKDRU+ojoFmlRktvhHUPSVjrH3PnSlJgEr+3Y0n6C5zu
3Y0pOVkJQe03Qsstc9Qs9qWATPY1GFMsl80c7XHGBU13Ak9xweb9JAdjdA+G7ojr
qRKUQ/MQZ/4WY2/BZOaJvzo6RIalDkHMtVssSc5+zdr4hWUeRO1giKFQTZtJnrc=
=7Frd
-----END PGP SIGNATURE-----

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150120/0462f8d3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OM.png
Type: image/png
Size: 8720 bytes
Desc: not available
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150120/0462f8d3/attachment.png>

From andy.bauer at kitware.com  Tue Jan 20 15:21:14 2015
From: andy.bauer at kitware.com (Andy Bauer)
Date: Tue, 20 Jan 2015 15:21:14 -0500
Subject: [Paraview-developers] [EXTERNAL] Re: Output Window Redesign
In-Reply-To: <54BE1303.6050804@ec-nantes.fr>
References: <D0E28734.1FD34%kmorel@sandia.gov>
 <cbfa62930870436ebc0706c53a3539ff@ES05AMSNLNT.srn.sandia.gov>
 <54BE1303.6050804@ec-nantes.fr>
Message-ID: <CAMaOp+GQZmhjZ+OT-MRDMh8RYvPMC7Bm+kR0vt7Z_OSVJdp4ug@mail.gmail.com>

Maybe not exactly related but it could be affected by the change -- this is
also the output window for Python information as well. For things like the
Programmable Filter I like seeing the outputted print statements from there
and would hate to see this not handled well in the new output window gui.
Other than that though this would be a nice improvement.

On Tue, Jan 20, 2015 at 3:34 AM, Felipe Bordeu <felipe.bordeu at ec-nantes.fr>
wrote:

>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> it is possible to have a dockable panel? And if you hide the panel and new
> messages are printed a warning icon will blink in the corner of the main
> window of paraview.
>
> see attached image.
>
> Felipe
>
> Le 19/01/2015 19:13, Scott, W Alan a ?crit :
> >
> > I also like the design proposed.  Also, the ability to combine messages
> will be a godsend, and is exactly what we need.
> >
> >
> >
> > Regarding Kens comments below, I wouldn?t change one word.  Perfect.
> Especially regarding his first bullet.
> >
> >
> >
> > Alan
> >
> >
> >
> > *From:*Paraview-developers [
> mailto:paraview-developers-bounces at paraview.org
> <paraview-developers-bounces at paraview.org>] *On Behalf Of *Moreland,
> Kenneth
> > *Sent:* Monday, January 19, 2015 10:37 AM
> > *To:* Dan Lipsa; ParaView Developers List
> > *Subject:* [EXTERNAL] Re: [Paraview-developers] Output Window Redesign
> >
> >
> >
> > This looks like a much better design. Here are some further suggestions.
> >
> > ?         I am worried that only combining messages that are reported
> one after another (with no error in between) will not be aggressive enough.
> A lot of errant events span two or more error messages, and these messages
> may be in a loop. You won't catch the duplicates if you are only looking
> for similar errors spawned one after the other. Perhaps the output window
> can listen to the undo/redo stack and combine all similar messages issued
> between events in the undo/redo stack.
> >
> > ?         The filter mechanism does not make much sense to me. It's too
> complicated, too different from every other application I've ever used, and
> doesn't seem to have much value. My recommendation is on the first pass to
> simply not implement any filtering. Once the verbosity improvements are
> made, I expect the output list to be short enough to be not worthwhile to
> filter. If you do want to implement filtering, I would change the "Filter
> All" pulldown menu with a simple toggle button that turns warning and debug
> message on and off. I would change the right-click functionality with a
> line edit widget that, when text was typed in, to show only messages that
> match the given text.
> >
> > ?         There should be a way to easily export errors to text with
> details so users can post them to the mailing list. One or more of the
> following should be available: select rows of the table and copy-paste to
> text; have a text view that shows the output in the old text verbosity;
> have an export button that saves the errors to a file.
> >
> > -Ken
> >
> >
> >
> > *From: *Dan Lipsa <dan.lipsa at kitware.com <mailto:dan.lipsa at kitware.com>
> <dan.lipsa at kitware.com>>
> > *Date: *Monday, January 19, 2015 at 9:42 AM
> > *To: *ParaView Developers List <paraview-developers at paraview.org
> <mailto:paraview-developers at paraview.org>
> <paraview-developers at paraview.org>>
> > *Subject: *[EXTERNAL] [Paraview-developers] Output Window Redesign
> >
> >
> >
> > Hi all,
> >
> > We are redesigning the output window for ParaView and we would like your
> feedback.
> >
> > Here is (roughly) how we see the new output window.
> >
> >
> >
> > http://www.paraview.org/Wiki/Output_Messages_Window
> >
> >
> >
> > Thanks,
> >
> > Dan
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
> >
> > Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
> - --
> Felipe Bordeu Weldt
> Ing?nieur de Recherche
> - -------------------------------------
> T?l. : 33 (0)2 40 37 16 57
> Fax. : 33 (0)2 40 74 74 06
> Felipe.Bordeu at ec-nantes.fr
> Institut GeM - UMR CNRS 6183
> ?cole Centrale Nantes
> 1 Rue de La No?, 44321 Nantes, FRANCE
> - -------------------------------------
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBAgAGBQJUvhL+AAoJEE/fMfNgU9/D0CcIAKS3VcLDrr0T7UyDnbWYhElx
> 6Ey2yywjzUJC+htgmTNUxbKVdzuHrGuG6Tya7DVNWZdE0ofjS18cEgR7vI8/JJfd
> EwQIbKl/qKKQbiPKNXW/BBB+bI4XJrlfgys2+cAv4jXSisBA2QeAtNxaNI27Abxs
> hqIbDxe1G9bEhqze6L+BtKDRU+ojoFmlRktvhHUPSVjrH3PnSlJgEr+3Y0n6C5zu
> 3Y0pOVkJQe03Qsstc9Qs9qWATPY1GFMsl80c7XHGBU13Ak9xweb9JAdjdA+G7ojr
> qRKUQ/MQZ/4WY2/BZOaJvzo6RIalDkHMtVssSc5+zdr4hWUeRO1giKFQTZtJnrc=
> =7Frd
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150120/5b4c8648/attachment-0001.html>

From utkarsh.ayachit at kitware.com  Tue Jan 20 16:17:16 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 20 Jan 2015 16:17:16 -0500
Subject: [Paraview-developers] ANN: ParaView 4.3.1 is available for download
Message-ID: <CADHSJjA+pfqoJM5NbvCcTWXWiMEh4MqLiWdYSrHHZ8zEdYcmkw@mail.gmail.com>

Folks,

ParaView 4.3.1 is now available for download. Checkout the release
notes on the Kitware blog [1].

As always, we look forward to your feedback [2].

Also stay tuned to the Kitware Blog [3] for upcoming features and
enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
more!

- The ParaView team

[1] http://www.kitware.com/blog/posts/view/825
[2] http://paraview.uservoice.com
[3] http://www.kitware.com/blog/

From furutaka.kazuyoshi at jaea.go.jp  Wed Jan 21 02:38:06 2015
From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka)
Date: Wed, 21 Jan 2015 16:38:06 +0900 (JST)
Subject: [Paraview-developers] [Paraview] ANN: ParaView 4.3.1 is
	available for download
In-Reply-To: <CADHSJjA+pfqoJM5NbvCcTWXWiMEh4MqLiWdYSrHHZ8zEdYcmkw@mail.gmail.com>
References: <CADHSJjA+pfqoJM5NbvCcTWXWiMEh4MqLiWdYSrHHZ8zEdYcmkw@mail.gmail.com>
Message-ID: <20150121.163806.74547358.furutaka.kazuyoshi@jaea.go.jp>

Hello,

The build from source (git branch v4.3.1) failed 
on my linux machine (Fedora-21, i686);

[ 84%] Building CXX object ParaViewCore/ClientServerCore/Rendering/CMakeFiles/vtkPVClientServerCoreRendering.dir/vtkGeometrySliceRepresentation.cxx.o
/home/furutaka/work/ParaView/ParaView.git/ParaViewCore/ClientServerCore/Rendering/vtkGeometryRepresentation.cxx: In member function ?virtual void vtkGeometryRepresentation::UpdateColoringParameters()?:
/home/furutaka/work/ParaView/ParaView.git/ParaViewCore/ClientServerCore/Rendering/vtkGeometryRepresentation.cxx:579:23: error: ?class vtkMapper? has no member named ?SetFieldDataTupleId?
         this->Mapper->SetFieldDataTupleId(0);
                       ^
/home/furutaka/work/ParaView/ParaView.git/ParaViewCore/ClientServerCore/Rendering/vtkGeometryRepresentation.cxx:581:26: error: ?class vtkMapper? has no member named ?SetFieldDataTupleId?
         this->LODMapper->SetFieldDataTupleId(0);
                          ^
/home/furutaka/work/ParaView/ParaView.git/ParaViewCore/ClientServerCore/Rendering/vtkGeometryRepresentation.cxx: In member function ?virtual void vtkGeometryRepresentation::SetMapScalars(int)?:
/home/furutaka/work/ParaView/ParaView.git/ParaViewCore/ClientServerCore/Rendering/vtkGeometryRepresentation.cxx:681:5: error: ?VTK_COLOR_MODE_DIRECT_SCALARS? was not declared in this scope
     VTK_COLOR_MODE_DIRECT_SCALARS,
     ^
ParaViewCore/ClientServerCore/Rendering/CMakeFiles/vtkPVClientServerCoreRendering.dir/build.make:330: recipe for target 'ParaViewCore/ClientServerCore/Rendering/CMakeFiles/vtkPVClientServerCoreRendering.dir/vtkGeometryRepresentation.cxx.o' failed
make[2]: *** [ParaViewCore/ClientServerCore/Rendering/CMakeFiles/vtkPVClientServerCoreRendering.dir/vtkGeometryRepresentation.cxx.o] Error 1
make[2]: *** Waiting for unfinished jobs....


Kazuyoshi


From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
Subject: [Paraview] ANN: ParaView 4.3.1 is available for download
Date: Tue, 20 Jan 2015 16:17:16 -0500

> Folks,
> 
> ParaView 4.3.1 is now available for download. Checkout the release
> notes on the Kitware blog [1].
> 
> As always, we look forward to your feedback [2].
> 
> Also stay tuned to the Kitware Blog [3] for upcoming features and
> enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
> more!
> 
> - The ParaView team
> 
> [1] http://www.kitware.com/blog/posts/view/825
> [2] http://paraview.uservoice.com
> [3] http://www.kitware.com/blog/
> _______________________________________________
> 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
> 
> Search the list archives at: http://markmail.org/search/?q=ParaView
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
--
Kazuyoshi Furutaka
furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp

From cory.quammen at kitware.com  Wed Jan 21 09:32:37 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 21 Jan 2015 09:32:37 -0500
Subject: [Paraview-developers] [Paraview] ANN: ParaView 4.3.1 is
	available for download
In-Reply-To: <20150121.163806.74547358.furutaka.kazuyoshi@jaea.go.jp>
References: <CADHSJjA+pfqoJM5NbvCcTWXWiMEh4MqLiWdYSrHHZ8zEdYcmkw@mail.gmail.com>
 <20150121.163806.74547358.furutaka.kazuyoshi@jaea.go.jp>
Message-ID: <CAB5Fpx7gs9sVd52SUS=fWO7ycGBWF3q39H9e6CzfyPYjVJgEsA@mail.gmail.com>

Hi Kazuyoshi,

Did you update the ParaView submodules?

Try running

git submodule update --init

from within the ParaView source directory and compile again.

Hope that helps,
Cory

On Wed, Jan 21, 2015 at 2:38 AM, Kazuyoshi Furutaka <
furutaka.kazuyoshi at jaea.go.jp> wrote:

> Hello,
>
> The build from source (git branch v4.3.1) failed
> on my linux machine (Fedora-21, i686);
>
> [ 84%] Building CXX object
> ParaViewCore/ClientServerCore/Rendering/CMakeFiles/vtkPVClientServerCoreRendering.dir/vtkGeometrySliceRepresentation.cxx.o
> /home/furutaka/work/ParaView/ParaView.git/ParaViewCore/ClientServerCore/Rendering/vtkGeometryRepresentation.cxx:
> In member function ?virtual void
> vtkGeometryRepresentation::UpdateColoringParameters()?:
> /home/furutaka/work/ParaView/ParaView.git/ParaViewCore/ClientServerCore/Rendering/vtkGeometryRepresentation.cxx:579:23:
> error: ?class vtkMapper? has no member named ?SetFieldDataTupleId?
>          this->Mapper->SetFieldDataTupleId(0);
>                        ^
> /home/furutaka/work/ParaView/ParaView.git/ParaViewCore/ClientServerCore/Rendering/vtkGeometryRepresentation.cxx:581:26:
> error: ?class vtkMapper? has no member named ?SetFieldDataTupleId?
>          this->LODMapper->SetFieldDataTupleId(0);
>                           ^
> /home/furutaka/work/ParaView/ParaView.git/ParaViewCore/ClientServerCore/Rendering/vtkGeometryRepresentation.cxx:
> In member function ?virtual void
> vtkGeometryRepresentation::SetMapScalars(int)?:
> /home/furutaka/work/ParaView/ParaView.git/ParaViewCore/ClientServerCore/Rendering/vtkGeometryRepresentation.cxx:681:5:
> error: ?VTK_COLOR_MODE_DIRECT_SCALARS? was not declared in this scope
>      VTK_COLOR_MODE_DIRECT_SCALARS,
>      ^
> ParaViewCore/ClientServerCore/Rendering/CMakeFiles/vtkPVClientServerCoreRendering.dir/build.make:330:
> recipe for target
> 'ParaViewCore/ClientServerCore/Rendering/CMakeFiles/vtkPVClientServerCoreRendering.dir/vtkGeometryRepresentation.cxx.o'
> failed
> make[2]: ***
> [ParaViewCore/ClientServerCore/Rendering/CMakeFiles/vtkPVClientServerCoreRendering.dir/vtkGeometryRepresentation.cxx.o]
> Error 1
> make[2]: *** Waiting for unfinished jobs....
>
>
> Kazuyoshi
>
>
> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Subject: [Paraview] ANN: ParaView 4.3.1 is available for download
> Date: Tue, 20 Jan 2015 16:17:16 -0500
>
> > Folks,
> >
> > ParaView 4.3.1 is now available for download. Checkout the release
> > notes on the Kitware blog [1].
> >
> > As always, we look forward to your feedback [2].
> >
> > Also stay tuned to the Kitware Blog [3] for upcoming features and
> > enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
> > more!
> >
> > - The ParaView team
> >
> > [1] http://www.kitware.com/blog/posts/view/825
> > [2] http://paraview.uservoice.com
> > [3] http://www.kitware.com/blog/
> > _______________________________________________
> > 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
> >
> > Search the list archives at: http://markmail.org/search/?q=ParaView
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview
> --
> Kazuyoshi Furutaka
> furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp
> _______________________________________________
> 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
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150121/efda5f7b/attachment.html>

From utkarsh.ayachit at kitware.com  Wed Jan 21 11:45:53 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 21 Jan 2015 11:45:53 -0500
Subject: [Paraview-developers] [Paraview] ANN: ParaView 4.3.1 is
	available for download
In-Reply-To: <D0E53FA4.1FD72%Richard.C.Angelini.CIV@mail.mil>
References: <CADHSJjA+pfqoJM5NbvCcTWXWiMEh4MqLiWdYSrHHZ8zEdYcmkw@mail.gmail.com>
 <D0E53FA4.1FD72%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CADHSJjAjQFku-TqfcwbtAvsAsWxF=L7cCVehs5QdfsrFMQ-rxQ@mail.gmail.com>

What are the errors you're getting? What cmake version are you using?
Dan, did the fix for hdf5 with cmake version get merged in time for
4.3.1?

On Wed, Jan 21, 2015 at 11:36 AM, Angelini, Richard C (Rick) CIV
USARMY ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> I?m having trouble building 4.3.1 on several systems where 4.2 built without
> issue.  Is there a particular version of cmake that 4.3.1 needs to be built
> with?
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Date: Tuesday, January 20, 2015 at 4:17 PM
> To: ParaView <paraview at paraview.org>, ParaView Developers
> <paraview-developers at paraview.org>
> Subject: [Paraview] ANN: ParaView 4.3.1 is available for download
>
> Folks,
>
> ParaView 4.3.1 is now available for download. Checkout the release
> notes on the Kitware blog [1].
>
> As always, we look forward to your feedback [2].
>
> Also stay tuned to the Kitware Blog [3] for upcoming features and
> enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
> more!
>
> - The ParaView team
>
> [1] http://www.kitware.com/blog/posts/view/825
> [2] http://paraview.uservoice.com
> [3] http://www.kitware.com/blog/
> _______________________________________________
> 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
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From utkarsh.ayachit at kitware.com  Wed Jan 21 12:39:25 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Wed, 21 Jan 2015 12:39:25 -0500
Subject: [Paraview-developers] [Paraview] ANN: ParaView 4.3.1 is
	available for download
In-Reply-To: <D0E54688.1FD81%Richard.C.Angelini.CIV@mail.mil>
References: <CADHSJjA+pfqoJM5NbvCcTWXWiMEh4MqLiWdYSrHHZ8zEdYcmkw@mail.gmail.com>
 <D0E53FA4.1FD72%Richard.C.Angelini.CIV@mail.mil>
 <D0E54688.1FD81%Richard.C.Angelini.CIV@mail.mil>
Message-ID: <CADHSJjBtUN05DLru00H-E_rYxe7MFxQd9pjNqPwCnkM=mvFTqw@mail.gmail.com>

Rick,

Can you try using the "release" branch on the Superbuild repo (or the
v4.3.1 tag)? There have been quite  few changes merged into git/master
of the repo since which may be causing these issues.

Utkarsh

On Wed, Jan 21, 2015 at 12:08 PM, Angelini, Richard C (Rick) CIV
USARMY ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> I was using cmake-2.8.11 and I upgraded to cmake-3.1.0, but I?m still seeing
> errors.   I?m currently dying in QT -  I?ve seen these QCLUcene errors
> before, but not on the platforms  that I?m currently testing the builds on
> ?.  I believe that I get around this by going into the qt build directory
> and running ?make install? and the problem goes  away.
>
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneIndexSearcher::~QCLuceneIndexSearcher()'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneTermQuery::QCLuceneTermQuery(QCLuceneTerm
> const&)'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneIndexReader::deleteDocuments(QCLuceneTerm
> const&)'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneIndexWriter::close()'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLucenePhraseQuery::addTerm(QCLuceneTerm const&)'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneTermQuery::~QCLuceneTermQuery()'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneQueryPrivate::~QCLuceneQueryPrivate()'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneStopAnalyzer::~QCLuceneStopAnalyzer()'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneBooleanQuery::add(QCLuceneQuery*, bool,
> bool, bool)'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to
> `QCLuceneStandardAnalyzer::QCLuceneStandardAnalyzer()'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneIndexWriter::setMinMergeDocs(int)'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneStopAnalyzer::englishStopWords() const'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneDocument::clear()'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneTerm::QCLuceneTerm(QString const&, QString
> const&)'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneIndexWriter::setMaxFieldLength(int)'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLucenePhraseQuery::QCLucenePhraseQuery()'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to
> `QCLuceneStandardAnalyzer::~QCLuceneStandardAnalyzer()'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneIndexWriter::addDocument(QCLuceneDocument&,
> QCLuceneAnalyzer&)'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneSearcher::search(QCLuceneQuery const&)'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneDocument::QCLuceneDocument()'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneQuery::toString() const'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneDocument::~QCLuceneDocument()'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneIndexReader::open(QString const&)'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneDocument::add(QCLuceneField*)'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneIndexWriter::optimize()'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneField::QCLuceneField(QString const&, QString
> const&, int)'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneIndexReader::indexExists(QString const&)'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneTerm::~QCLuceneTerm()'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneDocumentPrivate::~QCLuceneDocumentPrivate()'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to `QCLuceneHits::document(int)'
> /home/angel/PV/ParaViewSuperbuild/4.3.1/Build_4.3.1/qt/src/qt-build/lib/libQtHelp.so:
> undefined reference to
> `QCLuceneIndexWriter::~QCLuceneIndexWriter()'________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
> From: <Angelini>, Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
> Date: Wednesday, January 21, 2015 at 11:36 AM
> To: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>, ParaView
> <paraview at paraview.org>, ParaView Developers
> <paraview-developers at paraview.org>
> Subject: Re: [Paraview] ANN: ParaView 4.3.1 is available for download
>
> I?m having trouble building 4.3.1 on several systems where 4.2 built without
> issue.  Is there a particular version of cmake that 4.3.1 needs to be built
> with?
>
> ________________________________
> Rick Angelini
> USArmy Research Laboratory
> CISD/HPC Architectures Team
> Phone:  410-278-6266
>
> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
> Date: Tuesday, January 20, 2015 at 4:17 PM
> To: ParaView <paraview at paraview.org>, ParaView Developers
> <paraview-developers at paraview.org>
> Subject: [Paraview] ANN: ParaView 4.3.1 is available for download
>
> Folks,
>
> ParaView 4.3.1 is now available for download. Checkout the release
> notes on the Kitware blog [1].
>
> As always, we look forward to your feedback [2].
>
> Also stay tuned to the Kitware Blog [3] for upcoming features and
> enhancements to ParaView, ParaView Catalyst, ParaViewWeb and much
> more!
>
> - The ParaView team
>
> [1] http://www.kitware.com/blog/posts/view/825
> [2] http://paraview.uservoice.com
> [3] http://www.kitware.com/blog/
> _______________________________________________
> 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
>
> Search the list archives at: http://markmail.org/search/?q=ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview
>

From furutaka.kazuyoshi at jaea.go.jp  Wed Jan 21 18:05:06 2015
From: furutaka.kazuyoshi at jaea.go.jp (Kazuyoshi Furutaka)
Date: Thu, 22 Jan 2015 08:05:06 +0900 (JST)
Subject: [Paraview-developers] [Paraview] ANN: ParaView 4.3.1 is
	available for download
In-Reply-To: <CAB5Fpx7gs9sVd52SUS=fWO7ycGBWF3q39H9e6CzfyPYjVJgEsA@mail.gmail.com>
References: <CADHSJjA+pfqoJM5NbvCcTWXWiMEh4MqLiWdYSrHHZ8zEdYcmkw@mail.gmail.com>
 <20150121.163806.74547358.furutaka.kazuyoshi@jaea.go.jp>
 <CAB5Fpx7gs9sVd52SUS=fWO7ycGBWF3q39H9e6CzfyPYjVJgEsA@mail.gmail.com>
Message-ID: <20150122.080506.449440093.furutaka.kazuyoshi@jaea.go.jp>

Hi Cory,

I could build it after the `git submodule update --init`
command.  Thanks!
(Well, I must confess that I've heard about the command 
but completely forgotten...  I wonder if I can automate
the update of the submodules...)

Kazuyoshi

From: Cory Quammen <cory.quammen at kitware.com>
Subject: Re: [Paraview] ANN: ParaView 4.3.1 is available for download
Date: Wed, 21 Jan 2015 09:32:37 -0500

> Did you update the ParaView submodules?
> 
> Try running
> 
> git submodule update --init
> 
> from within the ParaView source directory and compile again.
--
Kazuyoshi Furutaka
furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp

From cory.quammen at kitware.com  Wed Jan 21 18:11:52 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Wed, 21 Jan 2015 18:11:52 -0500
Subject: [Paraview-developers] [Paraview] ANN: ParaView 4.3.1 is
 available for download
In-Reply-To: <20150122.080506.449440093.furutaka.kazuyoshi@jaea.go.jp>
References: <CADHSJjA+pfqoJM5NbvCcTWXWiMEh4MqLiWdYSrHHZ8zEdYcmkw@mail.gmail.com>
 <20150121.163806.74547358.furutaka.kazuyoshi@jaea.go.jp>
 <CAB5Fpx7gs9sVd52SUS=fWO7ycGBWF3q39H9e6CzfyPYjVJgEsA@mail.gmail.com>
 <20150122.080506.449440093.furutaka.kazuyoshi@jaea.go.jp>
Message-ID: <CAB5Fpx6CkbPwL1wfjeQ4aK9hyhSNgqKvS_VWFLy5aYovuqneFg@mail.gmail.com>

Kazuyoshi,

No problem. We all forget to update the submodules from time to time :-)

Thanks,
Cory



On Wed, Jan 21, 2015 at 6:05 PM, Kazuyoshi Furutaka <
furutaka.kazuyoshi at jaea.go.jp> wrote:

> Hi Cory,
>
> I could build it after the `git submodule update --init`
> command.  Thanks!
> (Well, I must confess that I've heard about the command
> but completely forgotten...  I wonder if I can automate
> the update of the submodules...)
>
> Kazuyoshi
>
> From: Cory Quammen <cory.quammen at kitware.com>
> Subject: Re: [Paraview] ANN: ParaView 4.3.1 is available for download
> Date: Wed, 21 Jan 2015 09:32:37 -0500
>
> > Did you update the ParaView submodules?
> >
> > Try running
> >
> > git submodule update --init
> >
> > from within the ParaView source directory and compile again.
> --
> Kazuyoshi Furutaka
> furutaka _dot_ kazuyoshi _at_ jaea _dot_ go _dot_ jp
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>



-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150121/74c3b044/attachment.html>

From dwilches at gmail.com  Thu Jan 22 00:00:41 2015
From: dwilches at gmail.com (Daniel Wilches Maradey)
Date: Wed, 21 Jan 2015 22:00:41 -0700
Subject: [Paraview-developers] Error loading plugin in different machine
	from where it was compiled
Message-ID: <CAEbtaO1BfOSRptAHx=+J5kyuhkBjL1HjGKEuzxAYpiVW3LW-Og@mail.gmail.com>

Hello,

I depeloved a plugin for Paraview and in my build machine it works well.
But, I'm seeing the following problem when I try to load it in a different
machine (using "Tools -> Manage Plugins ..."):


*ERROR: In
C:\DBD\pvs-x32\paraview\src\paraview\ParaViewCore\ClientServerCore\Core\vtkPVPluginLoader.cxx,
line 360*
*vtkPVPluginLoader (0BA1F610): N*


?The error message is that one you see there, it looks chopped and doesn't
give me much information about the actual reason.?

?What could be causing this error?
The version of Paraview is the same in both machines: 4.2.0? 32-bits. The
build machine is running Win7 32 bits and the other machine, where the
error happens, is running Win8 64-bits.

Also in case it helps: I have tried two versions of the plugin, one
compiled for Debug (which shows the message you see there), and one
compiled for Release (which just crashes Paraview).

?Thanks.?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150121/39d70e4c/attachment.html>

From joachim.pouderoux at kitware.com  Thu Jan 22 07:19:57 2015
From: joachim.pouderoux at kitware.com (Joachim Pouderoux)
Date: Thu, 22 Jan 2015 13:19:57 +0100
Subject: [Paraview-developers] Error loading plugin in different machine
 from where it was compiled
In-Reply-To: <CAEbtaO1BfOSRptAHx=+J5kyuhkBjL1HjGKEuzxAYpiVW3LW-Og@mail.gmail.com>
References: <CAEbtaO1BfOSRptAHx=+J5kyuhkBjL1HjGKEuzxAYpiVW3LW-Og@mail.gmail.com>
Message-ID: <54C0EAED.7060307@kitware.com>

Hi Daniel,

The error occures because the Windows kernel is unable to load your DLL 
file. This might occures because your dynamic library requires another 
DLL that is not present on the target machine. If you ignore which one 
it is, you can check with Dependency Walker tool.
Beware, if the target system runs ParaView in release mode, your plugin 
must be in release too (same for debug). Also note that a x64 plugin 
cannot be loaded by a x32 version of the software and vice-versa.
Hope it helps!

Joachim
Techincal Expert - Kitware France

On 22/01/2015 06:00, Daniel Wilches Maradey wrote:
> Hello,
>
> I depeloved a plugin for Paraview and in my build machine it works 
> well. But, I'm seeing the following problem when I try to load it in a 
> different machine (using "Tools -> Manage Plugins ..."):
>
> *
> *
> *ERROR: In 
> C:\DBD\pvs-x32\paraview\src\paraview\ParaViewCore\ClientServerCore\Core\vtkPVPluginLoader.cxx, 
> line 360*
> *vtkPVPluginLoader (0BA1F610): N*
>
>
> ?The error message is that one you see there, it looks chopped and 
> doesn't give me much information about the actual reason.?
>
> ? What could be causing this error?
> The version of Paraview is the same in both machines: 4.2.0? 32-bits. 
> The build machine is running Win7 32 bits and the other machine, where 
> the error happens, is running Win8 64-bits.
>
> Also in case it helps: I have tried two versions of the plugin, one 
> compiled for Debug (which shows the message you see there), and one 
> compiled for Release (which just crashes Paraview).
>
> ? Thanks.?
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at: http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150122/b76e32b3/attachment.html>

From utkarsh.ayachit at kitware.com  Thu Jan 22 09:53:06 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 22 Jan 2015 09:53:06 -0500
Subject: [Paraview-developers] Gatekeeper Review Summary
Message-ID: <CADHSJjCxOar9X-AXA4FbyA=fnpSXe-CG4U9jE9Aq5nkheTd8zA@mail.gmail.com>

SUMMARY
---------------------------------------------
Topics merged into master (v4.3.1-46-gc563e84):
        15246_updated_data_active_values
        allow-catalyst-tables
        cgns-plugin-string-fix
        custom_color_map_defaults_for_arrays
        fix_sphinx_icon
        internal_halo_finder
        new_cosmotools
(VTK)   pvweb-document-disable-registry
        read_only_certain_halos


---------------------------------------------
Topics reverted from next:
  msmpi-fix
  pvweb-add-scalar-range-controls

From Anton.Piccardo-Selg at tessella.com  Thu Jan 22 10:00:34 2015
From: Anton.Piccardo-Selg at tessella.com (Anton.Piccardo-Selg at tessella.com)
Date: Thu, 22 Jan 2015 15:00:34 +0000
Subject: [Paraview-developers] How to swap to sources in a pipeline?
Message-ID: <OF2123B477.A32AB3C1-ON80257DD5.0050698C-80257DD5.00527367@tessella.co.uk>

An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150122/6382479a/attachment-0001.html>

From cory.quammen at kitware.com  Thu Jan 22 10:04:10 2015
From: cory.quammen at kitware.com (Cory Quammen)
Date: Thu, 22 Jan 2015 10:04:10 -0500
Subject: [Paraview-developers] How to swap to sources in a pipeline?
In-Reply-To: <OF2123B477.A32AB3C1-ON80257DD5.0050698C-80257DD5.00527367@tessella.co.uk>
References: <OF2123B477.A32AB3C1-ON80257DD5.0050698C-80257DD5.00527367@tessella.co.uk>
Message-ID: <CAB5Fpx6iDeOG9eLF2g_MwQQRu8W3QcO9xOHaEGK=zDYuNE7jBw@mail.gmail.com>

Anton,

Right-click on the source whose input you would like to change and select
the "Change Input..." menu item.

- Cory

On Thu, Jan 22, 2015 at 10:00 AM, <Anton.Piccardo-Selg at tessella.com> wrote:

> Hi,
>
> I have a linear pipeline which consists of a source and and several
> filters. For various reasons I need to change the source of this pipeline.
>
> I was therefore wondering if there is a way to reset the input port of the
> first filter to the new source, or do I have to create all the filters
> again? I would like to just swap the sources in order to keep the filter
> settings.
>
> Many thanks,
>
> Anton
>
> This message is commercial in confidence and may be privileged. It is
> intended for the
> addressee(s) only. Access to this message by anyone else is unauthorized
> and strictly prohibited.
> If you have received this message in error, please inform the sender
> immediately. Please note that
> messages sent or received by the Tessella e-mail system may be monitored
> and stored in an
> information retrieval system.
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150122/c4461279/attachment.html>

From yumin.yuan at kitware.com  Thu Jan 22 10:27:10 2015
From: yumin.yuan at kitware.com (Yumin Yuan)
Date: Thu, 22 Jan 2015 10:27:10 -0500
Subject: [Paraview-developers] How to swap to sources in a pipeline?
In-Reply-To: <CAB5Fpx6iDeOG9eLF2g_MwQQRu8W3QcO9xOHaEGK=zDYuNE7jBw@mail.gmail.com>
References: <OF2123B477.A32AB3C1-ON80257DD5.0050698C-80257DD5.00527367@tessella.co.uk>
 <CAB5Fpx6iDeOG9eLF2g_MwQQRu8W3QcO9xOHaEGK=zDYuNE7jBw@mail.gmail.com>
Message-ID: <CAKkFzufKHuXh__ZD_xd-=S0a_AZdCWba_dY_6MLU=Ss7ppHeog@mail.gmail.com>

Hi Anton,

Since you are asking on developers list, I assume you want to know how to
do this in the code :)

vtkSMPropertyHelper(1stSMFilterProxy, "Input").Set(newSMSourceProxy);

HTH
Yumin

On Thu, Jan 22, 2015 at 10:04 AM, Cory Quammen <cory.quammen at kitware.com>
wrote:

> Anton,
>
> Right-click on the source whose input you would like to change and select
> the "Change Input..." menu item.
>
> - Cory
>
> On Thu, Jan 22, 2015 at 10:00 AM, <Anton.Piccardo-Selg at tessella.com>
> wrote:
>
>> Hi,
>>
>> I have a linear pipeline which consists of a source and and several
>> filters. For various reasons I need to change the source of this pipeline.
>>
>> I was therefore wondering if there is a way to reset the input port of
>> the first filter to the new source, or do I have to create all the filters
>> again? I would like to just swap the sources in order to keep the filter
>> settings.
>>
>> Many thanks,
>>
>> Anton
>>
>> This message is commercial in confidence and may be privileged. It is
>> intended for the
>> addressee(s) only. Access to this message by anyone else is unauthorized
>> and strictly prohibited.
>> If you have received this message in error, please inform the sender
>> immediately. Please note that
>> messages sent or received by the Tessella e-mail system may be monitored
>> and stored in an
>> information retrieval system.
>>
>>
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Search the list archives at:
>> http://markmail.org/search/?q=Paraview-developers
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>>
>
>
> --
> Cory Quammen
> R&D Engineer
> Kitware, Inc.
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150122/508dc9dd/attachment.html>

From utkarsh.ayachit at kitware.com  Thu Jan 22 10:37:40 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 22 Jan 2015 10:37:40 -0500
Subject: [Paraview-developers] Stage/PVVTK Housekeeping
Message-ID: <CADHSJjB7VczK=3fQ9evzoF-KYaT2VJeVUJXFV=u2_G1s=ooR5w@mail.gmail.com>

Folks,

The following branches will be purged from ParaView stage/pvvtk at the
of tomorrow. If you are interested in them, please make sure you have
local copies. In short if the topic is not merged in pvvtk/pv-master,
pvvtk/pv-next, paraview/master or paraview/next it will be purged.

PVVTK
---------------------
revert-python-wrapping
ghost-data
update-vtk-20140310
numpy-interface-3
ghost-points-support
GL2PS_png_zlib_support
13569_better_unique_values3
topic_new_transfer_function
fix-mingw
predicate-selections
test/use-external-data
13569_better_unique_values
vtk-test-macro-compat
vtkweb-update-to-WAMP-v2
cmake-python-modules-check
unified-bindings-warning-sweep
fixing-Outline-Filters
vtk_vr_improvements
cmake-fix-commit-2
13374-slac-multiple-modes
predicate_selections_tests
13569_better_unique_values2

ParaView
-----------------------------------------
catalyst-wrap-exclusion
15052_settings_test_failure
ghost-points-support
visit-bridge-update-2.7.0
fix-external-vtk-config
external-data
convert-selection-14941
14880_fix_state_properties
update_online_help
fix_delayed_interactive_render_issues
pvweb-vgl-toogle-toolbar
0014870_ordered_compositing
vr_improvements
pvw_rpc
12742_scalar_bar_improvements
widen_properties_panel
pvweb-update-vtk-for-vgl
co-processing-fortran-utilities
update_3d_widgets
allow-downstream-use-of-www
fix-external-vtk-python-wrapping
simpler-catalyst-editions
pvweb-add-scalar-range-controls
13963_add_light_management
fix-externals
smooth-cube-axis-actor-labels
pvw-testing
spatio-temporal-parallelism
fix-build-on-c++11
fix_sorting
fix-xml-crash-on-close
13977-paraviewweb-testing
help-15203
unified-bindings-warning-sweep
auto_update_active_values_from_visible
bing-map-support
update_vtk_sha1
pvweb-fix-visualizer-can-test
10962_find_data_initialization
transfer-function-plots-bugfix
update_vtk
msmpi-fix
streaming-temporal-AMR
14895_fix_log_plot_axis

From Anton.Piccardo-Selg at tessella.com  Thu Jan 22 12:05:36 2015
From: Anton.Piccardo-Selg at tessella.com (Anton.Piccardo-Selg at tessella.com)
Date: Thu, 22 Jan 2015 17:05:36 +0000
Subject: [Paraview-developers] How to swap to sources in a pipeline?
In-Reply-To: <CAKkFzufKHuXh__ZD_xd-=S0a_AZdCWba_dY_6MLU=Ss7ppHeog@mail.gmail.com>
References: <CAKkFzufKHuXh__ZD_xd-=S0a_AZdCWba_dY_6MLU=Ss7ppHeog@mail.gmail.com>, 
 <OF2123B477.A32AB3C1-ON80257DD5.0050698C-80257DD5.00527367@tessella.co.uk>
 <CAB5Fpx6iDeOG9eLF2g_MwQQRu8W3QcO9xOHaEGK=zDYuNE7jBw@mail.gmail.com>
Message-ID: <OF76186C97.CC436AF8-ON80257DD5.005D1930-80257DD5.005DE57C@tessella.co.uk>

An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150122/af6d7e27/attachment.html>

From utkarsh.ayachit at kitware.com  Fri Jan 23 09:52:41 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Fri, 23 Jan 2015 09:52:41 -0500
Subject: [Paraview-developers] Gatekeeper Review Summary
Message-ID: <CADHSJjB5KT22SFV2OcBT32qh1UURf9JGmJ+fUJpJaRaKAn2dpw@mail.gmail.com>

Topics merged into master (v4.3.1-50-g71439c9):
             help-15203
(VTK)   pvweb-add-scalar-range-controls

From wascott at sandia.gov  Fri Jan 23 20:33:35 2015
From: wascott at sandia.gov (Scott, W Alan)
Date: Sat, 24 Jan 2015 01:33:35 +0000
Subject: [Paraview-developers] [EXTERNAL] Re: CMake Version
In-Reply-To: <CADwGrVrGj0+3hx8rXEpgWZJexA0Naco2f2pqW1zOF2DS34G8qQ@mail.gmail.com>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
 <20150108150323.GA26903@megas.kitwarein.com>
 <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>
 <CANjZAi-+bT4DiLs6DcT_5=3okWzuC2c547mRnMC6TxgdDstqZQ@mail.gmail.com>
 <CADwGrVokKwcrmo4moRvz-Lu6v0_ybqBBHHuoH9Kkoc1Tqoub_Q@mail.gmail.com>
 <CAMkPkZWtwr7qvj+BWYD=FQowOwRQBuTbJAt-W3Cuz2Lfx=r_xw@mail.gmail.com>
 <CANjZAi98_=qEpfoARjmPn2u_fpKOCRSefZZFha=2A+Sdk=j-Gw@mail.gmail.com>
 <cc184e1a76ef4f23a73a09fb9f2da781@ES05AMSNLNT.srn.sandia.gov>
 <CADwGrVrGj0+3hx8rXEpgWZJexA0Naco2f2pqW1zOF2DS34G8qQ@mail.gmail.com>
Message-ID: <85a21663f7ee46f1b5ce74390d175e8b@ES05AMSNLNT.srn.sandia.gov>

Dan,
OK, now we are saying that we have two locations that we document what versions of packages we use.  There are actually three, if you include inside the superbuild itself.  I strongly feel that there should be one location that everyone can go to when they want to know what version of packages are to be used.  Currently, these two locations are:

http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisites
and
http://www.paraview.org/Wiki/ParaView_Binaries

Alan
p.s. ? not trying to shoot the messenger here ? thanks for the reply.  My point is just that we should document the version of what builds with ParaView one place, having gone through weeks of hell building cgns.



From: Dan Lipsa [mailto:dan.lipsa at kitware.com]
Sent: Monday, January 12, 2015 8:57 PM
To: Scott, W Alan
Cc: David E DeMarle; Marcus D. Hanwell; paraview-developers at paraview.org
Subject: Re: [Paraview-developers] [EXTERNAL] Re: CMake Version

http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisites

has the correct minimum version required for cmake 2.8.8.

Dan


On Fri, Jan 9, 2015 at 12:10 PM, Scott, W Alan <wascott at sandia.gov<mailto:wascott at sandia.gov>> wrote:
I am hearing that it makes sense to leave current minimum cmake version for VTK.  That is OK with me.  It is also always good to know that you can always use latest/ greatest Cmake.  But, that isn?t true for all packages (and I believe latest Cmake has been incompatible in the past).  Let?s update the ParaView wiki to show what Cmake version is used for the builds?  Surprisingly, upgrading Cmake versions isn?t trivial for some of us that build somewhere around a dozen platforms, and I don?t like having to guess what version to use...

Thanks all!

Alan


From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org<mailto:paraview-developers-bounces at paraview.org>] On Behalf Of David E DeMarle
Sent: Friday, January 09, 2015 8:53 AM
To: Marcus D. Hanwell
Cc: paraview-developers at paraview.org<mailto:paraview-developers at paraview.org>
Subject: [EXTERNAL] Re: [Paraview-developers] CMake Version

If there isn't a compelling reason I think we should remain
conservative, and it sounds like there is not in this case (especially
for a dependency that is pretty optional for many of our users).

Agreed. One factor in the minimum required decision is what the popular Linux distros have readily on hand.

You
can generally always use the latest CMake if you choose, but making
that the minimum makes it harder for others to compile and use our
code (often using the packaged CMake).

Agreed again. The "faraway" submission in the dependencies track of the vtk dashboard exists to verity that CMake master works for VTK. Unfortunately it didn't submit today so someone needs to shove it.

Marcus


_______________________________________________
Paraview-developers mailing list
Paraview-developers at paraview.org<mailto: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/20150124/28a9a0e6/attachment.html>

From mickey.phy at gmail.com  Mon Jan 26 09:07:48 2015
From: mickey.phy at gmail.com (Mickael Philit)
Date: Mon, 26 Jan 2015 15:07:48 +0100
Subject: [Paraview-developers] Change in ParaView[master]: Define a
 helper function to directly read a correct std::str...
In-Reply-To: <54B40FC7.3080808@gmail.com>
References: <gerrit.1420915612000.Ic85b5ea0fbb068384e7ce55e8b5a223c826ed66b@review.source.kitware.com>
 <20150112141918.1BF4F7EC0229@source.kitware.com> <54B40FC7.3080808@gmail.com>
Message-ID: <54C64A34.3090203@gmail.com>

Hello,

Can we try to re-enable the CGNS reader plugin in Paraview SuperBuild 
(http://review.source.kitware.com/#/t/5225/) ?

Best Regards

Mickael


From utkarsh.ayachit at kitware.com  Mon Jan 26 09:57:14 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 26 Jan 2015 09:57:14 -0500
Subject: [Paraview-developers] Change in ParaView[master]: Define a
 helper function to directly read a correct std::str...
In-Reply-To: <54C64A34.3090203@gmail.com>
References: <gerrit.1420915612000.Ic85b5ea0fbb068384e7ce55e8b5a223c826ed66b@review.source.kitware.com>
 <20150112141918.1BF4F7EC0229@source.kitware.com>
 <54B40FC7.3080808@gmail.com> <54C64A34.3090203@gmail.com>
Message-ID: <CADHSJjBT1FFdQTzGOJD7FL4jQzyJGkdWLOfCx14q6E8_MxtPQw@mail.gmail.com>

Sure things, once the superbuilds dashboards clear up, however.
Currently, the dashboards are already broken. I wouldn't want to add
another change that could potentially cause new issues.

Utkarsh

On Mon, Jan 26, 2015 at 9:07 AM, Mickael Philit <mickey.phy at gmail.com> wrote:
> Hello,
>
> Can we try to re-enable the CGNS reader plugin in Paraview SuperBuild
> (http://review.source.kitware.com/#/t/5225/) ?
>
> Best Regards
>
> Mickael
>

From dave.demarle at kitware.com  Mon Jan 26 10:22:24 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Mon, 26 Jan 2015 10:22:24 -0500
Subject: [Paraview-developers] CMake Version
In-Reply-To: <85a21663f7ee46f1b5ce74390d175e8b@ES05AMSNLNT.srn.sandia.gov>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
 <20150108150323.GA26903@megas.kitwarein.com>
 <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>
 <CANjZAi-+bT4DiLs6DcT_5=3okWzuC2c547mRnMC6TxgdDstqZQ@mail.gmail.com>
 <CADwGrVokKwcrmo4moRvz-Lu6v0_ybqBBHHuoH9Kkoc1Tqoub_Q@mail.gmail.com>
 <CAMkPkZWtwr7qvj+BWYD=FQowOwRQBuTbJAt-W3Cuz2Lfx=r_xw@mail.gmail.com>
 <CANjZAi98_=qEpfoARjmPn2u_fpKOCRSefZZFha=2A+Sdk=j-Gw@mail.gmail.com>
 <cc184e1a76ef4f23a73a09fb9f2da781@ES05AMSNLNT.srn.sandia.gov>
 <CADwGrVrGj0+3hx8rXEpgWZJexA0Naco2f2pqW1zOF2DS34G8qQ@mail.gmail.com>
 <85a21663f7ee46f1b5ce74390d175e8b@ES05AMSNLNT.srn.sandia.gov>
Message-ID: <CANjZAi-=397KOE5G_-Lj7E5i-o3QR4kZe=mZOVRn6T9SxaWvYQ@mail.gmail.com>

We want to document two things.

1) What version ranges the ParaView source code is compatible with.
2) What specific versions were the Kitware binaries built so that people
can build and distribute plugins that work with them.

On Friday, January 23, 2015, Scott, W Alan <wascott at sandia.gov> wrote:

>  Dan,
>
> OK, now we are saying that we have two locations that we document what
> versions of packages we use.  There are actually three, if you include
> inside the superbuild itself.  I strongly feel that there should be one
> location that everyone can go to when they want to know what version of
> packages are to be used.  Currently, these two locations are:
>
>
>
> http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisites
>
> and
>
> http://www.paraview.org/Wiki/ParaView_Binaries
>
>
>
> Alan
>
> p.s. ? not trying to shoot the messenger here ? thanks for the reply.  My
> point is just that we should document the version of what builds with
> ParaView one place, having gone through weeks of hell building cgns.
>
>
>
>
>
>
>
> *From:* Dan Lipsa [mailto:dan.lipsa at kitware.com]
> *Sent:* Monday, January 12, 2015 8:57 PM
> *To:* Scott, W Alan
> *Cc:* David E DeMarle; Marcus D. Hanwell; paraview-developers at paraview.org
> *Subject:* Re: [Paraview-developers] [EXTERNAL] Re: CMake Version
>
>
>
> http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisites
>
>
>
> has the correct minimum version required for cmake 2.8.8.
>
>
>
> Dan
>
>
>
>
>
> On Fri, Jan 9, 2015 at 12:10 PM, Scott, W Alan <wascott at sandia.gov> wrote:
>
> I am hearing that it makes sense to leave current minimum cmake version
> for VTK.  That is OK with me.  It is also always good to know that you can
> always use latest/ greatest Cmake.  But, that isn?t true for all packages
> (and I believe latest Cmake has been incompatible in the past).  Let?s
> update the ParaView wiki to show what Cmake version is used for the
> builds?  Surprisingly, upgrading Cmake versions isn?t trivial for some of
> us that build somewhere around a dozen platforms, and I don?t like having
> to guess what version to use...
>
>
>
> Thanks all!
>
>
>
> Alan
>
>
>
>
>
> *From:* Paraview-developers [mailto:
> paraview-developers-bounces at paraview.org] *On Behalf Of *David E DeMarle
> *Sent:* Friday, January 09, 2015 8:53 AM
> *To:* Marcus D. Hanwell
> *Cc:* paraview-developers at paraview.org
> *Subject:* [EXTERNAL] Re: [Paraview-developers] CMake Version
>
>
>
>  If there isn't a compelling reason I think we should remain
> conservative, and it sounds like there is not in this case (especially
> for a dependency that is pretty optional for many of our users).
>
>
>
> Agreed. One factor in the minimum required decision is what the popular
> Linux distros have readily on hand.
>
>
>
>  You
> can generally always use the latest CMake if you choose, but making
> that the minimum makes it harder for others to compile and use our
> code (often using the packaged CMake).
>
>
>
> Agreed again. The "faraway" submission in the dependencies track of the
> vtk dashboard exists to verity that CMake master works for VTK.
> Unfortunately it didn't submit today so someone needs to shove it.
>
>
>
>  Marcus
>
>
>
>
> _______________________________________________
> 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/20150126/cd4a10eb/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Jan 26 10:30:22 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 26 Jan 2015 10:30:22 -0500
Subject: [Paraview-developers] CMake Version
In-Reply-To: <CANjZAi-=397KOE5G_-Lj7E5i-o3QR4kZe=mZOVRn6T9SxaWvYQ@mail.gmail.com>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
 <20150108150323.GA26903@megas.kitwarein.com>
 <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>
 <CANjZAi-+bT4DiLs6DcT_5=3okWzuC2c547mRnMC6TxgdDstqZQ@mail.gmail.com>
 <CADwGrVokKwcrmo4moRvz-Lu6v0_ybqBBHHuoH9Kkoc1Tqoub_Q@mail.gmail.com>
 <CAMkPkZWtwr7qvj+BWYD=FQowOwRQBuTbJAt-W3Cuz2Lfx=r_xw@mail.gmail.com>
 <CANjZAi98_=qEpfoARjmPn2u_fpKOCRSefZZFha=2A+Sdk=j-Gw@mail.gmail.com>
 <cc184e1a76ef4f23a73a09fb9f2da781@ES05AMSNLNT.srn.sandia.gov>
 <CADwGrVrGj0+3hx8rXEpgWZJexA0Naco2f2pqW1zOF2DS34G8qQ@mail.gmail.com>
 <85a21663f7ee46f1b5ce74390d175e8b@ES05AMSNLNT.srn.sandia.gov>
 <CANjZAi-=397KOE5G_-Lj7E5i-o3QR4kZe=mZOVRn6T9SxaWvYQ@mail.gmail.com>
Message-ID: <CADHSJjDd2E+uC_umZ=nvi3eO9JeNa-e+n+eYH40Wm8PejGfhDw@mail.gmail.com>

I do see a bigger issue that Alan raises, which is a fair one. Wikis
have too much stale text! I keep wondering if we should drop the Wikis
entirely and go to documenting in code so it's easier to maintain. We
already have started documenting things like API changes, etc in the
Doxygen pages[1]. Maybe we should migrate everything there.

The one reason for Wikis is that its easier for external folks to
change. But if we move to github/gitlab workflow soon, people will be
able to edit files and create merge requests on the Web directly as
well. Hence those who are actually keep on editing the documentation
will indeed be able to.

What do folks think?

Utkarsh


[1] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/index.html

On Mon, Jan 26, 2015 at 10:22 AM, David E DeMarle
<dave.demarle at kitware.com> wrote:
> We want to document two things.
>
> 1) What version ranges the ParaView source code is compatible with.
> 2) What specific versions were the Kitware binaries built so that people can
> build and distribute plugins that work with them.
>
>
> On Friday, January 23, 2015, Scott, W Alan <wascott at sandia.gov> wrote:
>>
>> Dan,
>>
>> OK, now we are saying that we have two locations that we document what
>> versions of packages we use.  There are actually three, if you include
>> inside the superbuild itself.  I strongly feel that there should be one
>> location that everyone can go to when they want to know what version of
>> packages are to be used.  Currently, these two locations are:
>>
>>
>>
>> http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisites
>>
>> and
>>
>> http://www.paraview.org/Wiki/ParaView_Binaries
>>
>>
>>
>> Alan
>>
>> p.s. ? not trying to shoot the messenger here ? thanks for the reply.  My
>> point is just that we should document the version of what builds with
>> ParaView one place, having gone through weeks of hell building cgns.
>>
>>
>>
>>
>>
>>
>>
>> From: Dan Lipsa [mailto:dan.lipsa at kitware.com]
>> Sent: Monday, January 12, 2015 8:57 PM
>> To: Scott, W Alan
>> Cc: David E DeMarle; Marcus D. Hanwell; paraview-developers at paraview.org
>> Subject: Re: [Paraview-developers] [EXTERNAL] Re: CMake Version
>>
>>
>>
>> http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisites
>>
>>
>>
>> has the correct minimum version required for cmake 2.8.8.
>>
>>
>>
>> Dan
>>
>>
>>
>>
>>
>> On Fri, Jan 9, 2015 at 12:10 PM, Scott, W Alan <wascott at sandia.gov> wrote:
>>
>> I am hearing that it makes sense to leave current minimum cmake version
>> for VTK.  That is OK with me.  It is also always good to know that you can
>> always use latest/ greatest Cmake.  But, that isn?t true for all packages
>> (and I believe latest Cmake has been incompatible in the past).  Let?s
>> update the ParaView wiki to show what Cmake version is used for the builds?
>> Surprisingly, upgrading Cmake versions isn?t trivial for some of us that
>> build somewhere around a dozen platforms, and I don?t like having to guess
>> what version to use...
>>
>>
>>
>> Thanks all!
>>
>>
>>
>> Alan
>>
>>
>>
>>
>>
>> From: Paraview-developers
>> [mailto:paraview-developers-bounces at paraview.org] On Behalf Of David E
>> DeMarle
>> Sent: Friday, January 09, 2015 8:53 AM
>> To: Marcus D. Hanwell
>> Cc: paraview-developers at paraview.org
>> Subject: [EXTERNAL] Re: [Paraview-developers] CMake Version
>>
>>
>>
>> If there isn't a compelling reason I think we should remain
>> conservative, and it sounds like there is not in this case (especially
>> for a dependency that is pretty optional for many of our users).
>>
>>
>>
>> Agreed. One factor in the minimum required decision is what the popular
>> Linux distros have readily on hand.
>>
>>
>>
>> You
>> can generally always use the latest CMake if you choose, but making
>> that the minimum makes it harder for others to compile and use our
>> code (often using the packaged CMake).
>>
>>
>>
>> Agreed again. The "faraway" submission in the dependencies track of the
>> vtk dashboard exists to verity that CMake master works for VTK.
>> Unfortunately it didn't submit today so someone needs to shove it.
>>
>>
>>
>> Marcus
>>
>>
>>
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>

From dave.demarle at kitware.com  Mon Jan 26 10:33:48 2015
From: dave.demarle at kitware.com (David E DeMarle)
Date: Mon, 26 Jan 2015 10:33:48 -0500
Subject: [Paraview-developers] CMake Version
In-Reply-To: <CADHSJjDd2E+uC_umZ=nvi3eO9JeNa-e+n+eYH40Wm8PejGfhDw@mail.gmail.com>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
 <20150108150323.GA26903@megas.kitwarein.com>
 <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>
 <CANjZAi-+bT4DiLs6DcT_5=3okWzuC2c547mRnMC6TxgdDstqZQ@mail.gmail.com>
 <CADwGrVokKwcrmo4moRvz-Lu6v0_ybqBBHHuoH9Kkoc1Tqoub_Q@mail.gmail.com>
 <CAMkPkZWtwr7qvj+BWYD=FQowOwRQBuTbJAt-W3Cuz2Lfx=r_xw@mail.gmail.com>
 <CANjZAi98_=qEpfoARjmPn2u_fpKOCRSefZZFha=2A+Sdk=j-Gw@mail.gmail.com>
 <cc184e1a76ef4f23a73a09fb9f2da781@ES05AMSNLNT.srn.sandia.gov>
 <CADwGrVrGj0+3hx8rXEpgWZJexA0Naco2f2pqW1zOF2DS34G8qQ@mail.gmail.com>
 <85a21663f7ee46f1b5ce74390d175e8b@ES05AMSNLNT.srn.sandia.gov>
 <CANjZAi-=397KOE5G_-Lj7E5i-o3QR4kZe=mZOVRn6T9SxaWvYQ@mail.gmail.com>
 <CADHSJjDd2E+uC_umZ=nvi3eO9JeNa-e+n+eYH40Wm8PejGfhDw@mail.gmail.com>
Message-ID: <CANjZAi-zLua91unC8O8dLQwvQGZodyy7a0Y_CFSeMe7qFajwPA@mail.gmail.com>

Sounds like a good idea to me, AS LONG AS the mechanics of finding and
changing said information is easy to find and described well.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Mon, Jan 26, 2015 at 10:30 AM, Utkarsh Ayachit <
utkarsh.ayachit at kitware.com> wrote:

> I do see a bigger issue that Alan raises, which is a fair one. Wikis
> have too much stale text! I keep wondering if we should drop the Wikis
> entirely and go to documenting in code so it's easier to maintain. We
> already have started documenting things like API changes, etc in the
> Doxygen pages[1]. Maybe we should migrate everything there.
>
> The one reason for Wikis is that its easier for external folks to
> change. But if we move to github/gitlab workflow soon, people will be
> able to edit files and create merge requests on the Web directly as
> well. Hence those who are actually keep on editing the documentation
> will indeed be able to.
>
> What do folks think?
>
> Utkarsh
>
>
> [1] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/index.html
>
> On Mon, Jan 26, 2015 at 10:22 AM, David E DeMarle
> <dave.demarle at kitware.com> wrote:
> > We want to document two things.
> >
> > 1) What version ranges the ParaView source code is compatible with.
> > 2) What specific versions were the Kitware binaries built so that people
> can
> > build and distribute plugins that work with them.
> >
> >
> > On Friday, January 23, 2015, Scott, W Alan <wascott at sandia.gov> wrote:
> >>
> >> Dan,
> >>
> >> OK, now we are saying that we have two locations that we document what
> >> versions of packages we use.  There are actually three, if you include
> >> inside the superbuild itself.  I strongly feel that there should be one
> >> location that everyone can go to when they want to know what version of
> >> packages are to be used.  Currently, these two locations are:
> >>
> >>
> >>
> >> http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisites
> >>
> >> and
> >>
> >> http://www.paraview.org/Wiki/ParaView_Binaries
> >>
> >>
> >>
> >> Alan
> >>
> >> p.s. ? not trying to shoot the messenger here ? thanks for the reply.
> My
> >> point is just that we should document the version of what builds with
> >> ParaView one place, having gone through weeks of hell building cgns.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> From: Dan Lipsa [mailto:dan.lipsa at kitware.com]
> >> Sent: Monday, January 12, 2015 8:57 PM
> >> To: Scott, W Alan
> >> Cc: David E DeMarle; Marcus D. Hanwell;
> paraview-developers at paraview.org
> >> Subject: Re: [Paraview-developers] [EXTERNAL] Re: CMake Version
> >>
> >>
> >>
> >> http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisites
> >>
> >>
> >>
> >> has the correct minimum version required for cmake 2.8.8.
> >>
> >>
> >>
> >> Dan
> >>
> >>
> >>
> >>
> >>
> >> On Fri, Jan 9, 2015 at 12:10 PM, Scott, W Alan <wascott at sandia.gov>
> wrote:
> >>
> >> I am hearing that it makes sense to leave current minimum cmake version
> >> for VTK.  That is OK with me.  It is also always good to know that you
> can
> >> always use latest/ greatest Cmake.  But, that isn?t true for all
> packages
> >> (and I believe latest Cmake has been incompatible in the past).  Let?s
> >> update the ParaView wiki to show what Cmake version is used for the
> builds?
> >> Surprisingly, upgrading Cmake versions isn?t trivial for some of us that
> >> build somewhere around a dozen platforms, and I don?t like having to
> guess
> >> what version to use...
> >>
> >>
> >>
> >> Thanks all!
> >>
> >>
> >>
> >> Alan
> >>
> >>
> >>
> >>
> >>
> >> From: Paraview-developers
> >> [mailto:paraview-developers-bounces at paraview.org] On Behalf Of David E
> >> DeMarle
> >> Sent: Friday, January 09, 2015 8:53 AM
> >> To: Marcus D. Hanwell
> >> Cc: paraview-developers at paraview.org
> >> Subject: [EXTERNAL] Re: [Paraview-developers] CMake Version
> >>
> >>
> >>
> >> If there isn't a compelling reason I think we should remain
> >> conservative, and it sounds like there is not in this case (especially
> >> for a dependency that is pretty optional for many of our users).
> >>
> >>
> >>
> >> Agreed. One factor in the minimum required decision is what the popular
> >> Linux distros have readily on hand.
> >>
> >>
> >>
> >> You
> >> can generally always use the latest CMake if you choose, but making
> >> that the minimum makes it harder for others to compile and use our
> >> code (often using the packaged CMake).
> >>
> >>
> >>
> >> Agreed again. The "faraway" submission in the dependencies track of the
> >> vtk dashboard exists to verity that CMake master works for VTK.
> >> Unfortunately it didn't submit today so someone needs to shove it.
> >>
> >>
> >>
> >> Marcus
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> Paraview-developers mailing list
> >> Paraview-developers at paraview.org
> >> http://public.kitware.com/mailman/listinfo/paraview-developers
> >>
> >>
> >
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Search the list archives at:
> > http://markmail.org/search/?q=Paraview-developers
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/paraview-developers
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150126/eb3ec7c9/attachment-0001.html>

From wascott at sandia.gov  Mon Jan 26 13:11:15 2015
From: wascott at sandia.gov (Scott, W Alan)
Date: Mon, 26 Jan 2015 18:11:15 +0000
Subject: [Paraview-developers] [EXTERNAL] Re:  CMake Version
In-Reply-To: <CANjZAi-zLua91unC8O8dLQwvQGZodyy7a0Y_CFSeMe7qFajwPA@mail.gmail.com>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
 <20150108150323.GA26903@megas.kitwarein.com>
 <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>
 <CANjZAi-+bT4DiLs6DcT_5=3okWzuC2c547mRnMC6TxgdDstqZQ@mail.gmail.com>
 <CADwGrVokKwcrmo4moRvz-Lu6v0_ybqBBHHuoH9Kkoc1Tqoub_Q@mail.gmail.com>
 <CAMkPkZWtwr7qvj+BWYD=FQowOwRQBuTbJAt-W3Cuz2Lfx=r_xw@mail.gmail.com>
 <CANjZAi98_=qEpfoARjmPn2u_fpKOCRSefZZFha=2A+Sdk=j-Gw@mail.gmail.com>
 <cc184e1a76ef4f23a73a09fb9f2da781@ES05AMSNLNT.srn.sandia.gov>
 <CADwGrVrGj0+3hx8rXEpgWZJexA0Naco2f2pqW1zOF2DS34G8qQ@mail.gmail.com>
 <85a21663f7ee46f1b5ce74390d175e8b@ES05AMSNLNT.srn.sandia.gov>
 <CANjZAi-=397KOE5G_-Lj7E5i-o3QR4kZe=mZOVRn6T9SxaWvYQ@mail.gmail.com>
 <CADHSJjDd2E+uC_umZ=nvi3eO9JeNa-e+n+eYH40Wm8PejGfhDw@mail.gmail.com>
 <CANjZAi-zLua91unC8O8dLQwvQGZodyy7a0Y_CFSeMe7qFajwPA@mail.gmail.com>
Message-ID: <898e5e3d6e5340858ad234ac2c310c0d@ES05AMSNLNT.srn.sandia.gov>

The downside of dropping the wikis is that they hold a lot of information that probably would not be found in code.  For instance, the Sandia tutorials are found there, along with the SC Tutorials.  We also have locations for the configuration files, and my release testing.

From: David E DeMarle [mailto:dave.demarle at kitware.com]
Sent: Monday, January 26, 2015 8:34 AM
To: Utkarsh Ayachit
Cc: Scott, W Alan; paraview-developers at paraview.org
Subject: [EXTERNAL] Re: [Paraview-developers] CMake Version

Sounds like a good idea to me, AS LONG AS the mechanics of finding and changing said information is easy to find and described well.


David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Mon, Jan 26, 2015 at 10:30 AM, Utkarsh Ayachit <utkarsh.ayachit at kitware.com<mailto:utkarsh.ayachit at kitware.com>> wrote:
I do see a bigger issue that Alan raises, which is a fair one. Wikis
have too much stale text! I keep wondering if we should drop the Wikis
entirely and go to documenting in code so it's easier to maintain. We
already have started documenting things like API changes, etc in the
Doxygen pages[1]. Maybe we should migrate everything there.

The one reason for Wikis is that its easier for external folks to
change. But if we move to github/gitlab workflow soon, people will be
able to edit files and create merge requests on the Web directly as
well. Hence those who are actually keep on editing the documentation
will indeed be able to.

What do folks think?

Utkarsh


[1] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/index.html

On Mon, Jan 26, 2015 at 10:22 AM, David E DeMarle
<dave.demarle at kitware.com<mailto:dave.demarle at kitware.com>> wrote:
> We want to document two things.
>
> 1) What version ranges the ParaView source code is compatible with.
> 2) What specific versions were the Kitware binaries built so that people can
> build and distribute plugins that work with them.
>
>
> On Friday, January 23, 2015, Scott, W Alan <wascott at sandia.gov<mailto:wascott at sandia.gov>> wrote:
>>
>> Dan,
>>
>> OK, now we are saying that we have two locations that we document what
>> versions of packages we use.  There are actually three, if you include
>> inside the superbuild itself.  I strongly feel that there should be one
>> location that everyone can go to when they want to know what version of
>> packages are to be used.  Currently, these two locations are:
>>
>>
>>
>> http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisites
>>
>> and
>>
>> http://www.paraview.org/Wiki/ParaView_Binaries
>>
>>
>>
>> Alan
>>
>> p.s. ? not trying to shoot the messenger here ? thanks for the reply.  My
>> point is just that we should document the version of what builds with
>> ParaView one place, having gone through weeks of hell building cgns.
>>
>>
>>
>>
>>
>>
>>
>> From: Dan Lipsa [mailto:dan.lipsa at kitware.com<mailto:dan.lipsa at kitware.com>]
>> Sent: Monday, January 12, 2015 8:57 PM
>> To: Scott, W Alan
>> Cc: David E DeMarle; Marcus D. Hanwell; paraview-developers at paraview.org<mailto:paraview-developers at paraview.org>
>> Subject: Re: [Paraview-developers] [EXTERNAL] Re: CMake Version
>>
>>
>>
>> http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisites
>>
>>
>>
>> has the correct minimum version required for cmake 2.8.8.
>>
>>
>>
>> Dan
>>
>>
>>
>>
>>
>> On Fri, Jan 9, 2015 at 12:10 PM, Scott, W Alan <wascott at sandia.gov<mailto:wascott at sandia.gov>> wrote:
>>
>> I am hearing that it makes sense to leave current minimum cmake version
>> for VTK.  That is OK with me.  It is also always good to know that you can
>> always use latest/ greatest Cmake.  But, that isn?t true for all packages
>> (and I believe latest Cmake has been incompatible in the past).  Let?s
>> update the ParaView wiki to show what Cmake version is used for the builds?
>> Surprisingly, upgrading Cmake versions isn?t trivial for some of us that
>> build somewhere around a dozen platforms, and I don?t like having to guess
>> what version to use...
>>
>>
>>
>> Thanks all!
>>
>>
>>
>> Alan
>>
>>
>>
>>
>>
>> From: Paraview-developers
>> [mailto:paraview-developers-bounces at paraview.org<mailto:paraview-developers-bounces at paraview.org>] On Behalf Of David E
>> DeMarle
>> Sent: Friday, January 09, 2015 8:53 AM
>> To: Marcus D. Hanwell
>> Cc: paraview-developers at paraview.org<mailto:paraview-developers at paraview.org>
>> Subject: [EXTERNAL] Re: [Paraview-developers] CMake Version
>>
>>
>>
>> If there isn't a compelling reason I think we should remain
>> conservative, and it sounds like there is not in this case (especially
>> for a dependency that is pretty optional for many of our users).
>>
>>
>>
>> Agreed. One factor in the minimum required decision is what the popular
>> Linux distros have readily on hand.
>>
>>
>>
>> You
>> can generally always use the latest CMake if you choose, but making
>> that the minimum makes it harder for others to compile and use our
>> code (often using the packaged CMake).
>>
>>
>>
>> Agreed again. The "faraway" submission in the dependencies track of the
>> vtk dashboard exists to verity that CMake master works for VTK.
>> Unfortunately it didn't submit today so someone needs to shove it.
>>
>>
>>
>> Marcus
>>
>>
>>
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org<mailto:Paraview-developers at paraview.org>
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>>
>
>
> _______________________________________________
> Powered by www.kitware.com<http://www.kitware.com>
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150126/175c1cfd/attachment.html>

From utkarsh.ayachit at kitware.com  Mon Jan 26 13:15:05 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Mon, 26 Jan 2015 13:15:05 -0500
Subject: [Paraview-developers] [EXTERNAL] Re:  CMake Version
In-Reply-To: <898e5e3d6e5340858ad234ac2c310c0d@ES05AMSNLNT.srn.sandia.gov>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
 <20150108150323.GA26903@megas.kitwarein.com>
 <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>
 <CANjZAi-+bT4DiLs6DcT_5=3okWzuC2c547mRnMC6TxgdDstqZQ@mail.gmail.com>
 <CADwGrVokKwcrmo4moRvz-Lu6v0_ybqBBHHuoH9Kkoc1Tqoub_Q@mail.gmail.com>
 <CAMkPkZWtwr7qvj+BWYD=FQowOwRQBuTbJAt-W3Cuz2Lfx=r_xw@mail.gmail.com>
 <CANjZAi98_=qEpfoARjmPn2u_fpKOCRSefZZFha=2A+Sdk=j-Gw@mail.gmail.com>
 <cc184e1a76ef4f23a73a09fb9f2da781@ES05AMSNLNT.srn.sandia.gov>
 <CADwGrVrGj0+3hx8rXEpgWZJexA0Naco2f2pqW1zOF2DS34G8qQ@mail.gmail.com>
 <85a21663f7ee46f1b5ce74390d175e8b@ES05AMSNLNT.srn.sandia.gov>
 <CANjZAi-=397KOE5G_-Lj7E5i-o3QR4kZe=mZOVRn6T9SxaWvYQ@mail.gmail.com>
 <CADHSJjDd2E+uC_umZ=nvi3eO9JeNa-e+n+eYH40Wm8PejGfhDw@mail.gmail.com>
 <CANjZAi-zLua91unC8O8dLQwvQGZodyy7a0Y_CFSeMe7qFajwPA@mail.gmail.com>
 <898e5e3d6e5340858ad234ac2c310c0d@ES05AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjAGecu4k=4_8Dxx8Fb7redqcsa9nhCytnvMhRXbBFiURw@mail.gmail.com>

Alan,

Yes, good point. Wikis should still have a place to store such
resources. Maybe the Wiki won't disappear entirely, but will stop
being "the" resource for all documentation. It should probably be a
place for "additional documentation and resources" with all the
essential ones moving to the source.

Utkarsh

On Mon, Jan 26, 2015 at 1:11 PM, Scott, W Alan <wascott at sandia.gov> wrote:
> The downside of dropping the wikis is that they hold a lot of information
> that probably would not be found in code.  For instance, the Sandia
> tutorials are found there, along with the SC Tutorials.  We also have
> locations for the configuration files, and my release testing.
>
>
>
> From: David E DeMarle [mailto:dave.demarle at kitware.com]
> Sent: Monday, January 26, 2015 8:34 AM
> To: Utkarsh Ayachit
> Cc: Scott, W Alan; paraview-developers at paraview.org
>
>
> Subject: [EXTERNAL] Re: [Paraview-developers] CMake Version
>
>
>
> Sounds like a good idea to me, AS LONG AS the mechanics of finding and
> changing said information is easy to find and described well.
>
>
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
>
>
> On Mon, Jan 26, 2015 at 10:30 AM, Utkarsh Ayachit
> <utkarsh.ayachit at kitware.com> wrote:
>
> I do see a bigger issue that Alan raises, which is a fair one. Wikis
> have too much stale text! I keep wondering if we should drop the Wikis
> entirely and go to documenting in code so it's easier to maintain. We
> already have started documenting things like API changes, etc in the
> Doxygen pages[1]. Maybe we should migrate everything there.
>
> The one reason for Wikis is that its easier for external folks to
> change. But if we move to github/gitlab workflow soon, people will be
> able to edit files and create merge requests on the Web directly as
> well. Hence those who are actually keep on editing the documentation
> will indeed be able to.
>
> What do folks think?
>
> Utkarsh
>
>
> [1] http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/index.html
>
>
> On Mon, Jan 26, 2015 at 10:22 AM, David E DeMarle
> <dave.demarle at kitware.com> wrote:
>> We want to document two things.
>>
>> 1) What version ranges the ParaView source code is compatible with.
>> 2) What specific versions were the Kitware binaries built so that people
>> can
>> build and distribute plugins that work with them.
>>
>>
>> On Friday, January 23, 2015, Scott, W Alan <wascott at sandia.gov> wrote:
>>>
>>> Dan,
>>>
>>> OK, now we are saying that we have two locations that we document what
>>> versions of packages we use.  There are actually three, if you include
>>> inside the superbuild itself.  I strongly feel that there should be one
>>> location that everyone can go to when they want to know what version of
>>> packages are to be used.  Currently, these two locations are:
>>>
>>>
>>>
>>> http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisites
>>>
>>> and
>>>
>>> http://www.paraview.org/Wiki/ParaView_Binaries
>>>
>>>
>>>
>>> Alan
>>>
>>> p.s. ? not trying to shoot the messenger here ? thanks for the reply.  My
>>> point is just that we should document the version of what builds with
>>> ParaView one place, having gone through weeks of hell building cgns.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> From: Dan Lipsa [mailto:dan.lipsa at kitware.com]
>>> Sent: Monday, January 12, 2015 8:57 PM
>>> To: Scott, W Alan
>>> Cc: David E DeMarle; Marcus D. Hanwell; paraview-developers at paraview.org
>>> Subject: Re: [Paraview-developers] [EXTERNAL] Re: CMake Version
>>>
>>>
>>>
>>> http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisites
>>>
>>>
>>>
>>> has the correct minimum version required for cmake 2.8.8.
>>>
>>>
>>>
>>> Dan
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Jan 9, 2015 at 12:10 PM, Scott, W Alan <wascott at sandia.gov>
>>> wrote:
>>>
>>> I am hearing that it makes sense to leave current minimum cmake version
>>> for VTK.  That is OK with me.  It is also always good to know that you
>>> can
>>> always use latest/ greatest Cmake.  But, that isn?t true for all packages
>>> (and I believe latest Cmake has been incompatible in the past).  Let?s
>>> update the ParaView wiki to show what Cmake version is used for the
>>> builds?
>>> Surprisingly, upgrading Cmake versions isn?t trivial for some of us that
>>> build somewhere around a dozen platforms, and I don?t like having to
>>> guess
>>> what version to use...
>>>
>>>
>>>
>>> Thanks all!
>>>
>>>
>>>
>>> Alan
>>>
>>>
>>>
>>>
>>>
>>> From: Paraview-developers
>>> [mailto:paraview-developers-bounces at paraview.org] On Behalf Of David E
>>> DeMarle
>>> Sent: Friday, January 09, 2015 8:53 AM
>>> To: Marcus D. Hanwell
>>> Cc: paraview-developers at paraview.org
>>> Subject: [EXTERNAL] Re: [Paraview-developers] CMake Version
>>>
>>>
>>>
>>> If there isn't a compelling reason I think we should remain
>>> conservative, and it sounds like there is not in this case (especially
>>> for a dependency that is pretty optional for many of our users).
>>>
>>>
>>>
>>> Agreed. One factor in the minimum required decision is what the popular
>>> Linux distros have readily on hand.
>>>
>>>
>>>
>>> You
>>> can generally always use the latest CMake if you choose, but making
>>> that the minimum makes it harder for others to compile and use our
>>> code (often using the packaged CMake).
>>>
>>>
>>>
>>> Agreed again. The "faraway" submission in the dependencies track of the
>>> vtk dashboard exists to verity that CMake master works for VTK.
>>> Unfortunately it didn't submit today so someone needs to shove it.
>>>
>>>
>>>
>>> Marcus
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Paraview-developers mailing list
>>> Paraview-developers at paraview.org
>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>
>>>
>>
>>
>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Search the list archives at:
>> http://markmail.org/search/?q=Paraview-developers
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>
>

From pnav at tacc.utexas.edu  Mon Jan 26 11:13:08 2015
From: pnav at tacc.utexas.edu (Paul Navratil)
Date: Mon, 26 Jan 2015 16:13:08 +0000
Subject: [Paraview-developers] EGPGV 2015 Call for Papers
Message-ID: <D1098040-8F6E-494C-8B4A-B97E73BD5E2B@tacc.utexas.edu>

Hello ParaView Developers,

Please excuse the shameless plug, but I would like to remind everyone that the EGPGV submission deadline is three weeks away.
We have received strong submissions from the ParaView community in the past, and I hope that you all will consider submitting.

Please note that we also are featuring a new Visualization Showcase short papers track for state-of-the-art application of visualization techniques to interesting problems.
The deadline for this track is later, so there is more time to get the video in perfect shape :-)

All best,

Paul Navratil
Texas Advanced Computing Center

=================================================================

                E G P G V   2015
Eurographics Symposium on Parallel Graphics and Visualization
       25 - 26 May, Cagliari, Sardinia, Italy

       *** EGPGV 2015 - Call for Papers ***

Welcome to the 15th EGPGV, the Eurographics Symposium on
Parallel Graphics and Visualization. The event will take place
on May 25 - 26 in Cagliari, island of Sardinia, Italy.
The Symposium will be held in conjunction with EuroVis 2015.

*** NOTE: there are two tracks for this year?s symposium, full papers
and visualization showcase short papers ***

The importance of parallel computing is increasing rapidly with the
ubiquitous availability of multi-core CPUs, GPUs, and cluster systems.
Computationally demanding and data-intensive applications in graphics
and visualization are strongly affected by this trend and require novel
efficient parallel solutions. The aim of this symposium is to foster the
exchange of experiences and knowledge exploiting and defining new trends
in parallel graphics and visualization.

The proceedings of the EGPGV Symposium will be published in the
Eurographics Proceedings Series and in the Eurographics Digital Library.


Focusing on parallel computing, the symposium seeks papers on graphics
and visualization techniques, data structures, algorithms, and systems for:

 * large-data
 * clusters
 * (multi-)GPU computing, and heterogeneous, hybrid architectures
 * out-of-core
 * hybrid distributed and shared memory architectures
 * grid and cloud environments



In particular the symposium topics include:

 * computationally and data intensive rendering
 * scientific visualization (volume rendering, flow and tensor
   visualization)
 * information visualization and visual analytics
 * simulations for virtual environments (physics-based animation,
   collision detection, acoustic)
 * mesh processing, level-of-detail, and geometric methods
 * visual computing (image- and video-based rendering, image processing
   and exploitation, segmentation)
 * scheduling, memory management and data coherence
 * large and high resolution displays, virtual environments
 * scientific, engineering, and industrial applications


Full papers are expected to be eight to ten (8-10) pages in length, with
the final length appropriate to the contribution of the paper. Papers
should be submitted using the Eurographics Conference style
<https://srmv2.eg.org/COMFy/Conference/PGV_2015/GetConferenceFile?fileID=6146> (https://srmv2.eg.org/COMFy/Conference/PGV_2015/GetConferenceFile?fileID=6146).
Please use this linked version, which contains the correct details for
EGPGV.

The expected schedule is as follows:

 * Full Paper Due: February 13, 2014
 * Author Notification: March 27, 2014
 * Camera-Ready Paper Due: April 8, 2014


The best paper will be invited to submit an extended version to IEEE
Transactions on Visualization and Computer Graphics (TVCG).


   Scientific Visualization Showcase

This year we present a new track for EGPGV 2015, which provides a forum
for the year's most instrumental movies in parallel graphics and
visualization. Finalists will compete for the Best Visualization Award,
and each finalist will present his or her movie during a dedicated
session at EGPGV ?15 in a 10-minute presentation. Movies are judged
based on how their movie illuminates science, by the quality of the
movie, and for innovations in the process used for creating the movie.

The accepted submissions will appear as short papers in the symposium
proceedings.

Review and selection process:
Submission should include ?Visualization Showcase:? at the beginning of
the paper title. Submissions needed to include a movie (up to 150MB in
size) and a short paper (up to 4 pages including references). The short
paper should describe the scientific story conveyed by the movie, how
the visualization helps scientific discovery, and the
"state-of-the-practice" information behind making the movie. The short
paper should be submitted using the Eurographics Conference style
<https://srmv2.eg.org/COMFy/Conference/PGV_2015/GetConferenceFile?fileID=6146> (https://srmv2.eg.org/COMFy/Conference/PGV_2015/GetConferenceFile?fileID=6146).
Please use this linked version, which contains the correct details for
EGPGV.

Each submission will be peer reviewed by the EGPGV Paper Chairs.
Criteria for revision include:

1. Compelling visualization
2. Visualizing data involving parallel graphics and/or visualization in
   a significant way (e.g., data size, parallel processing, parallel
   rendering)
3. Meaningful and compelling science story
4. Description of visualization techniques necessary to accomplish the
   movie


The expected schedule is as follows:

 * Showcase Submission Due: February 28, 2014
 * Author Notification: March 27, 2014
 * Camera-Ready Paper Due: April 8, 2014
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150126/31e31fd4/attachment.html>

From wascott at sandia.gov  Mon Jan 26 13:46:50 2015
From: wascott at sandia.gov (Scott, W Alan)
Date: Mon, 26 Jan 2015 18:46:50 +0000
Subject: [Paraview-developers] [EXTERNAL] Re:  CMake Version
In-Reply-To: <CADHSJjAGecu4k=4_8Dxx8Fb7redqcsa9nhCytnvMhRXbBFiURw@mail.gmail.com>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
 <20150108150323.GA26903@megas.kitwarein.com>
 <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>
 <CANjZAi-+bT4DiLs6DcT_5=3okWzuC2c547mRnMC6TxgdDstqZQ@mail.gmail.com>
 <CADwGrVokKwcrmo4moRvz-Lu6v0_ybqBBHHuoH9Kkoc1Tqoub_Q@mail.gmail.com>
 <CAMkPkZWtwr7qvj+BWYD=FQowOwRQBuTbJAt-W3Cuz2Lfx=r_xw@mail.gmail.com>
 <CANjZAi98_=qEpfoARjmPn2u_fpKOCRSefZZFha=2A+Sdk=j-Gw@mail.gmail.com>
 <cc184e1a76ef4f23a73a09fb9f2da781@ES05AMSNLNT.srn.sandia.gov>
 <CADwGrVrGj0+3hx8rXEpgWZJexA0Naco2f2pqW1zOF2DS34G8qQ@mail.gmail.com>
 <85a21663f7ee46f1b5ce74390d175e8b@ES05AMSNLNT.srn.sandia.gov>
 <CANjZAi-=397KOE5G_-Lj7E5i-o3QR4kZe=mZOVRn6T9SxaWvYQ@mail.gmail.com>
 <CADHSJjDd2E+uC_umZ=nvi3eO9JeNa-e+n+eYH40Wm8PejGfhDw@mail.gmail.com>
 <CANjZAi-zLua91unC8O8dLQwvQGZodyy7a0Y_CFSeMe7qFajwPA@mail.gmail.com>
 <898e5e3d6e5340858ad234ac2c310c0d@ES05AMSNLNT.srn.sandia.gov>
 <CADHSJjAGecu4k=4_8Dxx8Fb7redqcsa9nhCytnvMhRXbBFiURw@mail.gmail.com>
Message-ID: <6ec4f5e796ad47039631fa535a936105@ES05AMSNLNT.srn.sandia.gov>

Two thoughts:
* Seems to me there is source level information (builds, version numbers, supporting libraries, etc.).  This can live either place.  Second, there is non source/executable level info, such as tutorials, python script snippets, etc.  This should live in a wiki.
* I believe the base issue I brought up is that we have information held in multiple locations, and it gets out of date.  I don't see how moving documentation into the code would make it any more likely to be updated.

No matter where it is located, we probably need a procedure for releases, that includes updating the version number documentation.

Alan

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: Monday, January 26, 2015 11:15 AM
To: Scott, W Alan
Cc: David E DeMarle; paraview-developers at paraview.org
Subject: Re: [EXTERNAL] Re: [Paraview-developers] CMake Version

Alan,

Yes, good point. Wikis should still have a place to store such resources. Maybe the Wiki won't disappear entirely, but will stop being "the" resource for all documentation. It should probably be a place for "additional documentation and resources" with all the essential ones moving to the source.

Utkarsh

On Mon, Jan 26, 2015 at 1:11 PM, Scott, W Alan <wascott at sandia.gov> wrote:
> The downside of dropping the wikis is that they hold a lot of 
> information that probably would not be found in code.  For instance, 
> the Sandia tutorials are found there, along with the SC Tutorials.  We 
> also have locations for the configuration files, and my release testing.
>
>
>
> From: David E DeMarle [mailto:dave.demarle at kitware.com]
> Sent: Monday, January 26, 2015 8:34 AM
> To: Utkarsh Ayachit
> Cc: Scott, W Alan; paraview-developers at paraview.org
>
>
> Subject: [EXTERNAL] Re: [Paraview-developers] CMake Version
>
>
>
> Sounds like a good idea to me, AS LONG AS the mechanics of finding and 
> changing said information is easy to find and described well.
>
>
>
>
> David E DeMarle
> Kitware, Inc.
> R&D Engineer
> 21 Corporate Drive
> Clifton Park, NY 12065-8662
> Phone: 518-881-4909
>
>
>
> On Mon, Jan 26, 2015 at 10:30 AM, Utkarsh Ayachit 
> <utkarsh.ayachit at kitware.com> wrote:
>
> I do see a bigger issue that Alan raises, which is a fair one. Wikis 
> have too much stale text! I keep wondering if we should drop the Wikis 
> entirely and go to documenting in code so it's easier to maintain. We 
> already have started documenting things like API changes, etc in the 
> Doxygen pages[1]. Maybe we should migrate everything there.
>
> The one reason for Wikis is that its easier for external folks to 
> change. But if we move to github/gitlab workflow soon, people will be 
> able to edit files and create merge requests on the Web directly as 
> well. Hence those who are actually keep on editing the documentation 
> will indeed be able to.
>
> What do folks think?
>
> Utkarsh
>
>
> [1] 
> http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/index.html
>
>
> On Mon, Jan 26, 2015 at 10:22 AM, David E DeMarle 
> <dave.demarle at kitware.com> wrote:
>> We want to document two things.
>>
>> 1) What version ranges the ParaView source code is compatible with.
>> 2) What specific versions were the Kitware binaries built so that 
>> people can build and distribute plugins that work with them.
>>
>>
>> On Friday, January 23, 2015, Scott, W Alan <wascott at sandia.gov> wrote:
>>>
>>> Dan,
>>>
>>> OK, now we are saying that we have two locations that we document 
>>> what versions of packages we use.  There are actually three, if you 
>>> include inside the superbuild itself.  I strongly feel that there 
>>> should be one location that everyone can go to when they want to 
>>> know what version of packages are to be used.  Currently, these two locations are:
>>>
>>>
>>>
>>> http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisite
>>> s
>>>
>>> and
>>>
>>> http://www.paraview.org/Wiki/ParaView_Binaries
>>>
>>>
>>>
>>> Alan
>>>
>>> p.s. ? not trying to shoot the messenger here ? thanks for the 
>>> reply.  My point is just that we should document the version of what 
>>> builds with ParaView one place, having gone through weeks of hell building cgns.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> From: Dan Lipsa [mailto:dan.lipsa at kitware.com]
>>> Sent: Monday, January 12, 2015 8:57 PM
>>> To: Scott, W Alan
>>> Cc: David E DeMarle; Marcus D. Hanwell; 
>>> paraview-developers at paraview.org
>>> Subject: Re: [Paraview-developers] [EXTERNAL] Re: CMake Version
>>>
>>>
>>>
>>> http://www.paraview.org/Wiki/ParaView:Build_And_Install#Prerequisite
>>> s
>>>
>>>
>>>
>>> has the correct minimum version required for cmake 2.8.8.
>>>
>>>
>>>
>>> Dan
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Jan 9, 2015 at 12:10 PM, Scott, W Alan <wascott at sandia.gov>
>>> wrote:
>>>
>>> I am hearing that it makes sense to leave current minimum cmake 
>>> version for VTK.  That is OK with me.  It is also always good to 
>>> know that you can always use latest/ greatest Cmake.  But, that 
>>> isn?t true for all packages (and I believe latest Cmake has been 
>>> incompatible in the past).  Let?s update the ParaView wiki to show 
>>> what Cmake version is used for the builds?
>>> Surprisingly, upgrading Cmake versions isn?t trivial for some of us 
>>> that build somewhere around a dozen platforms, and I don?t like 
>>> having to guess what version to use...
>>>
>>>
>>>
>>> Thanks all!
>>>
>>>
>>>
>>> Alan
>>>
>>>
>>>
>>>
>>>
>>> From: Paraview-developers
>>> [mailto:paraview-developers-bounces at paraview.org] On Behalf Of David 
>>> E DeMarle
>>> Sent: Friday, January 09, 2015 8:53 AM
>>> To: Marcus D. Hanwell
>>> Cc: paraview-developers at paraview.org
>>> Subject: [EXTERNAL] Re: [Paraview-developers] CMake Version
>>>
>>>
>>>
>>> If there isn't a compelling reason I think we should remain 
>>> conservative, and it sounds like there is not in this case 
>>> (especially for a dependency that is pretty optional for many of our users).
>>>
>>>
>>>
>>> Agreed. One factor in the minimum required decision is what the 
>>> popular Linux distros have readily on hand.
>>>
>>>
>>>
>>> You
>>> can generally always use the latest CMake if you choose, but making 
>>> that the minimum makes it harder for others to compile and use our 
>>> code (often using the packaged CMake).
>>>
>>>
>>>
>>> Agreed again. The "faraway" submission in the dependencies track of 
>>> the vtk dashboard exists to verity that CMake master works for VTK.
>>> Unfortunately it didn't submit today so someone needs to shove it.
>>>
>>>
>>>
>>> Marcus
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Paraview-developers mailing list
>>> Paraview-developers at paraview.org
>>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>>
>>>
>>
>>
>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at 
>> http://www.kitware.com/opensource/opensource.html
>>
>> Search the list archives at:
>> http://markmail.org/search/?q=Paraview-developers
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>
>

From utkarsh.ayachit at kitware.com  Tue Jan 27 11:50:49 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Tue, 27 Jan 2015 11:50:49 -0500
Subject: [Paraview-developers] [EXTERNAL] Re:  CMake Version
In-Reply-To: <6ec4f5e796ad47039631fa535a936105@ES05AMSNLNT.srn.sandia.gov>
References: <f8306c2d22754a689710de217c06f1d5@ES05AMSNLNT.srn.sandia.gov>
 <CAEbtaO0xUnXQeSoFk4RB1TX7RunerMTxJkopTMSvak6p9Hs3RQ@mail.gmail.com>
 <CAJk8dSBP9gaFdvgEemJ0WaDGVffu9V7h=RgZkZiEPbsLeSg1mQ@mail.gmail.com>
 <20150108150323.GA26903@megas.kitwarein.com>
 <CADwGrVq2aa879TdSut75=of=4om8SHYK2ZcF+ewPrQABony4NQ@mail.gmail.com>
 <CANjZAi-+bT4DiLs6DcT_5=3okWzuC2c547mRnMC6TxgdDstqZQ@mail.gmail.com>
 <CADwGrVokKwcrmo4moRvz-Lu6v0_ybqBBHHuoH9Kkoc1Tqoub_Q@mail.gmail.com>
 <CAMkPkZWtwr7qvj+BWYD=FQowOwRQBuTbJAt-W3Cuz2Lfx=r_xw@mail.gmail.com>
 <CANjZAi98_=qEpfoARjmPn2u_fpKOCRSefZZFha=2A+Sdk=j-Gw@mail.gmail.com>
 <cc184e1a76ef4f23a73a09fb9f2da781@ES05AMSNLNT.srn.sandia.gov>
 <CADwGrVrGj0+3hx8rXEpgWZJexA0Naco2f2pqW1zOF2DS34G8qQ@mail.gmail.com>
 <85a21663f7ee46f1b5ce74390d175e8b@ES05AMSNLNT.srn.sandia.gov>
 <CANjZAi-=397KOE5G_-Lj7E5i-o3QR4kZe=mZOVRn6T9SxaWvYQ@mail.gmail.com>
 <CADHSJjDd2E+uC_umZ=nvi3eO9JeNa-e+n+eYH40Wm8PejGfhDw@mail.gmail.com>
 <CANjZAi-zLua91unC8O8dLQwvQGZodyy7a0Y_CFSeMe7qFajwPA@mail.gmail.com>
 <898e5e3d6e5340858ad234ac2c310c0d@ES05AMSNLNT.srn.sandia.gov>
 <CADHSJjAGecu4k=4_8Dxx8Fb7redqcsa9nhCytnvMhRXbBFiURw@mail.gmail.com>
 <6ec4f5e796ad47039631fa535a936105@ES05AMSNLNT.srn.sandia.gov>
Message-ID: <CADHSJjC1+ZLcB1rJvp7Ex8JJ=YNGyqnwW+cTdnZ72EJ8JKdzsg@mail.gmail.com>

> Two thoughts:
> * Seems to me there is source level information (builds, version numbers, supporting libraries, etc.).  This can live either place.  Second, there is non source/executable level info, such as tutorials, python script snippets, etc.  This should live in a wiki.

Seems reasonable.

> * I believe the base issue I brought up is that we have information held in multiple locations, and it gets out of date.  I don't see how moving documentation into the code would make it any more likely to be updated.

My intuition is that when we move the documentation to code, it will
be more discoverable for the developers. Right now, when someone
changes a CMake variable, for example, the developer doesn't know
which all pages on the Wiki need to be updated. If its in the code, it
will be easier to locate. Secondly, we are going to a stricter review
based commit-system for ParaView (like VTK). If the documentation is
in the source dir, it will be easier for reviewers to block merge
requests that change/add  things like build flags etc. without
updating the corresponding documentation -- same reason why we think
moving the ParaView Guide to the source instead of the WIki should be
useful.

> No matter where it is located, we probably need a procedure for releases, that includes updating the version number documentation.

In source documentation will make versioning easier. I am still not
sure how to version documents on Wikis.

Utkarsh

From Anton.Piccardo-Selg at tessella.com  Wed Jan 28 04:37:04 2015
From: Anton.Piccardo-Selg at tessella.com (Anton.Piccardo-Selg at tessella.com)
Date: Wed, 28 Jan 2015 09:37:04 +0000
Subject: [Paraview-developers] Issue with invisible source and deleting
	filter.
Message-ID: <OFB5EBDF13.2ADD71A8-ON80257DDB.0031A1AD-80257DDB.0034D53E@tessella.co.uk>

An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150128/34611456/attachment.html>

From Joshua.Murphy at lasp.colorado.edu  Wed Jan 28 15:01:30 2015
From: Joshua.Murphy at lasp.colorado.edu (Joshua Murphy)
Date: Wed, 28 Jan 2015 13:01:30 -0700
Subject: [Paraview-developers] Super build Problem
Message-ID: <7B37CE47-6799-4D99-8904-33DA1E8153CE@lasp.colorado.edu>

I have posted this question once before, but everyone was probably busy with the 4.3.1 release? So here goes again.

I am trying to build the superbuild on the NCAR visualization cluster Caldera for development work.  I need to build 4.1.0, as I have not yet had time to update my tools to the most recent release.

When I attempt to build the superbuild, I get an error building Freetype (see below).

I have not been able to figure out what is causing the build error.

I am using the gnu/4.6.4 module, the cmake/3.0.2 module, and the gmake/4.1 module.

If anyone can help, that would be great.

Thanks,
Josh







?????
[ 31%] Performing build step for 'freetype'
LD_LIBRARY_PATH = /glade/u/home/jmurphy/Developer/paraview/build/install/lib:/glade/apps/opt/gnu/4.6.4/lib64:/glade/apps/opt/gnu/lib:/glade/apps/opt/gnu/4.6.4/lib64:/glade/apps/opt/gnu/lib
libtool: compile:  gcc -pedantic -ansi -fPIC -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/builds/unix -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/include -c -Wall -fPIC -DFT_CONFIG_OPTION_SYSTEM_ZLIB -DFT_CONFIG_OPTION_USE_BZIP2 "-DFT_CONFIG_CONFIG_H=<ftconfig.h>" -DFT2_BUILD_LIBRARY "-DFT_CONFIG_MODULES_H=<ftmodule.h>" /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base/ftinit.c  -fPIC -DPIC -o /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/.libs/ftinit.o
libtool: compile:  gcc -pedantic -ansi -fPIC -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/builds/unix -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/include -c -Wall -fPIC -DFT_CONFIG_OPTION_SYSTEM_ZLIB -DFT_CONFIG_OPTION_USE_BZIP2 "-DFT_CONFIG_CONFIG_H=<ftconfig.h>" -DFT2_BUILD_LIBRARY "-DFT_CONFIG_MODULES_H=<ftmodule.h>" /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/builds/unix/ftsystem.c  -fPIC -DPIC -o /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/.libs/ftsystem.o
libtool: compile:  gcc -pedantic -ansi -fPIC -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/builds/unix -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/include -c -Wall -fPIC -DFT_CONFIG_OPTION_SYSTEM_ZLIB -DFT_CONFIG_OPTION_USE_BZIP2 "-DFT_CONFIG_CONFIG_H=<ftconfig.h>" -DFT2_BUILD_LIBRARY "-DFT_CONFIG_MODULES_H=<ftmodule.h>" /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base/ftdebug.c  -fPIC -DPIC -o /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/.libs/ftdebug.o
libtool: compile:  gcc -pedantic -ansi -fPIC -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/builds/unix -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/include -c -Wall -fPIC -DFT_CONFIG_OPTION_SYSTEM_ZLIB -DFT_CONFIG_OPTION_USE_BZIP2 "-DFT_CONFIG_CONFIG_H=<ftconfig.h>" -DFT2_BUILD_LIBRARY "-DFT_CONFIG_MODULES_H=<ftmodule.h>" -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base/ftbase.c  -fPIC -DPIC -o /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/.libs/ftbase.o
libtool: compile:  gcc -pedantic -ansi -fPIC -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/builds/unix -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/include -c -Wall -fPIC -DFT_CONFIG_OPTION_SYSTEM_ZLIB -DFT_CONFIG_OPTION_USE_BZIP2 "-DFT_CONFIG_CONFIG_H=<ftconfig.h>" -DFT2_BUILD_LIBRARY "-DFT_CONFIG_MODULES_H=<ftmodule.h>" -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base/ftbbox.c  -fPIC -DPIC -o /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/.libs/ftbbox.o
/glade/apps/opt/modulefiles/ys/cmpwrappers/gcc[52]: eval[1]: -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base: cannot create [No such file or directory]
/glade/apps/opt/modulefiles/ys/cmpwrappers/gcc[52]: eval[1]: -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base: cannot create [No such file or directory]
gmake[3]: *** [/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/ftbase.lo] Error 1
/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base/rules.mk:87: recipe for target '/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/ftbase.lo' failed
gmake[3]: *** Waiting for unfinished jobs....
gmake[3]: *** [/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/ftbbox.lo] Error 1
/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base/rules.mk:93: recipe for target '/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/ftbbox.lo' failed
libtool: compile:  gcc -pedantic -ansi -fPIC -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/builds/unix -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/include -c -Wall -fPIC -DFT_CONFIG_OPTION_SYSTEM_ZLIB -DFT_CONFIG_OPTION_USE_BZIP2 "-DFT_CONFIG_CONFIG_H=<ftconfig.h>" -DFT2_BUILD_LIBRARY "-DFT_CONFIG_MODULES_H=<ftmodule.h>" -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base/ftbdf.c  -fPIC -DPIC -o /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/.libs/ftbdf.o
libtool: compile:  gcc -pedantic -ansi -fPIC -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/builds/unix -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/include -c -Wall -fPIC -DFT_CONFIG_OPTION_SYSTEM_ZLIB -DFT_CONFIG_OPTION_USE_BZIP2 "-DFT_CONFIG_CONFIG_H=<ftconfig.h>" -DFT2_BUILD_LIBRARY "-DFT_CONFIG_MODULES_H=<ftmodule.h>" -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base/ftbitmap.c  -fPIC -DPIC -o /glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/.libs/ftbitmap.o
/glade/apps/opt/modulefiles/ys/cmpwrappers/gcc[52]: eval[1]: -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base: cannot create [No such file or directory]
gmake[3]: *** [/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/ftbdf.lo] Error 1
/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base/rules.mk:93: recipe for target '/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/ftbdf.lo' failed
/glade/apps/opt/modulefiles/ys/cmpwrappers/gcc[52]: eval[1]: -I/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base: cannot create [No such file or directory]
gmake[3]: *** [/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/ftbitmap.lo] Error 1
/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype/src/base/rules.mk:93: recipe for target '/glade/u/home/jmurphy/Developer/paraview/build/freetype/src/freetype-build/ftbitmap.lo' failed
CMake Error at /glade/u/home/jmurphy/Developer/paraview/build/pv-freetype-build.cmake:26 (message):
  Failed!!!


CMakeFiles/freetype.dir/build.make:110: recipe for target 'freetype/src/freetype-stamp/freetype-build' failed
gmake[2]: *** [freetype/src/freetype-stamp/freetype-build] Error 1
CMakeFiles/Makefile2:964: recipe for target 'CMakeFiles/freetype.dir/all' failed
gmake[1]: *** [CMakeFiles/freetype.dir/all] Error 2
Makefile:147: recipe for target 'all' failed
gmake: *** [all] Error 2


From utkarsh.ayachit at kitware.com  Thu Jan 29 08:08:37 2015
From: utkarsh.ayachit at kitware.com (Utkarsh Ayachit)
Date: Thu, 29 Jan 2015 08:08:37 -0500
Subject: [Paraview-developers] Gatekeeper Review Summary
Message-ID: <CADHSJjB7f4hDiBZPv0-GdjM7R0emEo1DkiMCBgnUFuOdCqLwMw@mail.gmail.com>

Topics merged into master (v4.3.1-83-gf35be3b):
        14953_fix_Esc_key_in_settings_dialog
        14957_fix_settings_segfault
        15031_fix_multicore_mode
        15283_fix_camera_settings_importation
        15293-guard-interactive-rendering
        bag-plot
        cosmotools-filters-xml
        fix_mpi_link_issues
(VTK)   output-window-15240
(VTK)   pvweb-loadsave-state-and-save-data
        pvweb-merge-sources-filters

From ben.boeckel at kitware.com  Thu Jan 29 10:11:01 2015
From: ben.boeckel at kitware.com (Ben Boeckel)
Date: Thu, 29 Jan 2015 10:11:01 -0500
Subject: [Paraview-developers] Super build Problem
In-Reply-To: <7B37CE47-6799-4D99-8904-33DA1E8153CE@lasp.colorado.edu>
References: <7B37CE47-6799-4D99-8904-33DA1E8153CE@lasp.colorado.edu>
Message-ID: <20150129151101.GA3908@megas.kitwarein.com>

On Wed, Jan 28, 2015 at 13:01:30 -0700, Joshua Murphy wrote:
> I have posted this question once before, but everyone was probably
> busy with the 4.3.1 release? So here goes again.
> 
> I am trying to build the superbuild on the NCAR visualization cluster
> Caldera for development work.  I need to build 4.1.0, as I have not
> yet had time to update my tools to the most recent release.
> 
> When I attempt to build the superbuild, I get an error building
> Freetype (see below).
> 
> I have not been able to figure out what is causing the build error.
> 
> I am using the gnu/4.6.4 module, the cmake/3.0.2 module, and the
> gmake/4.1 module.
> 
> If anyone can help, that would be great.

What branch of the superbuild are you using? Are you using the 4.1.0 tag
in the repository?

At a guess, it looks like the targets are out-of-order since it looks
like output directories aren't being created? Is this a parallel or
serial build?

--Ben