MJ B
MJ B's Comments
-
- Ideas
- Taxonomy: A "network graph" of supertags, and how they connect via extensions and field instances
-
- Ideas
- For Supertags and Fields, add an Emoji + Icon field that can be displayed instead of the Text ⭐❗ 🚀
Have you tried this? https://tanacommunity.slack.com/archives/C02DP78UXHP/p1726144439882029
Hi all, I am not sure if it's actually a bug, but it FEELS like a :ladybug:
Workflow Setup
- I have a supertag called urgency which is just a number with a field to render an icon (don't mind the "icon" field value)
- I have ordered them top to bottom as you can see (in a place where I store such stuff)
- I have a field I use in various places called Urgency
Outcome
- I use that to set the value, and then render the icon in the title of a node (common pattern). That works just fine
Now, what I don't get is in which order the options are presented when I select the values. They seem to be in a complete random order. As you can see, they clearly don't represent "usage" (frequency).
Painpoint
- It causes unnecessary scrolling selecting of the ones I actually use most frequently. It wastes time!
:thinking_face: How can I fix that?
Thank you! :hugging_face:
-
Without a really thoughtful implementation, this is going to become a UX nightmare when we think about mobile and responsiveness. I'd rather see better "session" management (group of panels persistent) than having to deal with tabs on top of the clunky panels (which is the thing that actually requires fixes IMHO)
-
- Ideas
- Recurring Date Field
In reply to Odin UrdlandOdin Urdland StaffJun 6, 2023 It is worth mentioning that this is possible to build now using the Command Node 'Insert relative date'. Like RJ Nestor has done (a demo of it in use here): https://www.youtube.com/watch?v=6ikLbN0JoeYI have to agree with other commenters: building this out manually is a pain and far from an "elegant solution" from a UX perspective. This should come standard and I am sure you and the team are aware of that. I get that people in the Tana environment build personal businesses around selling such solutions to other Tana users, but once you pay for the software, things look differently.
The homepages claims Tana to be "The everything OS", but only if you literally build everything yourself? It's supposed to be "A game-changer for project management", but only if you spend literal hours (plural) to configure it (and then spend many more to maintain it)?
-
- Ideas
- Taxonomy: A "network graph" of supertags, and how they connect via extensions and field instances
In reply to Grant GochnauerGrant GochnauerOct 11, 2023 One major goal of a visual representation would be to enable refactoring. I think as your Tana graph grows and you realize you need to change supertags around or break things down or perhaps introduce...Yep, just seeing the supertags as a graph would already be super useful vs the regular requests of getting a graph of everything, which is hardly useful (as many existing apps have shown)
-
Also important for basic abbreviations or acronyms as long as they add/reference to the same node
-
- Ideas
- Taxonomy: A "network graph" of supertags, and how they connect via extensions and field instances
Today, you can only see the "X → extends → Y" relationship, but not the "Y → extended by → X" relation.
Having the ability to see "extended by" for each supertag would be really powerful.
As amazing as Tana is, most people will "work the system" quite a bit (or forever), so finding relationship is quite important to clean things up.
-
Would be nice if we could have a setting to "turn off 'build title from fields' in tables"
Background: I prefer to see the "challenge" in the title on daily basis (when I see individual nodes), but it's very much redundant in a table (exercise overview), where I'd rather just see it in the column rather than the node. This gets exacerbated if you build titles from multiple fields
Hi @Matt M , would you mind elaborating how that view helps "debugging the taxonomy", which is one of the main requests? I like the viz itself, I just don't quite understand how it helps me understand the connection and relations between supertags I'm afraid