Basicly, the idea is that the definition of how many pixels to use
per size is changeable:
For example, if "Font Size 3" is 90x90 pixels (i'm just trowing numbers
here for the example. Ignore the obvious mistakes) when you're on
800x600, then when you switch to 640x480, "Font Size 3" is re-defined
to use the font file that has fonts at the size of 70x70 pixels.
At the same time, Font Size 4 is now using the 90x90 one.
By changing the entire font-size set definition for each resolution
mode, you can make the sites to still appear fully readable under
each resolution, and quite similiar.
Try this one: Go to a site on 800x600. Drop down on the fly to
640x480. You'll see how the site suddenly looks "bigger". Thats
the problem - IIRC, the original idea of HTML was that sites will look
the same on whatever system and browser you're using. Now, obviously
things have changed for the worse since then, but the ability to
adapt sites to current resolution is one of the items.
Now, concider this: Michael wants to port Arachne to handheld devices.
A good idea, obviously. But - have you ever tried to use Arachne on
the resolution of 320x200? Try it.
That should let you feel like Guliver in the Land of Giants. :)
Fonts are HUGE, pics are also. Arachne will have to learn how to
get fonts that will be better fitting for its current res, and
maybe even (in extreme cases) resize images to fit when your res
let you only see 15% of the web page in its normal, untouched form.. :)
"L.D. Best" wrote:
> Admittedly, I'm not set up like some of the guys to actually change the
> base resolution "on the fly" to check things out. But since the font
> style and size are set by the page code itself [unless you're lazy like
> me and allow users' defaults to determin base size], I don't know how
> Arachne would make any font smaller at lower resolutions.
>
> Hey!! Someone explain all this, please?
