Desktop (DECK)
Due to network bandwidth and certain WAP server DECK transfers, the smaller the decker, the better, preferably not more than 1.2k. If your needs are complicated, it is best to be divided into several decks to complete.
The complete WML document structure is as follows:
"http://www.wapforum.org/dtd/wml_1.1.xml";>
.
Head information ...
.
.
Template definition ...
.
.
Contents ...
.
.
Other CARD (no available) ...
.
XML Description [TOP]
The beginning of the decker must indicate the following XML type declaration:
"http://www.wapforum.org/dtd/wml_1.1.xml";>
The first line indicates that the XML version, the tight document type (DOCTYPE) declares indicates the referenced language standard definition (the content of WML_1.1.xml can be viewed in the DTD description in the appendix of this tutorial).
The position and order of these two sentences cannot be changed, and there is no holiday in the middle.
grammar:
The
tag contains information about the DECK. The tag can contain aDomain: Specify the domain, the default value is the current domain.
PATH: Specify the path, the default value is "/", that is, the root directory.
syntax:
http-equiv = "string" | Name = "string" Forua = "true | false" Content = "string" Scheme = "String" /> Similar to HTML , provides META information of this deck. Including three situations Name = "name" UP.LINK Server ignores META data http-equiv = "name" UP.LINK Server converts META data to HTTP response head (same html) user-agent = "agent" UP.LINK Server directly to mobile device The Content property is also a must, and its content is determined according to attribute. The scheme attribute is currently not supported. Forua is optional attribute, the tag is deleted by the intermediate agent before the WML file is transmitted to the client (because the protocol of the transmission may change), the default value is false. Currently supported META data: Specifies the storage time period in the phone memory cache, the default for 30 days (unless the memory is exhausted), during which The phone is called directly from the cache for the visited DECK. If the information is sensitive to time, you can specify the survival period in the cache with the max-agn, the minimum unit is second, if specified as 0, then each time you need to call the DECK. and Demonstration bookmarks Features. When the user makes a bookmark, the mobile browser first records the CARD with a tag, this tag default is the title attribute in the Onenterbackward = "String" Ontimer = "String" /> OneNterForward: The link that is transferred when the user enters Card through OnenterbackWard: When the user returns a link to the CARD via OnTimer: Example (other commands involved in other chapters): ... ... You can also see events (Event). A DECK can contain multiple CARDs, each CARD may not only display, note the relationship between DECK, CARD, and screen displays. A CARD is included with grammar: ID = "string" Title = "String" NewContext = "True | FALSE" Ordered = "True | FALSE" Oneterforward = "String" Onenterbackward = "String" ONTIMER = "string" XML: Lang = "String"> Each CARD element can have a label (ID) and title. Of course, this is not necessary. ID: The name of the Card is unique in the DECK, which can be used as a URL has been jumped. Title: Card's title, user Bookmark, a name, a CARD. This attribute will appear in some user terminals. NewContext: User terminal (mobile phone, emulator, etc.) is not to clear the previously reserved information such as variables, stack history, terminal status, etc. The default is false. ORDERED: Indicates that the content in this Card is displayed in a fixed order or is displayed in the user's selection. The default is TRE. This is different from HTML, and the content in the CARD page can be displayed in a certain order. The default is to display in linear order, that is, according to the order of the code, but to note that the following three labels must be written in the following order Onevent> OnenterbackWard: When the user returns a link to the CARD via OnTimer: Different browser indicators [TOP]> Nokia 7110> Ericsson R320> Ericsson R380> UP.BROWSER> CARD maximum number of bytes> 1397 bytes> 3000 bytes> 3800 bytes> 1492 bytes> Image Maximum Bytes> 1397 bytes> 3000 bytes?> 3800 bytes?> 1492 bytes?> Display line number> 4 (including headline)> 5> 7> Different from the terminal> S3568i: 6> Display column numbers> 19> 14> do not know> Differences depending on the terminal> Display width (pixel)> 95> 101> 304> Different terms> Display height (pixel)> 45> 52> 98> Different from the terminal> Pixel ratio> 1: 1.25> Do not know> 1: 1.23> Different terms> Font> None> Small, Bold, Emphasis, Strong> Small, Big, Bold, Italic, Emphasis, Strong> Small, Big, Bold> Text location> No, forced home, home, home, right> home left, hit, hit, paragraph indenge> I don't know> Image location> Forced left> I don't know> I don't know> I don't know> Table Support> Do not support> How 5X5> I don't know> I don't know> Touch screen> No> None>> None> Icon button> No> None>> I don't know> Dialing in WML page> "Extraction Number" Features> Support by WTAI> Support> 3.1 above browser support from WTAI> Enter> In-line input> Set location input> Set location input> do not know> Input format> Only case you write> I don't know> I don't know> I don't know> Graphical link> No>> Have> I don't know> Link format> In the line> In Set Position> In Set Position> I don't know> Download order> Text, then graphics, start selective timing> text, start selecting timing, then is the picture (the result is that the Card has not been downloaded, it is over time)> I don't know >> HTTP Redirect>
