Ideas and proposals

[llcc]

Orgro has gradually become the most elegant and best viewer for Orgmode documents on mobile after extensive polishing, also, it holds the potential to become one of the top Orgmode editors in the future. For further development of Orgro, I'd like to open this discussion to gather ideas and proposals to make Orgro even better.

Key Improvement Areas:

1. Org Agenda. This feature has been requested in Issue Agenda View #92. Implementing a functional Org agenda will greatly enhance productivity.
2. Enhance the buffer or section editor.
3. Powerful Image Editor. I found that editing and annotating images feels more intuitive on mobile, especially with an Apple Pencil. Currently, long-pressing an image opens it in a viewer, we can integrate the pro_image_editor package to provide image annotation functionality for orgro.
4. Performance Optimization metioned in Issue Bad performance on large files #52. I also feel the pain of noticed lag when scrolling, cycling through headlines or documents, or searching in the Sparse Tree. As @amake mentioned, this is a long-term challenge. However, in the short term, adding a performance metrics UI could help gather bottleneck data for further optimization.
5. Ecosystem and Plugins. In the long run, Orgro could benefit from a plugin system to allow third-party or user-defined code to connect with the app. This could address suggestions like those in Issue Support for Org-drill #87 and Issue Open linked PDF files on device's default viewer or web browser #97 if the community loves to contribute. For example, an in-app PDF viewer using packages like (flutter_cached_pdfview or flutter_pdfview ) can be implemented. Developing more plugins would expand Orgro’s functionality even further.

More ideas and proposals are welcomed.

[llcc]

Another one:
The following Org meta line should be treated as same as table controller.

#+call: , #+caption: , #+tblfm:

[amake]

I'm not sure what you mean by "same as table controller". Can you clarify?

[llcc]

The above meta lines should be scrollable horizontally, similar to the table. Specifically, the #+tlbfm line, which belongs to the table, would be better to scroll together with the table.

[amake]

In v1.46.2 meta lines will scroll horizontally in Reader Mode. #+tlbfm won't get special treatment yet.

[llcc]

Great if https://github.com/nobiot/org-transclusion can be implemented.

[llcc]

Org property inheritance is not supported yet.

The following feature is also not supported.

If you want to add to the value of an existing property, append a ‘+’ to the property name. The following results in the property ‘var’ having the value ‘foo=1 bar=2’.

#+PROPERTY: var  foo=1
#+PROPERTY: var+ bar=2 

[kresdjan]

Font suggestion. Add Cascadia Code to list of fonts. https://github.com/microsoft/cascadia-code

[amake]

This will be available in v1.46.0, ready for testing now:

• iOS
• Android