Logseq - object oriented?

Questions & Help
1

A point of view question… in light of the Capacities offering.

In what ways does Logseq use or show ‘object-oriented’ tendencies?
I hope those who appreciate the differences would share their analysys.

Sincerely,
Tom

2

Welcome. I’ve never used Capacities myself, but I could gather the following (this is not AI-generated):

  • On the overall approach:
    • Capacities is object-oriented by design. It is built around objects, has a strong opinion on what an object is, and offers a collection of object types.
    • Logseq is built around blocks, and lets the user decide for each block if it represents an object and how. It is possible to build an object-oriented system within Logseq.
  • On object structure:
    • Capacities uses proper object types.
    • Logseq supports custom properties for fields and templates for quick input, but it doesn’t sync the properties of similar objects.
      • In the coming database version, tags can be configured to act as partial types and force the relevant properties.
  • On object behavior:
    • Capacities offers some predefined behaviors for its basic object types.
      • Not much beyond that.
    • Logseq supports macros and custom code.
      • This allows the development of custom behaviors, though coding is required.
3 Likes
3

I’m interested in using an object model for organizing my Logseq data. I asked Grok to help me build templates in Logseq that would mimic Capacities objects. It gave me a first round set of templates that I have not yet worked with. It does seem like the best way for me to figure how to create equivalent functionality. I know it won’t be exact.