xem / w

A micro WebGL2 framework with a ton of features

W

A micro WebGL2 framework with a ton of features

https://xem.github.io/W

license: public domain

Install via NPM with npm install https://github.com/xem/W/#semver:1.0.1

w's Issues

Add a package.json so the lib can be installed with npm

Issue

Right now you have to copy the files into your own project.

Goal

Make it easier for developers...

• to use the library without copying, using npm
• to update versions

Questions about the usage

Hello, I just found your project and it looks great! But I have a few questions:

• How to change texture (or size) individually per object? Do I really have to use W.move({n:"mario", size : ....?
• How to control size of the object? For example, in your demo - https://xem.github.io/W/demos/6.html - what if I wanted to mach cube dimensions with canvas dimensions? Or to have fixed dimensions like 100px X 100px X 100px? I see demos are using 1 and increase/decrease with small steps, but I do not understand what is 1.
• And is it possible to have a rectangles, like 200px X 100px x 20px ?
• Is it possible to have different textures per side for the objects? For example, to create a cube where one side would be bricks, but other - trees?

Thanks!

Remove unused parameters from setState

As far as I can tell, the setState function (https://github.com/xem/W/blob/gh-pages/w.js#L131) only uses the state, type, and texture parameters, and does not use i, normal = [], A, B, C, Ai, Bi, Ci, AB, BC.

@xem -- Can these be safely removed?

Create an ESM build of the library so it can be imported

Background

ESM (modules) are the future; they let developers handle dependencies without polluting the window scope.

Improvements

• Create a w.esm.js build that uses export default W

Challenges

Can this be done in a way that...

• doesn't increase the final build of a game?
• uses the same source file (so there aren't two divergent main js files)?

Putting the camera in a group works with the full source, does not with the minified one

As the title says.
When trying to put the camera in a group with the minified W code, the camera does not move anywhere.
Made a custom build from the full version, and it works, so probably some build step / option messed it up.

How to adjust camera distance?

The near and far values (the min and max values for the camera's frustrum?) are hard-coded to 1 and 1000. It would be useful to be able to adjust these. (Currently I'm working on a prototype of a solar system, and I'd like to use larger numbers for coordinates.)

I think this would involve adjusting the projection? https://github.com/xem/W/blob/gh-pages/w.js#L150 But I don't understand the math here. @xem I think this could be controlled via parameters on the camera method without adding too many bytes.

Add raycasting to add interaction through mouse or touch

I don't know how to implement a raycasting using W, there is some functionality to assist with raycasting?.
Raycasting is used for mouse picking (working out what objects in the 3d space the mouse is over) amongst other things.
If hasn't some function, could u implement it or guide on a way to add it on the W?