Talk:Physics File Format: Difference between revisions
Jump to navigation
Jump to search
(New page: Suggested topics for discussion: * Should the format be tied closely to Box2D's terminology, features and limitations or generalized? * Should the format be easily editable by novices (l...) |
No edit summary |
||
| Line 1: | Line 1: | ||
Suggested topics for discussion: |
Suggested topics for discussion: |
||
* What are the overall goals of the file format? |
|||
** Ability to save & load user-edited scenes. |
|||
** Ability to share scene geometry & mechanical devices between applications using the same (or similar) physics simulation engines. |
|||
** Ability to create complex scenes without programming knowledge. |
|||
** Ability to create converters to and from other 2D vector formats. |
|||
* Should the format be tied closely to Box2D's terminology, features and limitations or generalized? |
* Should the format be tied closely to Box2D's terminology, features and limitations or generalized? |
||
Latest revision as of 07:37, 11 July 2008
Suggested topics for discussion:
- What are the overall goals of the file format?
- Ability to save & load user-edited scenes.
- Ability to share scene geometry & mechanical devices between applications using the same (or similar) physics simulation engines.
- Ability to create complex scenes without programming knowledge.
- Ability to create converters to and from other 2D vector formats.
- Should the format be tied closely to Box2D's terminology, features and limitations or generalized?
- Should the format be easily editable by novices (like maybe JSON or YAML) or is XML okay?
- Should the format be derived from an existing format, like SVG, that would allow for use of existing vector editors?
- Should the format be derived from an existing 2D physics application format, like Phun or iPhysics?