Agenda views already configured in Org mode should be transfered to MobileOrg

[mgmart]

Agenda views already configured in Org mode should be transfered to MobileOrg

I would like to disregard this requirement because it would complicate the architecture if we would foresee this as a future feature.

[mgmart]

Link into the specification document do not work as expected.
This is the linked text:

The iOS’ UI works completely different to the UI Emacs serves. To provide a way where Org’s agendas could be reused within MobileOrg would complicate the software architecture. Configurable Agendas could be solution to fulfil the requirement in some way.

@abradd are you aware of this dicussion?

[abradd]

I was not aware, thanks for letting me know.

I agree that implementing this would not be an easy task. Do you have an ideas for how to implement agenda views in MobileOrg itself?

In my mind, the way I saw this working was to import the existing agenda views from a configuration file and have them translated to whatever internal mechanism MobileOrg uses for generating agendas. The translation itself would still be a significant amount of work though.

I am not against discarding this feature if it seems too burdensome. It was really more of a nicety than a must have feature.

[mgmart]

Maybe we should provide the org-mode default agendas in an iOS L&F way.

From the org-mode documentation:

The built-in views.

Weekly/daily agenda: The calendar page with current tasks
Global TODO list: All unfinished action items
Matching tags and properties: Structured information with fine-tuned search
Timeline: Time-sorted view for single file
Search view: Find entries by searching for text
Stuck projects: Find projects you need to review

I've never customised my agenda in org-mode. Therefore I'm unsure what we would probably miss. Could you provide some examples of your customised agendas?

If we would implement git-sync we would not be restricted by org-mobile.el. How would we attach the agenda-configuration which is in emacs.el (right?) to the org-files then? In a way that it is not too troublesome for the user?

[abradd]

 ("w" "Work 2 day view"
 ((agenda "" (
     (org-agenda-skip-function
     '(org-agenda-skip-entry-if 'notregexp ":@work:"))
     (org-agenda-start-on-weekday nil)
     (org-agenda-span 2))) 
   (tags-todo "@work") 
   )) 

This is one of my custom agendas, it is actually a block agenda so it presents both an agenda and a tags-todo beneath it seprated by a line. I see this type of setup fairly frequently when people filter for things not covered by the org-agenda builtins. Namely, I define the org-agenda-skip function to skip headings based on a regexp. Also checkout Custom agenda views and Block agendas.

I would assume most people have their org-custom-agenda-commands in their emacs.el, though I don't think there is a strict requirement for that to be the case. I'm not sure what you mean by attaching agenda-configuration to the org-files?

[mgmart]

Thank you, that helps a lot.

I'm not sure what you mean by attaching agenda-configuration to the org-files?

If we want to reuse the agenda configuration made in emacs, we would need a way to transfer them to MobileOrg. org-mobile.el could of course be extended to achieve that. But if we would also support git then there might be a problem.