|
« previous |
next » |
While these screen shots represent a colour Palm computer, most Palm's are monochrome. Any design should take this into account.
Most obviously, there isn't a lot of fonts to play with on a palm. As a result of this, heading one and two are identical in size. As are three - six, which are the same size as body text, but bold. This suggests that there are six fonts in total on a Palm:
Notice that the hr tag has been reduced to a single pixel line. Makes sense. It seems the only way to achieve large normal text is to use a big tag.
All font tags with a size parameter are ignored. Obviously the font face parameter is also ignored.
Unsurprisingly, bold displays identical to strong, and italic displays identically to emphasis. Link colours are slightly more attractive than the default on PC based browsers, being #309, rather than that scalding blue.
There is no additional monospaced font to use for the code tag, and text cannot be placed above or below the baseline using the sup or sub tags. Likewise, you can't put a line through the text using the strike tag. However, the highly confusing u tag can be used to underline text which isn't a link.
You can't abuse the blockquote tag to give some indentation. Also, unsurprisingly, passing a noshade parameter to a horizontal rule makes not the slightest bit of difference
Where tables are modest in size and no width is declared, Blazer does it's best to render them. This one has the borders turned on, but presumably these would be invisible, if no border was declared.
I've accidentally cropped it off, but the caption tag rendered perfectly, in small, centred text.
Nested lists are not indented further, but simply placed one under the other. This is rather confusing, and suggests we should avoid them if building for Blazer.
The screen is made artificially large for this demonstration.
However, ordered lists work fine.
Forms are weird. The dotted lines indicate the user can input stuff. The password box ("-Assigned-") would probably work if I hadn't pre filled it.
The first two lines ("Duh nur nur nur") are suppose to be checkboxes, but they've failed to render.
The radio buttons work fine, though.
Finally, the button ("can't touch this") looks like an input field, because I made a mistake in my code. If it is set to submit, it looks and acts a lot more like a normal button.
Select boxes display like this, when clicked.
The textarea and input tags both look the same, and when the user clicks on them, they get this dialogue box.
Marquee isn't supported. No chance for scrolling text, then.
However, pre works perfectly, but might cause horizontal scrolling problems.
This shows how some of the more commonly used tricks in linear navigation render on the Palm. It's unfortunate that circular bullets are square, but the German quotes (« and ») look great.
|
« previous |
next » |