Skip to content

User defined primitives #26

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

Closed
c42f opened this issue Nov 7, 2013 · 4 comments
Closed

User defined primitives #26

c42f opened this issue Nov 7, 2013 · 4 comments

Comments

@c42f
Copy link
Owner

c42f commented Nov 7, 2013

A proof of concept hack shows that user defined points of interest can be very useful. We need

  • Creation and deletion of points of interest
  • Some system to save them to a file (or possibly the log)
  • A way of loading them in again

Since these aren't exactly point clouds, we probably need a new geometry type for them; something that has flexible creation/deletion, and displays the points of interest in a visually distinctive way. Since the user is creating the points, it's probably fine to assume that there's not many of them.

Generalizing the concept, it also makes sense to support user-defined lines and planes since these can be useful for measuring things and creating models by hand for checking against automatically generated geometry. The tricky thing will be to keep this lightweight so that displaz doesn't try to grow into a full-blown 3D modeling program.

@c42f c42f added the feature label Nov 9, 2014
@c42f c42f changed the title Support for user defined points of interest User defined primitives Jun 13, 2015
@c42f c42f added the UI label Jun 13, 2015
@r-chris
Copy link

r-chris commented Jun 15, 2016

This could probably be combined with #83

@c42f
Copy link
Owner Author

c42f commented Jun 16, 2016

Hmm, I'm not sure #83 is that closely related. Can you expand on what you're imagining?

Personally I think the new scripting hooks cover this in a rather general and flexible way, so I'm almost inclined to close it now that #92 is done.

@r-chris
Copy link

r-chris commented Jun 17, 2016

I was imagining this suggestion was about defining your own POI in terms of camera placement / viewport and in turn allowing us to save / load such viewpoints for any dataset. It would allow jump between those different viewpoints and possibly have a Google Earth style camera path animation in between such viewpoints.

On second read I am not so sure any more that this is what you wanted to accomplish here.

@c42f
Copy link
Owner Author

c42f commented Jun 17, 2016

Ah yes that makes sense though it's not quite what I was originally going for here - this was meant to be about a way of recording "placemarks" or other geometry by clicking around. I think #92 does cover this nicely for now and is more flexible than anything we could do on the C++ side, so I'm going to close this.

@c42f c42f closed this as completed Jun 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants