anuraghazra / verly.js Goto Github PK

Hello

I was using this library to make a cord that hangs from the top of the page you can pull on and it works great but the one issue i have is that the point that is fixed can still be moved by the mouse, is there a way to prevent that

edit: setting the radius to 0.001 seems to work to hide the first point but if someone has a better suggestion let me know

Hello,

First congrats because this is a very nice library and really easy to use.

I was wondering if it would be interesting to workout a fork to be used with p5js : https://p5js.org/
(I coul help to do this by the way).

The main thing that I see would be to rewrite the render functions with p5 primitives, or maybe to enable people to get a list of points per objects to let them redraw.

This second option might help us to keep everything in this repo, and just write of few examples for p5js on how to get an customize the drawing.

What do you think ?

hi! I would like to know please if there is some example or tutorial to simulate rain and wind using Verly.js?

thanks!

• Setup proper release pipeline with changesets
• Use a better bundler eg vite or rollup so we can target dual cjs/esm bundles
• Publish to NPM
• Keep CDN packaged publishing too

Right now we have render() functions inside entity/point & stick, ideally we can keep the physics simulation renderer agnostic and have a separate Renderer class which can be swapped for any other renderer eg #9 webgl.

Hi, I love this physics engine, is really easy to use...
but can't the renderer support WebGL? or should I use a WebGL renderer, like Pixi.js?

also, can this be used in a Web Worker object?

I'm half newbie to js, I need performance for having thousands of particles, that's why I'm asking...

Right now Verly.js physics isn't independent of framerate, means if you have a faster or slower PC the physics will behave differently based on framerate.

Ideally we should take this into account when updating the physics of points/sticks

https://gafferongames.com/post/fix_your_timestep/

I don't know if you'd be up for any of these, so I'll just throw the ideas here. If you're game for any of them, happy to PR:

• standardize on the vec2 module from gl-matrix - this would mean vectors would be [ x, y ] rather than { x, y }.
  it's nice in that it re-uses a popular vector module. I'm always a little saddened looking at various game/sim repos in javascript, and every one invents it's own vector/matrix libraries. :(
• switch from Object-oriented to data-oriented design - rather than using classes to bundle code, the different primitives (sticks, dots etc.) essentially become structs, and the data structure gets passed in to all of the related functions

Will add more ideas as they come up., just wanted to throw these in as a starting point.