From: Sebastian Rose <sebastian_rose@gmx.de>
To: nicholas.dokos@hp.com
Cc: Emacs-orgmode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Advice needed. Use links or blocks?
Date: Fri, 03 Sep 2010 17:23:28 +0200 [thread overview]
Message-ID: <878w3ic0lr.fsf@gmx.de> (raw)
In-Reply-To: <12255.1283484172@gamaville.dokosmarshall.org> (Nick Dokos's message of "Thu, 02 Sep 2010 23:22:52 -0400")
Nick Dokos <nicholas.dokos@hp.com> writes:
> Sebastian Rose <sebastian_rose@gmx.de> wrote:
>
>
>> the attached file fetches background tiles from openstreetmap.org for
>> me, and produces SVG images of tracks I ran. Unfortunately, I cannot
>> find a good way to use that code in an automated way.
>>
>> What I'd like to do, is to have the coords in my training diary, and
>> produce the images on demand. When I publish the diary to HTML, I want
>> the coords to be replaced with a link to the image.
>>
>> Here is an example of the coords (just two), as I save them in my diary:
>>
>> '((9.707136154065665 52.3705158282501)(9.711406230817374 52.37525815071791))
>>
>>
>> And this is, how the function to produce the images is used:
>>
>> (osm-draw-track
>> ;; Fantasy-track in Brisbane:
>> '((152.968 -27.533) (152.968 -27.546) (152.974 -27.537))
>> "Track_in_Brisbane"
>> 8)
>>
>>
>>
>> Should I go for a special link type:
>>
>> [[track:((152.968 -27.533) (152.968 -27.546))][2010-09-03 in Brisbane]]
>>
>> ??
>>
>>
>> Right now, I produce a lisp file, that produces all those images using
>> `osm-draw-tracks' and add simple links. But this is inconvenient and
>> prone to error (forgotten tracks)...
>>
>
> Very cool indeed. I am certainly not an expert but I thought I'd remind you
> of a vaguely similar idea that Julien Danjou implemented with his
> org-location-google-maps.el: he stores the location in the LOCATION property
> of an entry.
>
> Maybe a TRACK property, possibly accompanied by an ID that will link to
> the SVG as an attachment and act as a cache? And other fields can be added
> at will (name, date, completion time, amount of water drunk :-) etc.)
I have those kind of properties. Start-time, pace, etc.
But I was hoping to make it usefull for other purposes, too. One could
have more than just one track in a section. E.g. one for the warm-up,
one for the competition.
Actually, I'd like to click somewhere and see the track in an extra
frame. In Emacs and in my Browser. That's why I was thinking about
links.
As I look into `C-h f org-add-link-type' I guess links are indeed the
way to go.
BTW: I like OSM better, because it includes cycling paths and stuff like
that as well as more detail in general (phone boths, stores etc.). For
runners, google maps are useless.
Sebastian
next prev parent reply other threads:[~2010-09-03 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 0:28 Advice needed. Use links or blocks? Sebastian Rose
2010-09-03 3:22 ` Nick Dokos
2010-09-03 15:23 ` Sebastian Rose [this message]
2010-09-12 11:23 ` David Maus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878w3ic0lr.fsf@gmx.de \
--to=sebastian_rose@gmx.de \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).