You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: