edin-m
commented
3 years ago Initial work has been done and merged into wip/components.
Feel free to test it out and send feedback.
Future work will be done in separate PRs and merged into the WIP branch.
Future work (in sub-branches):
- [x] Make components menu not flicker when holding shift
- [x] Add "Add Component" to the Property Dock context menu
- [x] Support all objects (not just MapObject)
- [x] Add/remove components to multiple objects
- [x] Add/Remove component undo/redo: use component name
- [x] Modify components for multiple objects
- [x] Scripting/API support
- [x] Support object templates
- [ ] Add ObjectReferenceItem support
- [ ] Add a compatibility option (default=on) when saving the map
- [ ] Review & Test this & all sub-features
- [ ] Support tile objects and inheritance?
- ~When adding a component add it into an alphabetically sorted place in the property browser~
- ~A different tool button menu icon~
- ~Remember the order of components~
- ~Use the object type color as the property browser bar color (cannot be implemented)~
bjorn
As a user, I'd like to assign different sets of properties to an object.
Problem/motivation: An object having a single type is not flexible enough. One object could have sounds, physics, and AI. Another could have trigger properties only. Basically the Components from the ECS (Entity Component System) pattern.
Idea: Similar features have been proposed and discussed. e.g. https://discourse.mapeditor.org/t/custom-property-type/5000 But they have more to do with the custom property types and the possibility of supporting components through these custom types which could maybe be nested.
It would look something like this: