Thanks, Mathieu, unfortunately the RenderView or the other hardcoded views
won't work for us.
As I described, I need to implement a custom view with a bunch of input
fields and buttons to represent data statistics.

The corresponding Qt views of the 4 mentioned View classes are created in
pqStandardServerManagerModelInterface::CreatePQView using hardcoded tests
such as:
 if (xmlname == pqSpreadSheetView::spreadsheetViewType())
  {
    return new pqSpreadSheetView(group, name, proxy, server, parent);
  }
Is it feasible to create another, generic vtkPVView-derived class besides
vtkPVRenderView...vtkSpreadSheetView, which will allow to define the view
elements using the plugin mechanism?

We can add menus, buttons and toolbars through plugins, why not customize a
generic view? Is there a reason that forbids such customization, or is it
just one of those topics that hasn't received sufficient interest or
funding, but could be implemented in principle?
Thanks
Kolja

On Tue, Jan 23, 2018 at 10:45 AM, Mathieu Westphal <
mathieu.westp...@kitware.com> wrote:

> Hello
>
> Here is a minimal example for creating a new type of view within a plugin.
> You actually cannot inherit directly from vtkPVView, you must inherit for
> a base view, which can be :
>  - vtkPVRenderView
>  - vtkPVContextView
>  - vtkPythonView
>  - vtkSpreadSheetView
> (https://www.paraview.org/ParaView/Doc/Nightly/www/cxx-
> doc/classvtkPVView.html)
>
> This choice is also visible in the associated xml files where you precise
> which kind of proxy you want to create.
>
> In the attached example, I demonstrated how to add a clone of the Render
> View, called Render View 2.
>
> Hope it helps,
>
> Best,
>
>
> Mathieu Westphal
>
> On Mon, Jan 22, 2018 at 7:08 PM, Kolja Petersen <petersenko...@gmail.com>
> wrote:
>
>> Thank you, Mathieu,
>> any update on this?
>> All my research seems to point to a few hardcoded views that are
>> accessible. I simply can't find a solution to implement a new view and open
>> it from a plugin.
>> Thanks
>> Kolja
>>
>>
>> On Wed, Jan 17, 2018 at 9:55 AM, Mathieu Westphal <
>> mathieu.westp...@kitware.com> wrote:
>>
>>> Hi Kolja
>>>
>>> I have a simple view plugin project ongoing that I should be able to
>>> scale down for your needs.
>>> I will try to find the time to do it before the end fo the week.
>>>
>>> Best,
>>>
>>> Mathieu Westphal
>>>
>>> On Tue, Jan 16, 2018 at 8:38 PM, Kolja Petersen <petersenko...@gmail.com
>>> > wrote:
>>>
>>>> Is it possible to write a plugin that derives from vtkPVView instead of
>>>> vtkPVRenderView?
>>>>
>>>> I don't know how I can further shorten my question. The answer is quite
>>>> important to decide whether we can continue our ParaView developments.
>>>> Thank you
>>>> Kolja
>>>>
>>>>
>>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>>>>  Virenfrei.
>>>> www.avast.com
>>>> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>>>> <#m_1712022189565304643_m_-7533380727799637296_m_63782262572172547_m_2726909845290941008_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>>
>>>> On Mon, Jan 15, 2018 at 7:32 PM, Kolja Petersen <
>>>> petersenko...@gmail.com> wrote:
>>>>
>>>>> I have stripped down Plugin/MantaView until all compilation problems
>>>>> disappear. What is left, is basically a plugin for a vtkOpenGLRenderer.
>>>>> The code, consisting of only two minimal classes, is attached and can
>>>>> be built using:
>>>>> unzip snippet-viewplugin.zip && mkdir build && cd build && cmake &&
>>>>> make
>>>>> (tested with ParaView 5.4.1)
>>>>>
>>>>> This brings me back to my initial question. I'd like to show a custom
>>>>> view, made of a number of Qt widgets (buttons and text) to show important
>>>>> statistics.
>>>>> In SnippetView.xml, the view is declared as:
>>>>> <SnippetViewProxy class="vtkPVSnippetView" ... base_proxygroup="views"
>>>>> base_proxyname="RenderView" ...
>>>>>
>>>>> How can I replace 'base_proxyname="RenderView"' by some generic view,
>>>>> to be filled with widgets? "View" or "ViewBase" are not recognized as base
>>>>> proxies.
>>>>> Thank you
>>>>> Kolja
>>>>>
>>>>>
>>>>> On Sun, Jan 14, 2018 at 5:05 PM, Kolja Petersen <
>>>>> petersenko...@gmail.com> wrote:
>>>>>
>>>>>> Dear plugin developers,
>>>>>> I need to implement a custom view to present datasets in a detailed
>>>>>> editable format.
>>>>>>
>>>>>> This link says that the plugin tutorial is obsolete for the view part:
>>>>>> https://www.paraview.org/Wiki/ParaView/Plugin_HowTo#Adding_a
>>>>>> _custom_view_.2A_obsolete_.2A
>>>>>>
>>>>>> The Examples/Plugins/GUIView suggested in the link doesn't exist. The
>>>>>> Plugins/MantaView is rather complex and doesn't compile due to other bugs
>>>>>> as reported elsewhere, so that I can't get a clue how the MantaView 
>>>>>> plugin
>>>>>> is supposed to work.
>>>>>>
>>>>>> Could some kind developer upload a minimal working view plugin
>>>>>> example, which needs to display only a simple QButton or any other 
>>>>>> widget?
>>>>>> This will help to allow users build their custom views for ParaView 
>>>>>> 5.x.y.
>>>>>> Thank you
>>>>>> Kolja
>>>>>>
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> 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:
>>>> https://paraview.org/mailman/listinfo/paraview
>>>>
>>>>
>>>
>>
>
_______________________________________________
Powered by www.kitware.com

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

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

Search the list archives at: http://markmail.org/search/?q=ParaView

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

Reply via email to