Joe Pea
Joe Pea
Fixes #2 The commits have all the details. TLDR: simple ESM output compatible with most tools of today, type definitions just work. Breaking change: ``` import {w} from 'wazum' //...
I know how to make this work well, I've too much experience with Node ESM. These are the issues I can help work through: Do you have any downstream projects...
Some output generators do things like this: ```js output.append('(func $', func.name) // the function is not complete yet // ... for (const param of func.parameters) output.append(' (param $', param.name, '...
I felt like the formatting of the grammar was a little difficult to read, namely the function/method calls, so I formatted them and took out the arguments lists into a...
To fix https://github.com/lume/three-meshline/issues/5, we need to take advantage of WebGL 2 geometry shading (generate the vertices in the shader) or [WebGPU compute shading](https://github.com/gpuweb/gpuweb/issues/1239#issuecomment-730514707) (similar, but different), so that the only...
closes #3
For example, here is a portion of the SVG demo with a line thickness greater than 1 and sizeAttenuation enabled, with the camera line of site perpendicular to direction of...
`line.setPoints` re-creates a bunch of stuff each time, lots of garbage collection. GPU upload during `renderer.render` is also slow.
When `sizeAttenuation` is `false` and `lineWidth` is `1`, we should essentially just render the same as `THREE.Line`, with the added bonus of features like `.advance()`.
See these lines: https://github.com/lume/three-meshline/blob/eba9c4a700c2d92fc933fbf3f00611e9f3e9caf1/demo/birds.html#L76-L87 The loop with the `Float32Array` leads to the lines initially glitched, but the loop with the normal `Array` works fine.