Clarence Verge wrote:

> Hello David;
> I'm guessing you are a Mac or Linux user originally ?

Good guess...though I do quite a bit of work in DOS & Winblows...

> As unlikely as it might be for a lowly DOS user for 20+ years to have a
> useful suggestion for a Linux user, (Mac's another story) may I suggest
> you use sensible 8.3 filenames for things you zip. There was one there
> I couldn't even ERASE !!.

Sorry about that...the zip files (and bmps inside) have been renamed for smoother
digestion. :) I'll keep that in mind in the future.

> Luckily I have an unzipper that allows me to produce an output file of
> any name. Since there are only two users of this unzipper on the planet,
> you may get some unkind comments from those not so lucky. ;-)
>
> Second point, yes zipped .pngs are redundant. I meant zipped BITMAPS
> which would then reproduce EXACTLY and not dependant on any png2bmp.
> If I may make another suggestion, smaller screens make smaller files.
>
> Enough bitching.<g>

I will make sure to do smaller screenshots in the future...

> I have seen all your screenshots and I understand your complaint about
> weird colors, but those weird colors are partly your own choice.
> They are also partly due to the stupidity of the person(s) that
> generated the page. See, they probably assumed you would be viewing them
> with IE or NS and that you wouldn't have been smart enough to change the
> default text or background colors cuz they certainly weren't smart enuff.
>
> The default colors for those in Arachne may be quite different depending
> on which color format you selected and/or what changes you made.
> Also, there is this thing called CSS (Crappy Style Shit) that makes
> CSS links a truly shitty color usually, unless you turn it off and make
> your own link color choice override.
>
> Regardless, you will always have a problem someplace. Set your links
> to blue and you will find a site that imposes a blue backgrond on you.

Here's where I'll have to disagree. The person(s) who coded the mozilla.org page
used a CSS for the page's style. For example, the bright yellow (the bgcolor of
the main content areas, such as the content starting "Developer Day...") came from
Arachne incorrectly interpreting the following:

.contentcell {
    background-color: #FFF;

The reasoning behind this format, as seen in the .css file itself, is as follows:

/* use colors of the form #rgb instead of #rrggbb  since this discourages
 * web-unsafe colors. Web-safe colors are of the form #rgb where
 * values of r, g and b are one of {0,3,6,9,C,F}.
 */

What is the default style used by Arachne, if it doesn't support CSS styles (or
linked CSS)? In my prefs, I have the default HTML colors as:
Text: black
Bg: grey
Link: blue
I'm not sure how it would be my or mozilla.org's fault... (didn't check CNN's CSS)

> The fantastic quantities of XMS.
> This is an indication that something on one of the sites you visited
> made Arachne crash softly. Just a bump.  Usually the problem is too
> many objects. Really, just stupid page design again.
>
> But still, Arachne should not do what it does. She may have run out
> of XMS memory and then switched xSwap to HD and started counting funny.
> The bad part here is she probably will not switch back unless you run
> setup again and re-select XMS. She will be very slow with xSwap on HD.

Haven't had this problem, I don't think (switching xSwap to HD)...I run Arachne
from a 12MB RAMdisk & have cache pointed to tmp (which is on the RAMdrive) & she
always seems fairly blazing (for a DOS app ;)

david

--

"None is so rich as to throw away a friend."

    -- Turkish proverb

Reply via email to