Joe Pea
Joe Pea
Those have unused Travis configs currently
LUME aims to bring the web forward, adding new features while aligning with existing patterns. We can override `getBoundingClientRect` (or make a new `getBoundingClientRectGL` method) in order for that to...
Don't you just love when this happens. https://github.com/lume/lume/actions/runs/1835819962
Let's make boilerplates (perhaps using Yeoman generator) for application starting points; one based on Webpack, another on Browserify, one on Parcel, one on Meteor, and perhaps others. Let's pick like...
Maybe classes generated from the WebComponent mixin can be cleared after some time. Usually classes will be defined at module eval time. Those classes would all be cleared after some...
Remove ElementOperations in favor of putting that code in our classes. The old idea of separating DOM logic from our Node logic doesn't apply anymore.
Currently, updating a Node outside of Motor's render loop (by not using [`Motor.addRenderTask`](https://github.com/trusktr/infamous/blob/83bea332263279cf411820d4cacbdd841256f161/src/motor/Motor.js#L94)) causes a no-op render task to be automatically added to update the modified Node in the upcoming...
On each update of an element, its position/rotation/etc are always mapped to the Three.js matrix, which isn't always necessary. For example, when updating matrices of a loaded GLTF model in...
It may be nice for render tasks to be promises that resolve whenever they are removed. This would make it easier to string tasks together. For example, here's what it...
We're using mixin classes. For example the [`WithChildren`](https://github.com/lume/lume/blob/develop/src/core/WithChildren.ts#L6-L7) class is used [like this](https://github.com/lume/lume/blob/develop/src/core/DeclarativeBase.ts#L20). We used to have this feature, but we removed it to simplify the types. Maybe we can...