From: Jens-Uwe Morawski <morawski@gmx.net>
Subject: Re: Re[2]: [NTG-context] Frames (collection of)
Date: Sat, 19 Oct 2002 12:48:10 +0200 [thread overview]
Message-ID: <20021019124810.2b5bd893.morawski@gmx.net> (raw)
In-Reply-To: <4920069528.20021018150410@iol.it>
On Fri, 18 Oct 2002 15:04:10 +0200
Giuseppe Bilotta <gip.bilotta@iol.it> wrote:
>
> Friday, October 18, 2002 Jens-Uwe Morawski wrote:
>
> JUM> On Thu, 17 Oct 2002 19:06:12 +0200
> JUM> Giuseppe Bilotta <gip.bilotta@iol.it> wrote:
>
> >> Hello,
> >>
> >> I'm working on an extension of tooltips (see attached file) whose
> >> primary goal is for use "instead of" footnotes in interactive
> >> documents.
>
> >> Suggestions for improvements are more than welcome
>
> JUM> I really would like to see this feature as part of the core:
> JUM> \setupfootnotes[...,location=tooltip,...]
>
> JUM> This way one can use the normal \footnote command for a print
> JUM> and interactive version of a document.
>
> There are at least three things that need to be done to add this
> to the core in a fully ConTeXtish way:
>
> (1) add frame classes
if you mean something like
\defineframed[<name>]
\setupframed[<name>][...]
\<name>{..text..}
then i think this on the wish list of many ConteXt users.
Commands that currently support framed-parameters could then
support a parameter framedclass=<name>
> (2) add tooltip classes
in the other mail-thread we agree that for tooltips the whole word
should be an active area. IMO, this is not the best solution. If we
can use tooltips for footnotes or bib-entries in the future, those
elements will show a mark/symbol in the text, but for normal tooltips
the problem is that nothing shows the reader of the document that
there is a tooltip available. I think it is not a common practice to
read a document and scan constantly the words with the pointing
device. Thus, there should be also for normal tooltips a symbol or
something else that indicates the tooltip.
Best,
Jens
_______________________________________________
ntg-context mailing list
ntg-context@ref.ntg.nl
http://ref.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2002-10-19 10:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 17:06 Giuseppe Bilotta
2002-10-17 23:52 ` Jens-Uwe Morawski
2002-10-18 0:50 ` Bruce D'Arcus
2002-10-18 13:04 ` Re[2]: " Giuseppe Bilotta
2002-10-19 10:48 ` Jens-Uwe Morawski [this message]
2002-10-19 12:31 ` Re[4]: " Giuseppe Bilotta
2002-10-20 16:51 ` Hans Hagen
2002-10-20 19:39 ` Re[5]: " Giuseppe Bilotta
2002-10-21 11:46 ` Re[4]: " Jens-Uwe Morawski
2002-10-21 13:13 ` Re[6]: " Giuseppe Bilotta
2002-10-21 13:31 ` Re[4]: " Taco Hoekwater
2002-10-21 20:30 ` Jens-Uwe Morawski
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021019124810.2b5bd893.morawski@gmx.net \
--to=morawski@gmx.net \
/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.
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 NNTP newsgroup(s).