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

Conversion, filtering, etc #5

Closed
io7m opened this Issue Nov 22, 2016 · 3 comments

Comments

Projects
None yet
1 participant
@io7m
Owner

io7m commented Nov 22, 2016

The command line tool already does transcoding, but it should also do:

  • Filtering: Removing and renaming attributes
  • Component type conversion: Convert an attribute to a different component type (with the same number of components)
  • Triangle index type conversion: Upcasting to larger index sizes, or downcasting to the smallest size that can fit all the indices
  • Validation: Do all triangle indices point to vertices that actually exist?

@io7m io7m added the enhancement label Nov 22, 2016

@io7m io7m self-assigned this Nov 22, 2016

@io7m

This comment has been minimized.

Show comment
Hide comment
@io7m

io7m Nov 22, 2016

Owner

Validation: Do all attribute elements exist?

Owner

io7m commented Nov 22, 2016

Validation: Do all attribute elements exist?

@io7m

This comment has been minimized.

Show comment
Hide comment
@io7m

io7m Nov 22, 2016

Owner

I feel like the right way to do this would be to have the user specify what type they expect for the output, and then specify a series of commands that state how to make the input match the expected output. For example "rename attribute x to y", "convert the components of x to y", "remove attribute z", "optimize triangles", etc.

Owner

io7m commented Nov 22, 2016

I feel like the right way to do this would be to have the user specify what type they expect for the output, and then specify a series of commands that state how to make the input match the expected output. For example "rename attribute x to y", "convert the components of x to y", "remove attribute z", "optimize triangles", etc.

@io7m

This comment has been minimized.

Show comment
Hide comment
@io7m

io7m Dec 27, 2016

Owner
Owner

io7m commented Dec 27, 2016

io7m added a commit that referenced this issue Dec 27, 2016

Initial in-memory implementation for processing
Implement an in-memory mesh for processing. Add the initial
specification types for controlling which processing should
occur.

Affects #5

io7m added a commit that referenced this issue Dec 27, 2016

io7m added a commit that referenced this issue Dec 28, 2016

io7m added a commit that referenced this issue Dec 28, 2016

io7m added a commit that referenced this issue Dec 28, 2016

Update serialization API for correctness
This simplies the implementation of serializers. All command-line
commands have been replaced with a single general filter command.

Affects #5

@io7m io7m closed this in 5880484 Dec 28, 2016

io7m added a commit that referenced this issue Dec 28, 2016

Merge branch 'release/0.3.0'
Release: io7m-smfj 0.3.0
Code change: Change serialization API to make implementations easier to write.
Code new: Add API and tools to process meshes. (tickets: #5)
Code new: Export SMFImmutableStyleType.

io7m added a commit that referenced this issue Dec 28, 2016

Merge tag 'io7m-smf-0.3.0' into develop
Release: io7m-smfj 0.3.0

Code change: Change serialization API to make implementations easier to write.
Code new: Add API and tools to process meshes. (tickets: #5)
Code new: Export SMFImmutableStyleType.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment