Outliner Software Forum RSS Feed Forum Posts Feed

Subscribe by Email

CRIMP Defined

 

Tip Jar

Zavala - An open source outliner for Macs, iPads, and iPhones

< Next Topic | Back to topic list | Previous Topic >

Pages: ‹ First  < 6 7 8 9 10 11 12 13 14 >  Last ›

Posted by Stephen Zeoli
Oct 31, 2021 at 03:30 PM

 

Hi, Maurice,

For what they are worth, here are a few thoughts about your question:

First, if you’re trying to distinguish your outline manager from a spreadsheet, I would suggest avoiding the term row, as that is very spreadsheet oriented. Since a “row” can be a note, headline, or subhead, I can see the allure of finding a generic term for it. Perhaps “node” would work.

Second, since meta data means data about data, saying “row meta data” is saying row data about data, when what you really want to say is data about row data… or meta row data… would be more accurate.

So my suggestion is to call it meta node data… Probably I’m just over-thinking this, so feel free to ignore.

BTW, Zavala is a nice app. Thank you for making it available!

Steve

Maurice Parker wrote:
I could use some community feedback on how Zavala should incorporate
>Columns or what I call Row Metadata.
> >https://zavala.vincode.io/2021/10/29/Row-Metadata-Proposal.html
> >You can comment here or in the linked GitHub Discussion. Thanks!

 


Posted by Maurice Parker
Oct 31, 2021 at 04:06 PM

 

Thanks for the suggestion. I think “meta node data” has basically the same problem as “row metadata”, even though it is technically more accurate. It isn’t accessible to the average user and will probably scare them off. This new feature is mostly for advanced users, but I still don’t want new users seeing it and getting freaked out.

 


Posted by satis
Nov 1, 2021 at 04:25 PM

 

> I use “tag” to identify a way of categorizing and organizing outlines.
> Using it differently when applied towards rows is going to be confusing.

Perhaps use tags for the metadata and rename current ‘tags’?

 


Posted by Maurice Parker
Nov 2, 2021 at 12:19 AM

 

satis wrote:
> >Perhaps use tags for the metadata and rename current ‘tags’?

The confusion I see with this approach is that macOS already has the concept of tags in it for some apps, like the Finder and Reminders. These are always just a single field, most often just a single word. The metadata will be key/value pairs, so it isn’t the best fit.

I’ve heard of hierarchal tags before, which may be what you are referencing? Maybe some kind of adjective+“tag” might work. The Row Metadata could be, Row Tags, Hierarchal Tags, or something else.

“Badges” might work. “Markers” is another candidate. (I had to hit up a Thesaurus.) “Tokens” hasn’t been completely ruled out yet.

 


Posted by satis
Nov 2, 2021 at 03:24 AM

 

Badges is not a bad term.

Bear, Obsidian and NotePlan have the ability to do ‘nested tags’.

https://help.noteplan.co/article/116-nested-tags

 


Pages: ‹ First  < 6 7 8 9 10 11 12 13 14 >  Last ›

Back to topic list