https://linen.dev logo
Join Discord
Powered by
# ceramic
  • Yet i have NO UNDERSTANDING on how is used eh
    m
    Yet i have NO UNDERSTANDING on how is used eh
  • Some types can be used as component but also as standalone
    b
    Some types can be used as component but also as standalone
  • Just saying this from firs glimpse in source
    m
    Just saying this from firs glimpse in source
  • (like `StateMachine`)
    b
    (like 
    StateMachine
    )
  • Yeah i saw that, no idea why it was like that
    m
    Yeah i saw that, no idea why it was like that
  • So component is for the sake of the runtime Type plus the macros?
    m
    So component is for the sake of the runtime Type plus the macros?
  • (yeah, guide page about state machines not written yet heh :D)
    b
    (yeah, guide page about state machines not written yet heh :D)
  • i know 🙂
    m
    i know 🙂
  • The other reason you would instanciate a component independently is because you might only decide at runtime to what entity you will attach it
    b
    The other reason you would instanciate a component independently is because you might only decide at runtime to what entity you will attach it
  • How do you think the API should look like otherwise?
    b
    How do you think the API should look like otherwise?
  • Uff no idea mate
    m
    Uff no idea mate
  • Imagine im checking ceramic for the sake of mimicking the api haha
    m
    Imagine im checking ceramic for the sake of mimicking the api haha
  • And the implementation because of the lang syntax differences is becoming hard
    m
    And the implementation because of the lang syntax differences is becoming hard
  • I though component was a class on its own that expanded behaviour over the entity
    m
    I though component was a class on its own that expanded behaviour over the entity
  • Im not fluent at all at haxe, yet, somehow i would use type inference?
    m
    Im not fluent at all at haxe, yet, somehow i would use type inference?
  • Like how many clicks components do u need on a visual entity?
    m
    Like how many clicks components do u need on a visual entity?
  • Usually is 1 instance of a type to add behaviour no?
    m
    Usually is 1 instance of a type to add behaviour no?
  • so myEntity.addComponent<Click>()
    m
    so myEntity.addComponent()
  • And only consume components though their entities
    m
    And only consume components though their entities
  • As the entities are responsable anyway to dispose them
    m
    As the entities are responsable anyway to dispose them
  • Entity.createWith<Click>() 🤷‍♂️
    m
    Entity.createWith() 🤷‍♂️
  • Thats what i meant with factories
    m
    Thats what i meant with factories
  • Different approach i guess. Yet the disposal of components is what bothers me when im instantiate them on my own
    m
    Different approach i guess. Yet the disposal of components is what bothers me when im instantiate them on my own
  • True
    m
    True
  • Whats an example of multiple components of the same type on an entity?
    m
    Whats an example of multiple components of the same type on an entity?
  • I don't have any example in mind, but I didn't want to restrict the ability to bind a component by type in ceramic
    b
    I don't have any example in mind, but I didn't want to restrict the ability to bind a component by type in ceramic
  • It’s fine, just wondering cause im not used to ECS and derivates
    m
    It’s fine, just wondering cause im not used to ECS and derivates
  • Ceramic is not really ECS for sure
    b
    Ceramic is not really ECS for sure
  • closer to Unity-style of binding components
    b
    closer to Unity-style of binding components
  • So says the guide 😂
    m
    So says the guide 😂
1...102103104...124Latest