Better naming for "Folder settings" and "Tree settings"

uzzer123 commented 1 month ago

I have been trying to change the default fonts on my notes ("notes" is what I call the right pane, where we put the content, while "tree" I call the tree structure on the left) and with these namings of "Folder settings" and "Tree settings", I'm still confused what is what.

I would suggest that we call them: tabs, folders and notes:

tabs seem to be currently without font settings :(
folders makes perfect sense for the tree structure on the left; otherwise both trees and folders easily convey the same concept and this is why these namings are so confusing;
notes, I think, is appropriate for the right side content pane. In case "notes" is equivalent enough with "folders" and "tree", it could be changed to "note pane". That is a bit wordy, though.

Stefanoko commented 1 month ago

tabs seem to be currently without font settings :(

Tools > Configuration Options > Chrome Tab-fonts

fitness888 commented 1 month ago

Referring to all tree content as nodes seems to make most sense for me as nodes can either contain text which you see in the text editor on the right while other nodes are used to just group other nodes for better organization. You can't call all nodes folders because folders as we understand them in Windows just contain other folders and you can't call all nodes notes because some nodes contain no notes just other nodes... As for changing the current reference of folders to tabs [located just below toolbar] that might be more intuitive. AllMyNotes works exactly how you are thinking where a folder can only be a folder where notes with text editor go into.

s427 commented 1 month ago

Technically, each and every entry in the left part of the screen (the tree) is a note. Even if it is left empty and used solely to organize sub-notes, it's still a note (an empty note). At any time you can add any text you want to it.

(I agree that calling them "folders" doesn't work.)

uzzer123 commented 1 month ago

tabs seem to be currently without font settings :(

Tools > Configuration Options > Chrome

Hm, thanks, most unexpected place and naming for tabs settings. I'd expect them in the "Default settings" dialogue and what does "Chrome" mean in this context, for Christ's sake?

dpradov commented 1 month ago

You can't call all nodes folders because folders as we understand them in Windows just contain other folders and you can't call all nodes notes because some nodes contain no notes just other nodes...

Well, currently all nodes are exactly the same, as @s427 correctly pointed out. They all can contain text and all of them can have a parent (except TOP nodes, obviously) and childs. That's why I call of them 'notes'. If some note in your case is only a container to other notes and it doesn't contain text by itself is up to you. But at any time you can add text.

That said, it's true that there are things that can be improved. I'll also tell you the following in advance. I have a series of ideas that I want to gradually incorporate, but I need to do it little by little, as I need to refactor a lot of code (hundreds, if not more, lines of code), always keeping in mind that what I do must allow recognition of the current format, to which I am evolving.

Among the things I am considering is having a list of "notes", where each one is initially independent in itself. Each of these "notes" can appear in one or several trees, in the form of "nodes". Moreover, there may be notes that do not appear in any tree, and this will not prevent them from being located. The fact of appearing in one or more trees allows the note to inherit the corresponding relationships based on the hierarchy, and where the tags presented by these notes with which it relates can be taken into account simultaneously.

For me a “folder” is an entity that allows “notes” to be grouped, in which it is possible to establish hierarchical relationships. The tree is the visual representation of them. But apart from that tree, the concept of a "folder" allows defining default properties that affect all the included notes. It also adds a possible 'context' to the note. (Apart from the relationships derived from the tree, it will be possible to establish others not based on this hierarchy of neighboring nodes. I'll clarify it little by little. An example could be having on hand, whenever we work with a certain note or given subtree, another series of notes as resources.)

Although currently each tree node corresponds to a note, and therefore each node has an associated ID (and recently a GID, GlobalD), I am considering the possibility that the trees allow combining nodes that represent notes (as until now) and even nodes that represent tags. In fact, I think that probably many of us often use nodes for that purpose, to group/tag notes. For example, we can have a node "Errors" and underneath multiple nodes (notes) with different 'errors'

It is something I need to think about carefully. But right now, I need to have an architecture that allows me to progress, and that’s why I am first refactoring what exists. I have many other ideas that will try to improve the possibilities that KeyNote offers, mainly in note management. I will clarify them as I am able to incorporate them in future versions.

As for changing the current reference of folders to tabs [located just below toolbar] that might be more intuitive.

Maybe, but the problem is that Tab has a visual connotation (at least it seems that way to me), and I need to not limit myself to that. In fact, I am considering offering different ways to visually display the different groups of notes (which I currently call "folders"). The current way, in which each folder has a single tab, does not have to be the only and most convenient way at all times. When I changed the terminology to Folders/Notes, I tried to find a term that was intuitive and that would work for grouping, filing, etc., multiple notes. And after many searches and alternatives it seemed to me that 'folder' could be suitable.

I agree that calling them "folders" doesn't work

Propose names to me and I will consider them. They should serve as a way to group notes, but don't just think about what KeyNote offers right now, where each 'folder' is built 'by hand'. My intention is for there to be folders where the content is dynamic, for example reflecting the content of a search (eg. notes tagged 'important' and meeting any other conditions). These dynamic folders can also deliver the result through a hierarchy, using existing hierarchical relationships. 'Views' was another term I was tossing around.

uzzer123 commented 1 month ago

@dpradov yup, it is really plenty of work both on the concept development side and the rough coding work side. As far as the former is concerned, I'd like to suggest you a great method, which I am currently exploring myself: Object-oriented UX (OOUX). It is an approach meant exactly for planning complex interfaces.

fitness888 commented 1 month ago

https://github.com/dpradov/keynote-nf/issues/709#issuecomment-2138220777

Thank you dpradov for all that insight! For me I'm happy providing some input but I have no real understanding how they get implemented into the code...I leave that to you!

s427 commented 1 month ago

I agree that calling them "folders" doesn't work
Propose names to me and I will consider them.

To clarify, I was talking about uzzer123's proposition that the tree structure should be called "folders".

fitness888 commented 1 month ago

tabs seem to be currently without font settings :(

Tools > Configuration Options > Chrome

Hm, thanks, most unexpected place and naming for tabs settings. I'd expect them in the "Default settings" dialogue and what does "Chrome" mean in this context, for Christ's sake?

Chrome in reference to software settings refers to the changes you can make to the graphic user interface including colour, font, size, and other characteristics.

Stefanoko commented 1 month ago

Binder — my suggestion in lieu of "folder".

dpradov / keynote-nf

Better naming for "Folder settings" and "Tree settings" #709