[Interop-dev] GSoC 2017 netjsongraph.js progress report 1

[Nemesis]

Yes it's clear enough for me.

What about canvas vs SVG?

Can you make it to complete the first goal before the first GSoC evaluation?

Federico



On 06/12/2017 03:05 PM, Xiang Gao wrote:
> I think d3 4.0 + three.js is the best choice currently.
> 
> 
> Because they are both famous and iteration rapidly.
> 
> Pixi.js is also great but it only support 2d render, so if we want to expand our visualisation to 3D in the future, we can only choose three.js. Three.js is a library which lightweight webGL packaging in order to avoid writing WebGL directly that is very hard and verbose.
> 
> The problem of importing Sigma.js plugins lead me to give up this approaches. We should make our workflow which includes development by us and installation by users be very easy, for example, if we use webpack to build our project, we can run it just one line command, and if user want to use our lib in their project, just install and import it by one line code rather than downloading it from website and use <scripts> to import.
> 
> I don’t know if I have explained it clear.
> 
> 
> Xiang
> 
>> On Jun 12, 2017, at 20:45, Nemesis <(spam-protected)> wrote:
>>
>> Ok, made it now.
>>
>> After trying these 3 different approaches, could you tell us which one
>> do you think is best and why?
>>
>> Federico
>>
>>
>> On 06/12/2017 02:37 PM, Nemesis wrote:
>>> Ok after chatting with Xiang we found out I had an old NodeJS version
>>> installed, now I have another issue: I can't load the demo built with
>>> Sigma.js.
>>>
>>> Let me know via chat when you are back.
>>>
>>> Federico
>>>
>>>
>>> On 06/12/2017 12:11 PM, Xiang Gao wrote:
>>>> Have you run npm install ? let’s chat on Gitter
>>>>
>>>>
>>>>> On Jun 12, 2017, at 17:40, Nemesis <(spam-protected)
>>>>> <mailto:(spam-protected)>> wrote:
>>>>>
>>>>> On 06/11/2017 01:48 PM, Xiang Gao wrote:
>>>>>> Hi, all
>>>>>>
>>>>>> Last week I developed 3 demos using 3 library and completed my stage
>>>>>> task in my proposal :)
>>>>>>
>>>>>> - improve webpack config for development
>>>>>> - develop 3 demos using Sigma.js, Pixi.js, Three.js respectively.
>>>>>>
>>>>>> Sigma.js code looks very concise, but importing of its plugins (such as
>>>>>> force layout plugin) in modern way is so hard, I have asked its author
>>>>>> by issues: https://github.com/jacomyal/sigma.js/issues/871. but it not
>>>>>> work for me, so I have to wait their respond.
>>>>>> Pixi.js and Three.js I used it only to render d3 force layout. And
>>>>>> three.js looks slow than Pixi.js but its slowness may caused by lines
>>>>>> render way. So I plan to use anther way to draw line between nodes to
>>>>>> improve its performance, maybe.
>>>>>>
>>>>>> I haven’t wrote section that explain how to run my demo in README,
>>>>>> because it’s only experiment.
>>>>>> So I write it here:
>>>>>>
>>>>>> /git clone dev branch/
>>>>>> /yarn install  // or npm install/
>>>>>> /npm start  // replace `entry` in webpack.config.js to check
>>>>>> different demo/
>>>>>> /
>>>>>> /
>>>>>
>>>>>
>>>>> I'm getting this error whan launching npm start:
>>>>>
>>>>> /var/www/netjsongraph.js/node_modules/eslint-loader/index.js:17
>>>>> class ESLintError extends Error {
>>>>> ^^^^^
>>>>> Hash: b3f9f9780406d097b3d8
>>>>> Version: webpack 1.15.0
>>>>>
>>>>> What am I doing wrong?
>>>>>
>>>>> Federico
>>>>
>>>
>>>
>>> _______________________________________________
>>> Interop-dev mailing list
>>> (spam-protected)
>>> https://lists.funkfeuer.at/mailman/listinfo/interop-dev
>>>
>>
>>
>> _______________________________________________
>> Interop-dev mailing list
>> (spam-protected)
>> https://lists.funkfeuer.at/mailman/listinfo/interop-dev