Support subdirs for namespace hierarchy

[alex0]

@Prote

but I truly don’t see how having a Folder-like management in addition (this is the key concept I’m trying to convey) to the current “just write somewhere, add metadata, and then use Query” approach could damage the user.

As I said I’m not against it and I don’t think it’s set on stone for Logseq devs neither. I think it just happened that Logseq focuses on the Efficiency mindset and the UI for a more RDB experience is just lacking at the moment. If one contributes to Logseq in that direction with a good implementation I don’t think the devs will refuse it. Indeed properties are a step in that direction.

---

@Prote

A corny example: you can probably do the same operations on a smartphone and a tablet, but nonetheless one could certainly be willing to spend for both of them and choose which one to use based on the moment their needs occur.

I mean one should use the best approach according to the problem, not the situation. For example if I want to track books and their authors the RDB model is better for me.

@Prote

The analogy with OOP and FP is great, although it may put it a certain way that could make you think “it’s either this or that”

Again it depends on the problem: sometimes OOP is very naturally the best paradigm and sometimes it makes sense to use FP instead. It’s not like a developer will always use one or the other, of course.

@Prote

At least, that’s my opinion, based on the thinking that a software provides a set of features, and the users decides how and which one to use to better suit their needs.

In my opinion, compared to other applications, Logseq gives very abstract, general and powerful tools and the user is free to build a custom workflow . Indeed my “indexes” are a workaround that is possible thanks to the generic Logseq tools.

---

I don’t remember if I already mentioned it, but for example here there is my proposal to make it easier to add properties while keeping the efficiency approach:

Syntax for inline properties::

From the discussion here I think we have a cool proposal. We want this syntax: - [[title::The Picture of Dorian Gray]] is a [[type::book]] written by [[author::Oscar Wilde]]. as a more compact way to write this block: - type:: book title:: The Picture of Dorian Gray author:: Oscar Wilde [[The Picture of Dorian Gray]] is a [[book]] written by [[Oscar Wilde]]. Rendered, with links, as: The Picture of Dorian Gray is a book written by Oscar Wilde. So it’s rendered just like: - [[Th…