Move tags to the sidebar

[martinstoeckli]

A user requested to move the selection of a tag (filter) from the dropdown in the toolbar into the sidebar. This would allow to keep the list of available tag open when working on a wide desktop screen, but wouldn't require space on a narrow mobile desktop.

[martinstoeckli]

I'm currently making a proof of concept with Blazor/WASM and the implementation there was easy and it looks nice and practical. Should it be possible to switch, then it will contain a sidebar with the tags.

[smitt111]

I definitely would like to see this as an option. Having the tag list stay open in a sidebar will give the interface a folder-like look -- something a lot of old-school Windows types are accustomed to in our workflows.

[martinstoeckli]

Could implement it with a sidebar and I like it. If the transition to Blazor works out, it will probably look like this:

[smitt111]

That would most DEFINITELY would work.

…

--Steve

On 06/04/23 06:20, Martin Stoeckli wrote: Could implement it with a sidebar and I like it. If the transition to Blazor works out, it will probably look like this: grafik <https://user-images.githubusercontent.com/7747113/243180313-c10133d0-e9c1-4f63-be78-e877c30b5bed.png> — Reply to this email directly, view it on GitHub <#221 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5VAZC62TO77CIPLTTSV7E3XJSDRJANCNFSM6AAAAAAYSAX5DU>. You are receiving this because you commented.Message ID: ***@***.***>

[asasn]

Could implement it with a sidebar and I like it. If the transition to Blazor works out, it will probably look like this:

Hi, martinstoeckli.
Previously, I had an idea to use a method similar to bidirectional links to organize and connect nodes in a crisscross manner.
Your original silent notes were created by treating each note as a level presence.
The tree structure TreeView that I once suggested actually increases the mental burden of recording and grouping, making people have to think about which directory group to place it under when recording.
Now, I propose a new approach, which is that there is no overall "tree" that connects all nodes, but rather one "branch" after another.

I am a writer, and my understanding is to use it as a source of inspiration and ideas.
For example, I associate a protagonist with the weapon they possess, and then from this weapon, I associate its materials, its creators, and the protagonist's way of defeating enemies with it. Then, from the part of the producer, I associate it with a master who forged weapons, and then from that master, I associate it with the weapons that the master created (connected back, forming a circuit).
In the software I create myself, I use bidirectional links similar to OBSIDIAN to concatenate them.
Using this method, the mental burden I need to bear when recording is simply to consider labeling these notes as necessary, such as # characters, # weapons
In addition, it is to associate "a certain weapon owned by the protagonist" with "a certain weapon forged by the master" and judge it as the same note.
This manifests as a circuit similar to a star map in space.

The specific implementation method is: I create a note and name it "My protagonist", then record something in this note and label it like this: # character. Then, in this note (which is very important, so I don't need to go back outside to operate), I click on "Derived Ideas" in the note, create a new note, and then create the title "Weapons owned by the protagonist". At this point, the software automatically establishes bidirectional links for the two notes, and can freely add or remove other links.
Correspondingly, the previous note 'My protagonist' should also have an echo link, telling me that this note was mentioned by a certain one.
With this method, what I store is not isolated notes, but a series of ideas.
When necessary, I can use labels to identify all "thread"
Unfortunately, these suggestions may significantly increase the complexity of the software, which may lead to the establishment of tag and tag_map, reference_map, sources... tables like this

[martinstoeckli]

The tag tree will make it into the coming release 8.0, it will allow to work similar to a folder structur, but is dynamically built from the tag lists of the notes. This way we can combine the advantage of tags with the advantage of a folder based organization:

[asasn]

Wow, this is really cool! I think our thoughts align in some ways, where everything is about balancing between the "whole" and the "parts."

The entire note system is a whole, but presenting everything at once is meaningless. We need to invest a significant amount of time and effort in selecting the ones we need from countless notes.

Regular string search is one way, but it's based on titles and content strings and feels more like an accidental "coupling."

Tags refine keywords and summarize topics, taking us a step closer.

I think adding double links would make it too large and complex, which is clearly not practical. So, achieving the current stage is just right.

By the way, I'm not sure if it's possible to determine the color/style of notes based on tags.

[martinstoeckli]

Version 8.0 has a new dynamic treeview to filter by tags.