[Paraview] Using ParaviewWeb examples

[Sgouros, Thomas]

I tried that page twice and get errors about missing fix-autobahn, and when
I removed that from the package.json, webpack complained about missing
eslint (I installed eslint, but it doesn't change), and then errors saying
"Webpack has been initialised using a configuration object that does not
match the API schema" and errors about the output directory needing to be
an "**absolute path** (required)". I'm sure there's something simple I'm
missing, but not sure what.

Thank you,

 -Tom

On Mon, Feb 19, 2018 at 4:08 PM, Aron Helser <aron.helser at kitware.com>
wrote:

> I think you're looking for the setup doc: https://kitware.github.
> io/paraviewweb/docs/setup.html
> It gives you a sample webpack config. Nearly all the paraviewweb
> dependencies are contained in kw-websuite, as documented on that page.
>
> The examples as they stand use a bit of magic, you are right, so they can
> be embedded in the documentation pages. AFAIK, we don't have an install
> option to make a stand-alone example.
> Regards,
> Aron
>
> On Mon, Feb 19, 2018 at 3:59 PM, Sgouros, Thomas <thomas_sgouros at brown.edu
> > wrote:
>
>> Thank you. it would be great also to have pointers to normalize.css, and
>> the webpack and package configs for these examples. They are more like
>> puzzles than examples in their current state, with the challenge to find
>> all the missing pieces and guess how to put them together. Am I missing
>> some intro that steps me through those parts? Or is there a way to see the
>> whole example laid out with those other pieces? Maybe an npm install option
>> that will give me these examples on my disk?
>>
>> I see fragments of examples on this page: https://kitware.github.i
>> o/paraviewweb/docs/import.html , but apparently it is not enough for me.
>>
>> Thank you,
>>
>>  -Tom
>>
>> On Mon, Feb 19, 2018 at 2:48 PM, Aron Helser <aron.helser at kitware.com>
>> wrote:
>>
>>> Hi Tom,
>>> The ParaviewWeb examples always live in a sub-directory of the component
>>> they illustrate - so here, this is the Composite example, so '..' just
>>> refers to 'Composite'.
>>> If you look in the left menu, you can see that 'Composite' is grouped
>>> into ' Component/Native'. That's the directory it's in.  '../../BackgroundColor'
>>> is a sibling directory to 'Composite', so it will also be in '
>>> Component/Native'
>>>
>>> Generally you can follow the '..' out from the example sub-directory and
>>> figure out where you are.
>>>
>>> Hope that helps,
>>> Aron
>>>
>>> On Mon, Feb 19, 2018 at 2:38 PM, Sgouros, Thomas <
>>> thomas_sgouros at brown.edu> wrote:
>>>
>>>> Hello all:
>>>>
>>>> When I see a Paraviewweb example like this (from Composite.html):
>>>>
>>>> import CompositeComponent from '..';
>>>> import BGColorComponent from '../../BackgroundColor';
>>>>
>>>> Where should I look for BackgroundColor and CompositeComponent? I feel
>>>> sure I could find them eventually, but is there another search algorithm
>>>> besides brute force?
>>>>
>>>> Thank you,
>>>>
>>>>  -Tom
>>>>
>>>> _______________________________________________
>>>> 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://public.kitware.com/mailman/listinfo/paraview
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://public.kitware.com/pipermail/paraview/attachments/20180219/fb195376/attachment.html>