Thanks for the clarification. I am going to look into this in more detail in due course.
Note, I'm suggesting providing an Elisp function that we could add to our .emacs file. Using that as a base, we could then create other functions to get information from other databases and format it appropriately for BeOrg. Eventually, you could collect Elisp functions and build a Beorg library to put up on MELPA. You could also build a Scheme library to go with it.
The key right now is getting the Location on Tasks.
This sounds an interesting idea. I guess to make it user friendly there should be an easy way to add standard properties to an entry from the property editor - such as setting a property containing a location either picked from the map, the users current location or text which is processed by the iOS geocoder. These standard properties would also be recognised so that the user could tap the location property and see a map with a pin.
It would be good to see if there is interest on this functionality from other users.
I like the new calendar sync option, but it needs to set location as well. That would allow the calendar to provide an interface between Org -> BeOrg -> Maps. I'd suggest creating an Org Property (say org-beorg-addr) that can be put into a Task by an Org function that you create (we add it to our emacs.el) that takes input of a properly formatted address and stores it in the Org Property that Beorg could then pick up and add to the iOS calendar. The standard iOS Calendar program could then push the address to Maps which could then plot how you get to your meeting. Using you Org function as a base, we could later create other functions to (say) get the address out of various contact databases.
What do you think?
1 person likes this idea