Skip to content
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

No Box2D To PlayRho Migration Guide #219

Open
6 tasks
louis-langholtz opened this issue Nov 25, 2017 · 2 comments
Open
6 tasks

No Box2D To PlayRho Migration Guide #219

louis-langholtz opened this issue Nov 25, 2017 · 2 comments
Labels
Docs Use when issue or pull request relates to the documentation of the project. Enhancement For suggestions or changes that enhance any part of the project and isn't a bug. Help Wanted For things that other people are encouraged to help with.
Milestone

Comments

@louis-langholtz
Copy link
Owner

louis-langholtz commented Nov 25, 2017

Expected/Desired Behavior or Experience:

There's a guide written in markdown for helping people transition from Box2D code to PlayRho. Among other things, it should mention:

  • The transition from using shape types to using the visitor design pattern for this.
  • The transition from using joint types to using the visitor design pattern for this.
  • Circle shapes have been renamed disk shapes.
  • Settings have become runtime parameters via StepConf.
  • The base float32 type has morphed into the playrho::Real type supporting any fundamental floating point type as well as user definable types that at least satisfy the LiteralType concept, have supporting common mathematical functions, and have a specialization of the std::numeric_lists template class for them.
  • Gravity, acceleration and forces all rolling into bodies' acceleration property.

Actual Behavior:

There's currently no transition guide like this.

@louis-langholtz louis-langholtz added Docs Use when issue or pull request relates to the documentation of the project. Enhancement For suggestions or changes that enhance any part of the project and isn't a bug. Help Wanted For things that other people are encouraged to help with. labels Nov 25, 2017
@louis-langholtz louis-langholtz added this to the 1.0 Release milestone Nov 25, 2017
@louis-langholtz louis-langholtz added this to To Do in Documentation work via automation Nov 25, 2017
@louis-langholtz
Copy link
Owner Author

louis-langholtz commented Dec 31, 2017

Hmm... just remembered: there's PlayRho/Changes.md that relates to this. Because there's this document already which I think just needs review and some updates, I'm re-targeting this issue to the Beta launch.

@louis-langholtz louis-langholtz modified the milestones: 1.0 Release, Beta Launch Jan 31, 2018
@louis-langholtz louis-langholtz modified the milestones: Beta Launch, 1.0 Release Oct 23, 2020
@louis-langholtz
Copy link
Owner Author

I'd love to have a document for this that was focused on explaining PlayRho in terms of Box2D but I don't want to hold up a release 1.0 for this.

@louis-langholtz louis-langholtz modified the milestones: 1.0 Release, 1.0+ Nov 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Docs Use when issue or pull request relates to the documentation of the project. Enhancement For suggestions or changes that enhance any part of the project and isn't a bug. Help Wanted For things that other people are encouraged to help with.
Projects
No open projects
Development

No branches or pull requests

1 participant