Before diving into the specifics of the WML specification, let's look at some ofthe general issues and processes of creating WAP content:
A New Model
If you are accustomed to designing pages for the Web, you will need to adjust (and reduce) your thinking for handheld devices. Due to the limitations inscreen size, processing power, and connection speed, normal information-rich
web pages are not feasible. In fact, it is useful to abandon the notion of"documents" (information that is displayed and read) and think in terms of"applications" (based on choices and user interaction). WAP applications are
typically made up of screenfuls of minimal text and lists of options. Information and interaction design is king as there is virtually no graphic design to be done.
Another difference is that unlike the Web, where it is desirable to entice avisitor to linger at your site as long as possible, a successful WAP application can be measured by how quickly the user can find information or make atransaction and get out.
Mobile devices use special browsing software, sometimes referred to as"microbrowsers" due to their size and capacity, to request and displayinformation from a network. As on the Web, not all WAP browsers are created equal. Older devices with outdated browsers are still in circulation, and what works on one device may not work on another at all.
Add to that the fact that the WML specification allows for a range ofinterpretations of elements and functions, so even browsers that are 100%WML-compliant may have significant differences in their implementation of the standard.
Most WAP-enabled devices use the recently renamed Openwave MobileBrowser (formerly called UP.Browser) developed by Openwave (at one timecalled Unwired Planet, thus "UP").
Not surprisingly, Microsoft has thrown its hat into the wireless ring with itsbrowser, Microsoft Mobile Explorer for cell phones. MME is a dual-modebrowser, supporting both WML and HTML content. The list of devices that useMME is growing.
There are hundreds of mobile devices on the market. Unfortunately, there is no standard hardware configuration, so it is difficult to anticipate just how yourapplication will look and work when it reaches the end user. The following are some device variables WAP developers contend with:
Screen size varies from one device to another. To give you a ballpark idea,many phone display areas are 95 to 120 pixels wide and 50 to 65 pixels high. Newer phones and PDAs may have larger screens (approximately 300 100pixels).
Screen resolution is difficult to pin down. To make matters more interesting, the Nokia 7110 phone has pixels that are taller than they are wide (by a ratio of 1.25:1), which can stretch out graphical images.
Because WAP content is primarily text-based, it may be more meaningful to measure screen space in terms of number of characters displayed. In general, mobile browsers can display only 3 to 6 lines of text at a time with 12 to 20 characters per line.
Text may be displayed as either monospace, where all characters are the same width, or proportional, where characters are varying widths. This can make it difficult to anticipate how many characters will fall on a line.
The vast majority of mobile devices (particularly in the United States, which lags two years behind the rest of the world in mobile technology) have 1-bit black and white LCD displays. As processor power improves, expect to see grayscale and 8- bit color displays become available in the next few years, as they already are in Japan.
Handheld devices typically feature softkeys, buttons that can be programmed for application-specific functionality. How many keys are available, where they are placed, and how they get assigned to actions in the code varies from device to device. Some softkeys are just rendered graphically in the display area. This makes it difficult to anticipate how users will access and navigate through an application.
Each .wml document (called a "deck") within a WAP application has a maximum permitted size of 1400 bytes, although most web developers aim to keep the file size below 500 bytes to improve performance. This size limit refers to compiled decks. Your working documents may be a bit larger, so keep an eye on the compiled size of your file as indicated in the emulator or other development tool.
If your deck is larger than 1400 bytes, you must split it logically into separate files.
WAP application developers generally use WAP emulators to test theirdocuments. An emulator (or "simulator") is a program that runs on yourcomputer that shows you how your document will appear and function on awireless device. It alleviates the need to buy a half-dozen cell phones to test your designs.
One of the nifty things about emulators is that they look just like the real thing(see Figure) -- you can even use the buttons to navigate the way you would on a real phone. Unfortunately, emulators do not always behave exactly like thereal thing. Expect some discrepancies in text layout and even basicfunctionality, so be sure to test on real devices before going live to avoidsurprises.
Figure: The Openwave Simulator WAP emulator program
The following are some popular WML emulators and their respective sites for downloading. The Openwave Simulator is the most popular due to thewidespread use of the Openwave Mobile Browser and its predecessor, theUP.Browser. All of these programs are Windows-only, so Mac and Unix users are out of luck.
The Opera browser Version 5 features experimental support for WAP and WML. While it is not a substitute for a full emulator, it may be useful for testing your WML code or just viewing other WAP applications.
As alternative to a full emulation program, you can view WML pages using one of the web-based emulators at Wapemulator.com or Gelon.net. Theseemulators are limited in their functionality and accuracy, but they give you a good general idea and allow you to view WAP applications from the comfort of your desktop computer.
Web Designing Related Interview Questions
|HTML Interview Questions||HTML 5 Interview Questions|
|Flash Interview Questions||Graphic Design Interview Questions|
|Illustrator Interview Questions||Dreamweaver Interview Questions|
|UI Developer Interview Questions||Dreamweaver CS3 Interview Questions|
|CSS Advanced Interview Questions||Web Developer Guide Interview Questions|
|Log Shipping Interview Questions||Spring Boot Interview Questions|
|UI Designer Interview Questions||Bootstrap 4 Interview Questions|
Web Designing Related Practice Tests
|HTML Practice Tests||HTML 5 Practice Tests|
|Flash Practice Tests||Graphic Design Practice Tests|
|Illustrator Practice Tests||Dreamweaver Practice Tests|
|UI Developer Practice Tests||Dreamweaver CS3 Practice Tests|
|Web Developer Guide Practice Tests||Advanced jQuery Practice Tests|
Web Designing Tutorial
Designing For A Variety Of Browsers
Designing For A Variety Of Displays
Web Design Principles For Print Designers
A Beginners Guide To The Server
Printing From The Web
Structural Html Tags
Adding Images And Other Page Elements
Specifying Color In Html
Cascading Style Sheets
Server Side Includes
Designing Graphics With The Web Palette
Audio On The Web
Video On The Web
Flash And Shockwave
Introduction To Smil
Introduction To Dhtml
Introduction To Xml
Wap And Wml
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.