>In fact, in an ideal world, I'd like to plant a very "full featured"
>link, with javascript mouseovers and all sorts. I could generate
>the link very easily in Perl, if only I knew the file names
>to link to. PerlPoint must be able to find the information I need, so
>it can do \XREF. So some way to get the bare XREF information in
>Perl...
>
>Something like...
> xref_destination("foo")
>returning the URL/filename of the relevant page. The function must
>exist, surely: I just don't know its name!
The problem is that embedded Perl ist executed at parsing time, and the
parser doesn't know about any results. HTML results are pages, SDF
results are chapters in a one-in-all document (currently), PPresenter
results are parts of an XML structure. So address resolution is up to a
converter and happens at backend runtime.
Nevertheless, we could pass a tag. A tag *is* intended to be resolved
by a backend. So if we would introduce a new tag ... hm, assumed such a
tag would be there, the problem would remain to be unsolved - something
provided at backend runtime does not help you in Perl code executed at
parsing time.
Ways I currently see to achieve what you are looking for, links build
according to personal preferences:
* pp2html templates provide a keyword/syntax to
include the address of a certain destination.
As part of the template system, this would not
help in slide contents.
* pp2html implements certain wished configurations,
e.g. JavaScript links as suggested, maybe by
settings passed to \...REF tags.
* A very general interface to let users define
how a tag should be resolved by a converter.
This is the most flexible but most difficult
(if ever possible) approach and would need
additional design.
All if these ideas are currently unimplemented. Maybe there are more or
better ones?
Jochen