Skip to content

Naming #51

@soehrl

Description

@soehrl
  • Scene
    • Seems quite fitting
    • Level: misleading as, e.g., a main menu would be considered a level
  • SceneComponent
    • okay?
  • SceneObject
    • Fitting but is a little long
    • Object: too generic?
    • Entity: fitting name as it really is an entity in the sense of an entity component system, however, can a user grasp the role of an entity without any explanation?
  • SceneObjectComponent
    • Should always be the previous name + Component to describe it well. SceneObjectComponent seems to be too long
  • Transform.position
    • The use immediately understands the concept of position, however, he might think it is more absolute than it really is as its always considered relative to its parent.
    • translation: describes the concept well but maybe a little long for how often it will be used? maybe too technical?
    • offset: hmmm?
    • location: sounds even more absolute than position
    • relativePosition: too long, too weird
  • Concept: function that alters the state of the scene
    • SceneController
    • Behaviour
    • Job
    • System: ECS lingo

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions