Kevin Jackson tapped away at the keyboard with:

...

What's the URL?

I daren't post it yet, as we are STILL working hard on it. I'll post it on the list when it is tried and tested on all browsers I have at my disposal.

Loads of tedious work there. Set yourself guidelines for what you consider to be acceptable before you start. Do remember to use Bobby or other similar accessability-checking tool. Bobby also reports browser-specific gotchas so it's a pretty useful tool all round. It's free at http://www.cast.org/bobby/ and runs under Java. Runs quite fast - processed over 300 of my pages in under an hour on a 166MHz PII with Java 2 runtime on SuSE. It's a processor hog; but that goes without saying I guess.

And I was wrong to suggest an upgrade. Point taken. :)

Fair enough. We all make mistakes.

Which, brings me to the point of WAP phone surfing... What qualities of web site design should I include to cater for Mobile surfing?

No frames. No image maps. Small pages (both data and presentation). Primarily text-based as most devices aren't expected to be graphical; and if so, they're more likely to be b/w or grayscale. Don't rely on a mouse or similar random pointing device being present, or a keyboard. (Anybody who's ever typed a long SMS message on a phone keypad will appreciate the difficulty one would encounter with filling in forms.) See the dicussions at w3.org. There's a mailing list pertaining to WAP, as well as a dedicated section on their web site at http://www.w3.org/Mobile/ w3.org is first port of call for all WWW queries in my book. There's an HTML4 guidelines page http://www.w3.org/TR/NOTE-html40-mobile/ but most points apply to other limited-capability browsers as well. I know it's a lot of reading, I've only just skimmed the surface of some of the links and I'm still befuddled. My phone doesn't do WAP, so I can't try my pages. Maybe if I shrink my xterm to 4x24 and run lynx. :-) Maybe not; the "decorations" consume too much real-estate. Suggestions for a WAP simulator are invited. It should probably only "listen" to cursor keys and numbers (*# as well); doing the alphabet in mobile-phone fashion. I haven't even seen the real thing in operation so I'm not entirely sure of how little to expect. -- Bernd Felsche - Innovative Reckoning Perth, Western Australia -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/