> This isn't about making the jag fiat compatible. It's about
making roads
> jag and fiat compatible. If you want to use a jag, you
shouldn't be
> slowed down, but you shouldn't stop me from using the road
cause I have a
> fiat.
Look. There's a straight way of making the road compatible with
both, the fiat, and the jag. There should be seperate ways for
the two. The fiats should take one route, and the jags should
take the other. The destination will be the same.
Slashdot.org has an option where you can set the display to
text-only mode. Now this is just what all Web sites should do,
without compromising. Something like this -
if(browser == jag) { loadJagVersion(); } else {}
The jag (jag.version >= 4) should be able to read this, and load
a version for itself. The 'text' in both versions should be the
same (using ASP/CGI/JavaScript/CSS, the jag can read from the
fiat version of the text and render it in it's own fancy ways
(with images! animation! java! wow!!!)).
W3C should produce a standard code template, that helps
developers have the version4 jags load a different site (same
'text'). This code template should be implemented by all
developers. After all, it's not double work, because the 'text'
comes from the same source. Whether it's dynamically picked up,
or not, depends on the developer's way of implementing.
It's the 'text' that really makes the Web pages their worth. The
rest is just extra stuff. So if people don't want it, it
shouldn't be _forced_ on them. Linux users know this best.
As of now, the destination being the same, and both starting off
together, the so called 'dukkar' fiat still reaches the
destination first. The 2MB New Hacker's Dictionary loads faster
in Lynx than in IE/Netscape.
--
Manish Jethani
http://mjworld.hypermart.net/
To subscribe / unsubscribe goto the site www.ilug-bom.org ., click on the mailing list
button and fill the appropriate information
and submit. For any other queries contact the ML maintener
