two colors anchors (encore)
Lutz Raymond
ma...@ncsa.uiuc.edu (Marc Andreessen) replies to my post
>In article <CG8nA...@cc.umontreal.ca> lut...@ERE.UMontreal.CA (Lutz
>Raymond) writes:
>
> conceptually going forward -> "Go, tell me more"
>
> conceptually going backward -> "Huh? Wazat?"
>
> These two kinds of link should be differently displayed...
>
>This is the type of thing that can be done easily in the document,
>particularly if you are using inlined images. See, e.g., GNN, which
>has a consistent set of little inlined images it uses for hyperlinks,
>with terms like "GET", "GO", etc. You could have little icons for
>"Tell me more", "Huh?", etc. and use those with your hyperlinks.
>
Thanks for your reply but I think didn't explain myself precisely
enough... (or is it my English? :^). Here's an example of a notion
I could write in a math courseware:
Conical curves are produced by the
intersection between a plane and two cones.
Orientation of the plane determines the
curve shape and if it is open or closed.
From there one could want to see a 3D illustration of a plane
cutting through a cone, or to explore effects of the plane
orientation on the curve shape. These are "Go ahead"
links, and anchors could be respectively the "intersection" and
"Orientation" words (not necessarily).
Conical curves are produced by the
intersection[1] between a plane and two cones.
Orientation[2] of the plane determines the
curve shape and if it is open or closed.
Note that "Go ahead" link doesn't imply a linear path already
set by the author. It means: "OK, I understand what is in this node
and want to know *more* about [anchor word]"
But what if the hypernaut doesn't understand notions that are
prerequisites to this node? Here, links for concepts like curve,
plane and cone should be offered... Those are "Huh?" links and
are as important as "Go" ones. Maybe this node is the first one
in all my course the hypernaut is dropping in (sentence?) Remember,
"There is no top to the World Wide Web..." (TM) 8^)
The problem is that you can mistake "Huh?" links for "Go" ones and
move to an unwanted node:
Conical curves[1] are produced by the
intersection[2] between a plane[3] and two cones[4].
Orientation[5] of the plane determines the
curve shape and if it is open or closed.
Hence my suggestion that only "Go" links should be displayed
initially on entering the node: "Help" links for prerequisite notions
could be revealed with an <ALT> key (then normal links could in turn
be un-identified).
Explicitly describing the types of the link in the text is unwieldy...
Conical curves (if you don't know what a curve is,
click here[1]) are produced by the intersection
(click here[2] to see more) between a plane
(what's a plane is explained there[3]) and two
cones (go there[4] to get a definition of cone).
Orientation of the plane determines the
curve shape and if it is open or closed (more on
orientation effect is shown there[5]) .
8^)
--
Raymond Lutz, etudiant 2e cycle
matiere condensee, departement de physique
Universite de Montreal, Canada
NeXTdimension cube newbie wannabie
Steve Toleque
>
>in article <MARCA.93N...@wintermute.ncsa.uiuc.edu>,
>ma...@ncsa.uiuc.edu (Marc Andreessen) replies to my post
>
>>In article <CG8nA...@cc.umontreal.ca> lut...@ERE.UMontreal.CA (Lutz
>>Raymond) writes:
>>
How about this for a possible solution:
two pages: one plain, the other with additional links
you move from on to the other with a [expand] or [summarize] button
Steve.
54312-J.ELLSON(HOP671)NONE
by stol...@qrc.com (Steve Toleque):
> In article <CGELF...@cc.umontreal.ca>,
> lut...@ERE.UMontreal.CA (Lutz Raymond) says:
>>in article <MARCA.93N...@wintermute.ncsa.uiuc.edu>,
>>ma...@ncsa.uiuc.edu (Marc Andreessen) replies to my post
>>>In article <CG8nA...@cc.umontreal.ca> lut...@ERE.UMontreal.CA (Lutz
>>>Raymond) writes:
...
>>Hence my suggestion that only "Go" links should be displayed
>>initially on entering the node: "Help" links for prerequisite notions
>>could be revealed with an <ALT> key (then normal links could in turn
>>be un-identified).
...
> How about this for a possible solution:
>
> two pages: one plain, the other with additional links
> you move from on to the other with a [expand] or [summarize] button
But why only two? Someone else recently suggested that it would be
nice to have links to dictionary and thesauras from every word.
Isn't there a more general mechanism that could allow an arbitrary
number of links to originate from a word or phrase?
John Ellson
AT&T Bell Labs
Joe English
54312-J.ELLSON(HOP671)NONE <ell...@hogpg.att.com> wrote:
>>>>In article <CG8nA...@cc.umontreal.ca> lut...@ERE.UMontreal.CA (Lutz
>>>>Raymond) writes:
>...
>>>Hence my suggestion that only "Go" links should be displayed
>>>initially on entering the node: "Help" links for prerequisite notions
>>>could be revealed with an <ALT> key (then normal links could in turn
>>>be un-identified).
>
>But why only two? Someone else recently suggested that it would be
>nice to have links to dictionary and thesauras from every word.
>
>Isn't there a more general mechanism that could allow an arbitrary
>number of links to originate from a word or phrase?
<A> elements have a REL attribute which could be
used for this puprpose; perhaps the HTML+ draft
<RENDER> feature could be extended to work with
these as well.
Something like this in the <HEAD> element:
<RENDER rel=goforward color=red emph=b>
<!-- Show "Forward" links in red boldface -->
<RENDER rel=wuzzat color=blue emph=i>
<!-- Show "Backward" links in blue italics -->
<!-- I don't remember if 'color' and 'emph' are actually
supported in the current draft; it's something like that though.
Maybe an icon= attribute too?
-->
would be a hint to the browser to display
<A rel=goforward href="moreinfo.html">this link</A>
in one style and
<A rel=wuzzat href="explain.html">this link</A>
in another.
This would offer quite a bit of flexibility
in displaying different link styles, since
the document designer/author would be able
to choose whatever logical link roles are
appropriate for each document.
Some problems might occur if the browser reserved
those emphasis attributes for links to begin with;
for example, if a user had configured Mosaic to show
unvisited links in red and visited ones in blue,
the document-directed styles would conflict with
the user-directed styles. You'd also have to be
careful to support monochrome screens and tty-based
browsers, as usual.
--Joe English