Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify what goes in `vg` vs `polliwog` #95

Open
paulmelnikow opened this issue Nov 19, 2019 · 0 comments
Open

Clarify what goes in `vg` vs `polliwog` #95

paulmelnikow opened this issue Nov 19, 2019 · 0 comments

Comments

@paulmelnikow
Copy link
Contributor

@paulmelnikow paulmelnikow commented Nov 19, 2019

Since there is a closely related library, polliwog which does a lot of computational geometry, it's useful to clarify what belongs here vs. there.

Accordingly, the idea is to clarify this library's purpose:

A vector-geometry toolbelt for dealing with 3D points and vectors

and say that anything more complicated is general computational geometry, and goes in polliwog.

In particular, transformation matrices will be scoped to polliwog.

Accordingly, the matrix functions will be removed in the next major release.

Refs:

@paulmelnikow paulmelnikow changed the title Clarify what goes in vg vs polliwg Clarify what goes in vg vs polliwog Nov 19, 2019
@paulmelnikow paulmelnikow changed the title Clarify what goes in vg vs polliwog Clarify what goes in `vg` vs `polliwog` Nov 19, 2019
@paulmelnikow paulmelnikow mentioned this issue Nov 19, 2019
2 of 3 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.