tags because it will degrade well, and yet allow you to specify CSS class and id.
WALL does not have tags for tables, though it can use tables to generate menus.
Here's a list of WALL tags you can use:
a, alternate_img, b, block, body, br, caller, cell, cool_menu, cool_menu_css,
document, font, form, h1, h2, h3, h4, h5, h6, head, hr, i, img, input, load_capabilities,
marquee, menu, menu_css, option, select, title, wurfl_device_id, xmlpidtd.
Complete listings of the attributes available with each tag, and their meanings are
available from: http://wurfl.sourceforge.net/java/refguide.php.
Adapting to User Devices
[ 80 ]
Will This Work Well for WML?
WALL can generate WML. WML itself has limited capabilities so you will be
restricted in the markup that you can use. You have to enclose content in
block> tags and test rigorously to ensure full WML support. WML handles user
input in a different way and we can't use radio buttons or checkboxes in forms. A
workaround is to change radio buttons to a menu and pass values using the GET
method.
Pages:
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119