tags Feature request

[asasn]

#221 I've read it.
Now the software has become very useful, but as the number of Notes has increased, some things are not easy to find,
Perhaps can set up something like '#aaa/bbb/ccc' to implement the classification.

[martinstoeckli]

Thanks for the suggestion, this could be done without increasing the complexity of operation. The tags could be automatically grouped to a tree, each branch showing only the remaining tags which are available in notes with the parent tag. I will keep it this mind as a future improvement, but probably not yet for the upcoming version 8.

[asasn]

Thanks for the suggestion, this could be done without increasing the complexity of operation. The tags could be automatically grouped to a tree, each branch showing only the remaining tags which are available in notes with the parent tag. I will keep it this mind as a future improvement, but probably not yet for the upcoming version 8.

Translated from Baidu:
Hello, dear software creator, it seems that you have plans to provide the future version 8.0. Before that, I would like to take this opportunity to chat with you about the development direction in my mind.
This software is indeed a rare and good product, but in current view, it is more like a ListView system than a TreeView system, which also makes it difficult to practice Zettelkasten (card box note taking method) in it.
However, I believe that the change from ListView to TreeView is feasible, combined with a more user-friendly tree label and keyword search system (I hope to customize the keyword search bar and fix it as another label to facilitate search aggregation)
This will enable this software to perform Zettelkasten (card box note taking method), which will be a transformation.

In addition, it would be even better if nuget's wpf control could be provided to facilitate integration into other wpf products.
Download as a control through nuget, provide a RootNode, as well as its primary, secondary, tertiary, and quaternary topics, etc., and include its children in the form of ObservableCollection.
In this way, scalability becomes even stronger.
(By the way, I also try to integrate it into my own software normally, but I am just an amateur and don't quite understand the source code... This is really a difficult thing. If it's convenient, would you consider porting it to Nuget as a control?)

The above are just some immature personal ideas, some of which may require a lot of work to implement, for reference only.

[martinstoeckli]

Hello Asasn, I think I understood it correctly, a treeview would be the control of choice. All tags of the selected branch could be combined with a logical AND to filter the notes. The databinding will require a nested ViewModel, so there are no limits to how many levels a branch can have, it would depend on the number of tags in a note. The ViewModel could determine the child nodes on demand when the user expands a node.

At the moment I'm pretty sure that version 8 will contain the transition to Blazor/Hybrid (a big part of the code is already ported and running). I used the MudBlazor library (not WPF) and therefore the treeview of MudBlazor would be the obvious choice, here you can see some examples:
https://www.mudblazor.com/components/treeview#itemtemplate

[asasn]

Hello Martinstoeckli, The following content is translated from Chinese through Baidu:

Zettelkastan just "looks like a tree structure", The important thing is , notes need a theoretical support, everything is for "easier input" and "faster and more accurate finding".
I have seen many products before and found that some are doing "stress free recording", while others are doing "big and comprehensive content". This is just like dialectical and contradictory philosophical thinking, and sometimes they are contradictory and mutually influencing.
When we input too easily, the number of notes is easy to pile up, and when we input too much trouble, we don't want to record at all.
I think the significance of software may be to help us with our lives, work, and studies.
The "second brain" is the concept of commercial companies such as Obsedian and Notion, which are trying to create powerful tools that are large and comprehensive. Unfortunately, those software are too large and have too many functions, sometimes making it difficult for people to start, and various privacy issues are also difficult to trust.
It is rare for your software to be able to maintain restraint and achieve "small and beautiful", which is truly a gratifying thing.
I don't know if you have ever been familiar with Zettelkasten. Its philosophy is to believe that there is an internal connection between knowledge. We make cards one after another and connect them in specific ways, so that they can present a connected relationship internally, and quickly find what we need when using them.
(This way of working is similar to brain neurons)

---

Main viewpoints

• There may be connections between any cards (notes), so try not to isolate them as much as possible;
• What you create is a web of ideas composed of your thoughts, opinions, inspirations, or specific knowledge encountered;
• Adhere to the Atomicity principle of notes, where each note only contains one knowledge point (This is actually a decoupling of knowledge!)
• Prioritize connecting notes rather than just collecting them;
• Each note is a separate address, and connections are established between notes through two-way links;
• The entry point for notes is the index, but more efficient is the subject;
• Strong discovery ability;

[martinstoeckli]

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