Re: [Paraview] Running a simple example using ParaviewWeb

2017-08-22 Thread Léo Pessanha
Thank you, Sebastien! It worked! The correct path should also have a '/' at the end so: dataModel = new QueryDataModel(jsonData, '/data/'), > instead of dataModel = new QueryDataModel(jsonData, '/data'), > Thanks again! Leonardo Pessanha Laboratory of Computational Methods in Engineering

Re: [Paraview] Running a simple example using ParaviewWeb

2017-08-22 Thread Sebastien Jourdain
Almost, the missing part is for "dataModel = new QueryDataModel(jsonData, 'path/to/dist/data')" 'path/to/dist/data' should be '/data' since your web server is serving path/to/dist as / On Tue, Aug 22, 2017 at 12:23 PM, Léo Pessanha wrote: > So, just to be clear

Re: [Paraview] Running a simple example using ParaviewWeb

2017-08-22 Thread Léo Pessanha
So, just to be clear in order for me to understand I should copy the content of 'node_modules/tonic-arctic-sample-data/data/probe/' to 'dist/data' and use dataModel = new QueryDataModel(jsonData, 'path/to/dist/data'), > in the src/index.js ? Thanks in advance! Leonardo Pessanha Laboratory of

Re: [Paraview] Running a simple example using ParaviewWeb

2017-08-22 Thread Sebastien Jourdain
__BASE_PATH__ is meant to dynamically define the http endpoint. This should not be a file path... You can remove it from your code and provide a proper endpoint. For us it is used on to allow local and github.io deployment. In your case, you need to copy that data by yourself to the dist/data

Re: [Paraview] Running a simple example using ParaviewWeb

2017-08-22 Thread Léo Pessanha
Thank you, Sebastien. I am able to build the example but the data don't show up yelding in the browser debugger ReferenceError: __BASE_PATH__ is not defined[Learn More] > In the following line of MyWebApp.js dataModel = new _QueryDataModel2.default(_index2.default, __BASE_PATH__ + >

Re: [Paraview] Running a simple example using ParaviewWeb

2017-08-14 Thread Sebastien Jourdain
I think your import is correct. Regarding the sample data, this is the way you can download it via npm (when doing "npm install") => https://github.com/Kitware/paraviewweb/blob/master/package.json#L48 On Mon, Aug 14, 2017 at 3:12 PM, Léo Pessanha wrote: > Hi!

Re: [Paraview] Running a simple example using ParaviewWeb

2017-08-14 Thread Léo Pessanha
Hi! Thank you for the help! Because of it I was able to build and start the example correctly. Now I am trying different examples such as MultiLayoutViewer https://kitware.github.io/paraviewweb/examples/MultiLayoutViewer.html . I am still a little doubtful about my imports but I believe import

Re: [Paraview] Running a simple example using ParaviewWeb

2017-08-10 Thread Sebastien Jourdain
With ParaViewWeb, we force the user to pick the version of the dependencies they wants to install instead of forcing them. Regarding your import path they are still wrong. from paraviewweb/src/Component/Native/Composite/example/index.js when you import '..' that resolve to

Re: [Paraview] Running a simple example using ParaviewWeb

2017-08-09 Thread Léo Pessanha
So, I was able to build using 'paraviewweb/src/' and installing forcibly mout, axios and hammerjs packages. Now there's other js errors that I am going after like /plotly.js\ and global reference ones ! It's definitely not a simple task to build an example of paraviewweb as a standalone app.

Re: [Paraview] Running a simple example using ParaviewWeb

2017-08-09 Thread Léo Pessanha
So I am not sure of the first path yet. Is it 'paraviewweb/src/' or 'paraviewweb/src/Component'? I have the exactly same result using full path or starting with 'paraviewweb' Using: import CompositeComponent from 'paraviewweb/src/'; > import BGColorComponent from >

Re: [Paraview] Running a simple example using ParaviewWeb

2017-08-09 Thread Sebastien Jourdain
The import should start with 'paraviewweb' then you provide the full path from there like: import BGColorComponent from 'paraviewweb/src/Component/Native/ BackgroundColor'; On Wed, Aug 9, 2017 at 6:24 PM, Léo Pessanha wrote: > Hi! I did the changes. The only

Re: [Paraview] Running a simple example using ParaviewWeb

2017-08-09 Thread Léo Pessanha
Hi! I did the changes. The only thing I am not sure it's the right paths in the imports of ${ROOT}/src/index.js import CompositeComponent from '..'; > import BGColorComponent from '../../BackgroundColor'; > > Should I change this paths? I did try import CompositeComponent from

Re: [Paraview] Running a simple example using ParaviewWeb

2017-08-03 Thread Sebastien Jourdain
If I get to it, I'll do what I've done with vtk.js to support both. See: https://github.com/Kitware/vtk-js/blob/master/Utilities/config/dependency.js On Thu, Aug 3, 2017 at 1:49 PM, Léo Pessanha wrote: > Thank you, Sebastien. I will give a try! > > Do you believe

Re: [Paraview] Running a simple example using ParaviewWeb

2017-08-03 Thread Léo Pessanha
Thank you, Sebastien. I will give a try! Do you believe it's best to rollback webpack to 1.x or to change the webpack.config.js in order to fit webpack 2.x API? Leonardo Pessanha Laboratory of Computational Methods in Engineering Federal University of Rio de Janeiro - COPPE Rio de Janeiro, RJ,

Re: [Paraview] Running a simple example using ParaviewWeb

2017-07-24 Thread Sebastien Jourdain
Based on the path given in the setup guide, you should copy the example you want to reproduce inside ${ROOT}/src/* where the main example file should be named index.js. Then you should be able to build your example using the npm command: "npm run build". Maybe the vtk.js explanation might be

[Paraview] Running a simple example using ParaviewWeb

2017-07-24 Thread Léo Pessanha
Hi! I would like to know the steps in order to run simple example like the following one: https://kitware.github.io/paraviewweb/examples/Composite/index.html It doesn't need to be a really elaborated tutorial, but a simple one with the main things. I have little to no background in web