develooper Front page | perl.perlpoint | Postings from January 2002

Re: Building user designed links (was: Another "simple" problem)

Thread Previous
From:
Robert Inder
Date:
January 30, 2002 15:32
Subject:
Re: Building user designed links (was: Another "simple" problem)
Message ID:
f517kpzxvjz.fsf@auk.3lg.org

>>>>> Jochen Stenzel writes:
    > To: "Robert Inder" <robert@interactive.co.uk>
    > Cc: "perlpoint@perl.org" <perlpoint@perl.org>
    > Date: Wed, 30 Jan 2002 22:00:02 +0100
    > Subject: Building user designed links (was: Another "simple" problem)

    :
    :
    > 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.
Yes it does.

My perl at run-time does not know what the name of the slide/file
is going to be.  But it can NAME that filename: it can plant a
tag that will be turned into it.  So the perl could return

  <A HREF='\REFID{name="Section 2"}' 
     onmouseover="alert('Read this first')">The Second Section</A>

knowing that it would turn into...

  <A HREF='slide0012' onmouseover="alert('Read this first')">The Second Section</A>

or whatever...

    > 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.
So I, of course, want both of these:-)


    >   * 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.
Indeed.

Perhaps something like:
   Any unknown tag "\FOO" 
   causes PerlPoint to call the function FOO with two arguments:
       a hash of the arguments given to the tag, and
       the body of the tag.
   The string returned by the tag is taken as its expansion.   
   
    > All if these ideas are currently unimplemented. Maybe there are more or
    > better ones?

    >                       Jochen

Robert.

------------------------------------------------------------------------
Robert Inder   Interactive Information Limited,           07770 30 40 52
               3, Lauriston Gardens,    Edinburgh    EH3 9HH    SCOTLAND
------------------------------------------------------------------------

Thread Previous


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About