Forum Posts Feed
Zavala - An open source outliner for Macs, iPads, and iPhones
< Next Topic | Back to topic list | Previous Topic >
Pages: ‹ First < 4 5 6 7 8 9 10 11 12 > Last ›
Posted by Maurice Parker
Oct 24, 2021 at 08:20 AM
Yeah, unfortunately the quality of Apple’s software isn’t what it used to be. Quirks like this can be really frustrating.
Posted by Larry_in_Bangkok
Oct 26, 2021 at 12:46 PM
Darren McDonald wrote:
>I would like to see in an outliner what Brett Terpstra states in his
>blog when he wrote about the Tree app;
>a horizontal view of the outline.
For a horizontal view of the outline, you can find that today in SimpleMind Pro.
The outliner feature is simple, basic, but it works smoothly, is totally reliable, and is updated frequently.
I’ve been using SimpleMing Pro for many years.
I just wrote about it elsewhere on this forum, so here I’ll put just a link, not a double post:
https://www.outlinersoftware.com/topics/viewt/9131/20
Posted by Maurice Parker
Oct 26, 2021 at 05:10 PM
I don’t have a mind-map or tree view on the roadmap yet. It probably won’t happen before version 3 as version 2 is well in development with a new set of features.
Here is the GitHub issue to track it if you want to add any requests about how it should work.
https://github.com/vincode-io/Zavala/issues/129
Posted by Maurice Parker
Oct 29, 2021 at 04:01 PM
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 satis
Oct 30, 2021 at 07:08 PM
Your blog post was very thoughtful, Maurice. Your idea to show metadata inline would probably benefit most on smaller iPhone screens, but might confuse some who would think of them as tags. But I think it might benefit users to simply *call* them tags, with which people are already conceptually familiar, compared to introducing a relatively obscure idea of columns in a category that itself isn’t too commonly used.
I don’t commonly use columns in OmniOutliner but when I do it’s typically to simulate checkboxes because I detest the all-or-nothing approach in which I’m forced to see superfluous checkboxes throughout a long outline when I just need it in a few child-nodes. (Over the years people have requested that changed in OO but it’s apparently not on the horizon.) I use columns primarily on the Mac, and while it’s not ideal to view on iOS for me it’s read-only, so that’s not a significant issue.
When metadata/tags are embedded inline the eye has to scan all over the screen (based on the length of the content) to find and read the metadata results. With columns it’s just easier to see and compare metadata, which is why I personally prefer it for my own uses.