1. 06 1月, 2018 1 次提交
  2. 04 1月, 2018 2 次提交
  3. 03 1月, 2018 2 次提交
  4. 31 12月, 2017 3 次提交
  5. 29 12月, 2017 1 次提交
  6. 28 12月, 2017 2 次提交
  7. 26 12月, 2017 1 次提交
  8. 25 12月, 2017 1 次提交
    • M
      Fixed spelling colour => color · 7677646e
      Magnuz Binder 提交于
      Not a real error, but many frowns at mixing British and US English, so I thought it's better to keep it consistent US English, especially since color is also a common keyword.
      7677646e
  9. 24 12月, 2017 1 次提交
  10. 14 12月, 2017 3 次提交
  11. 13 12月, 2017 1 次提交
  12. 10 12月, 2017 2 次提交
  13. 09 12月, 2017 9 次提交
    • M
      Fix inconsistent menu order. · a063cf57
      Magnuz Binder 提交于
      a063cf57
    • M
      Fix broken link. · 3ccef258
      Magnuz Binder 提交于
      3ccef258
    • M
      Fix broken link. · 1b11cef4
      Magnuz Binder 提交于
      1b11cef4
    • M
      Change parameter name to be consistent with code. · 1c826c07
      Magnuz Binder 提交于
      GitHub got the hickups, so it's possible this is a duplicate commit.
      
      Both radiusSegment and radialSegments are misleading. I would prefer to call it archSegments, both in code and documentation. For consistency and easier understanding, I think the prefix theta should also be replaced by arch here and in some other places, e.g. Ring(Buffer)Geometry. For easier understanding, I also think phiSegments should be replaced with radialSegments there, where it would be correct. But since these are a bit major changes, at least if implemented in the code, I would like the views of those with a better overview and understanding.
      1c826c07
    • M
      Change parameter name to be consistent with code. · 0741ec25
      Magnuz Binder 提交于
      Both radiusSegment and radialSegments are misleading. I would prefer to call it archSegments, both in code and documentation. For consistency and easier understanding, I think the prefix theta should also be replaced by arch here and in some other places, e.g. Ring(Buffer)Geometry. For easier understanding, I also think phiSegments should be replaced with radialSegments there, where it would be correct. But since these are a bit major changes, at least if implemented in the code, I would like the views of those with a better overview and understanding.
      0741ec25
    • M
      Change parameter name to be consistent with code. · 6bdec963
      Magnuz Binder 提交于
      Both radiusSegment and radialSegments are misleading. I would prefer to call it archSegments, both in code and documentation. For consistency and easier understanding, I think the prefix theta should also be replaced by arch here and in some other places, e.g. Ring(Buffer)Geometry. For easier understanding, I also think phiSegments should be replaced with radialSegments there, where it would be correct. But since these are a bit major changes, at least if implemented in the code, I would like the views of those with a better overview and understanding.
      6bdec963
    • M
      Change parameter name to be consistent with code. · ac259428
      Magnuz Binder 提交于
      Both radiusSegment and radialSegments are misleading. I would prefer to call it archSegments, both in code and documentation. For consistency and easier understanding, I think the prefix theta should also be replaced by arch here and in some other places, e.g. Ring(Buffer)Geometry. For easier understanding, I also think phiSegments should be replaced with radialSegments there, where it would be correct. But since these are a bit major changes, at least if implemented in the code, I would like the views of those with a better overview and understanding.
      ac259428
    • M
      Correct example to use 2D vectors. · 935650a4
      Magnuz Binder 提交于
      935650a4
    • M
      InterleavedBuffer: Improve stride definition one more time · a48b71ca
      Mugen87 提交于
      a48b71ca
  14. 08 12月, 2017 1 次提交
  15. 06 12月, 2017 7 次提交
  16. 05 12月, 2017 3 次提交