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
Stop using terms like width and height #11
Comments
This also includes terms like "horizontally" and "vertically". |
io7m
added a commit
that referenced
this issue
May 7, 2017
Stop using terms such as "horizontally", "vertically", "width", "height", etc. Deprecate methods and add replacements. Affects #11
io7m
added a commit
that referenced
this issue
May 7, 2017
io7m
added a commit
that referenced
this issue
May 8, 2017
This removes the final uses of "width" and "height" from the code and introduces binary-compatible deprecated methods to be removed in a future release. Affects #11
Done. |
io7m
added a commit
that referenced
this issue
May 9, 2017
Release: com.io7m.jregions 1.1.0 Code new: Add splitAlongXY method for dividing areas into quadrants. Code new: Stop using terms such as "horizontally", "vertically", "width", "height", etc. Deprecate methods and add replacements. (tickets: #11) Code new: Add volume types. (tickets: #9) Code fix: Fix overlaps() for areas and volumes. (tickets: #12, #14) Code fix: Fix contains() for areas and volumes. (tickets: #13)
io7m
added a commit
that referenced
this issue
May 9, 2017
Release: com.io7m.jregions 1.1.0 Code new: Add splitAlongXY method for dividing areas into quadrants. Code new: Stop using terms such as "horizontally", "vertically", "width", "height", etc. Deprecate methods and add replacements. (tickets: #11) Code new: Add volume types. (tickets: #9) Code fix: Fix overlaps() for areas and volumes. (tickets: #12, #14) Code fix: Fix contains() for areas and volumes. (tickets: #13)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This ascribes meaning to axes that programmers using
jregions
may not be using.Removes any possibility of ambiguity.
The text was updated successfully, but these errors were encountered: