Question about images...
Rick E Romkey
People have been chatting about XMosaic supporting GIF's and X pics.
Are you talking about Xmosaic using XV or does Mosaic actually handle
images itself?
I looked in the source file, xresources.h and it has definitions for
Mosaic to use whatever viewer you want....should I changed the
entry for GIF to something other than XV to make Mosaic work
nice and fast?
Rick.
Rick Romkey
Advanced Computing Technology
United Technologies Research
Marc Andreessen
<r...@sun1x.res.utc.com> writes:
People have been chatting about XMosaic supporting GIF's and X pics.
Are you talking about Xmosaic using XV or does Mosaic actually handle
images itself?
Mosaic does both -- to used inlined images (as opposed to using xv),
use the IMG tag in an HTML document, like so: <IMG SRC="myimage.gif">,
where "myimage.gif" can be the URL of your choice pointing to GIF or
XBM image.
This should probably be better documented (there, I said it before you
could :-).
Cheers,
Marc
--
Marc Andreessen
Software Development Group
National Center for Supercomputing Applications
ma...@ncsa.uiuc.edu
Rick E Romkey
Andreessen, ma...@ncsa.uiuc.edu writes:
>Mosaic does both -- to used inlined images (as opposed to using xv),
>use the IMG tag in an HTML document, like so: <IMG SRC="myimage.gif">,
>where "myimage.gif" can be the URL of your choice pointing to GIF or
>XBM image.
>
>This should probably be better documented (there, I said it before you
>could :-).
>
>Cheers,
>Marc
Well that was pretty damn cool!
But how do I just put a link to an image instead of actually displaying
it?
If I do <A NAME=0 HREF=myimage.gif>My pretty picture</A>, it always
defaults to using XView...
Rick.
Marc VanHeyningen
>But how do I just put a link to an image instead of actually displaying
>it?
>
>If I do <A NAME=0 HREF=myimage.gif>My pretty picture</A>, it always
>defaults to using XView...
Um, I'm not sure what you mean. I'm guessing you mean that XView is
the wrong viewing program to use and you want to change it; there's a
resource to do so.
I've actually thought for a while that there really should be a lot
more similarity between <IMG> and <A> references to images; it would
be nice to see something vaguely like:
<A HREF="/some/dorky/image.gif" TYPE=inline>see picture</A>
so that browsers like Xmosaic with the sophistication for inlined
images can display it inline, while browers that just ignore the
inline request or that aren't capable of displaying it inline can
still try to do something reasonable like pop it up in a separate
window. This also could be used for more general inline "inclusion"
of other stuff, like plain text or HTML or maybe a small DVI file
containing an equation or whatever.
For that matter, a slight variation of that; maybe something like:
<A HREF="abstract.txt" TYPE=inline-request>(abstract)</A>
to indicate that the anchor text should be presented, but that the
fetched document should be included inline and replace the anchor text
when fetched if the browser knows how. I was thinking of this as a
method for organizing the TR index; initially just the titles of
articles are displayed, with the user expanding the outline by
clicking and fetching abstracts only where she wishes to.
The only disadvantage of this compared to <IMG> that I can think of is
that there's no good way to make an image an anchor with this scheme.
However, it allows for things like substitute text to be displayed
when an image isn't viewable by that browser.
- Marc
--
Marc VanHeyningen mvan...@cs.indiana.edu MIME & RIPEM accepted
Immediate access, limited costs, high-tech medicine.
For health care, choose only two of the above.
Tim Berners-Lee
<mvan...@cs.indiana.edu> writes:
> I've actually thought for a while that there really should be a lot
> more similarity between <IMG> and <A> references to images; it would
> be nice to see something vaguely like:
>
> <A HREF="/some/dorky/image.gif" TYPE=inline>see picture</A>
>
> so that browsers like Xmosaic with the sophistication for inlined
> images can display it inline, while browers that just ignore the
> inline request or that aren't capable of displaying it inline can
> still try to do something reasonable like pop it up in a separate
> window. This also could be used for more general inline "inclusion"
> of other stuff, like plain text or HTML or maybe a small DVI file
> containing an equation or whatever.
This has only been proposed for about a year or so, and in the specs for
a few months. The form is in fact
<A HREF="/some/dorky/image.gif" REL="EMBED">see picture</A>
I proposed this for basically the reasons you say. XMosaic implemented
<IMG> instead. The difference is that
1. IMG is ignored by implementations which con't do it, whereas
A REL=EMBED causes a link to be generated.
2. IMG can appear within anchors., as you point out.
Therefore, IMG is appropriate for icons but not for figures, which should
use A.
It is all a question of the semantics of link relationships.
These can be used for many things! I think it is a pity
that SRC rather than HREF was used as the IMG attribute name.
Perhaps we should make both acceptable in the short term and
put HREF in the spec.
> Marc VanHeyningen mvan...@cs.indiana.edu MIME & RIPEM accepted
Tim Berners-Lee