orgzly-revived / orgzly-android-revived

Outliner for taking notes and managing to-do lists
https://www.orgzlyrevived.com
GNU General Public License v3.0
677 stars 42 forks source link

Many feature requests, prioritized #88

Open 9z0 opened 1 year ago

9z0 commented 1 year ago

I was involved in feature requests in the original repo. Here they are in order of importance and expected ease of implementation and thank you for reviving Orgzly!

High priority or easy to implement:


Medium priority:


Low priority:


Bug:

Thanks a lot!

alensiljak commented 1 year ago

I think 819 is already there in some form. Have you tried the current version's settings?

9z0 commented 1 year ago

I think 819 is already there in some form. Have you tried the current version's settings?

Not yet. I am waiting a bit until potential early bugs are dealt with.

alensiljak commented 1 year ago

Not yet. I am waiting a bit until potential early bugs are dealt with.

How will we know unless you try it out? :D

I've been using the 1.8.12 since it was published on F-Droid and have not experienced any issues. But my use cases may differ. In any case, the signature is different to Orgzly so you can have both installed.

I'm using git so can track the changes made by the app. I can only recommend doing something similar, if not already.

9z0 commented 1 year ago

How will we know unless you try it out? :D

You are right! But I am afraid of data-losing bugs that may go unnoticed by me even though I do regular backups.

I have added some issues to the first post for your consideration, prefixed by (new).

stefan2904 commented 1 year ago
9z0 commented 1 year ago

Not quiet.

The PR is about sorting contents of a note.

353 is about sorting notes themselves under the parent note/notebook.

GfEW commented 3 weeks ago

@9z0

That's a great issue collection! Some of those are also in my own orgzly-revived reporting pipeline. Hope I get around to filing them, over time.

However, there are many more gems in your list. Do you consider recreating them here? I'm not overly confident it makes sense to discuss orgzly-revived issues in the orgzly repo.