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

I am creating a package which is also called SignedDistanceFields #19

Open
freemin7 opened this issue Jul 28, 2019 · 0 comments
Open

I am creating a package which is also called SignedDistanceFields #19

freemin7 opened this issue Jul 28, 2019 · 0 comments

Comments

@freemin7
Copy link

Hello,

i released my fist Julia code yesterday and due to popular demand i turned it into a package. I doubt anybody will use it but i went with it. I called the package SignedDistanceFields but today i noticed there is already a package like that in the registry.
My package aims to provide a toolbox to turn scenes made out of set primitives and primitive shapes in signed distance functions which evaluate (Currently in 3d) fastly. It grew out of a raymarching engine used to render 2d images of simple 3d scenes i wrote for fun.
Do you have proposals how to resolve this naming conflict?

Would you be open to change your API allowing our packages to merge in the long run (i will have to change mine too)?
I see that the approach to discretize and existing field over a small range as a feature which can be implemented easily and the reverse operation of interpolating such arrays into a continuous solution as something which would add more variety to the shapes possible in my system.

How do the signed distance fields created here get rendered currently?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant