One of the most striking new features of Pocket PC is to specifically designed Internet Explorer web browsers (hereinafter referred to as Pocket Internet Explorer). Pocket Internet Explorer not only enables owners of the Pocket PC to browse the web content in a online manner, but also allows you to keep synchronization with the web page to achieve offline browsing. In all handheld devices, Pocket Internet Explorer is the first product that supports this feature. Microsoft Jim Floyd and Joseph Kirk Ollis
The information contained in this document only represents the viewpoints and problems of the information release on the date of information on Microsoft Corporation (Microsoft). Since Microsoft must respond to the sun-changing market conditions, the information should not be understood as some kind of commitment made by Microsoft, and Microsoft does not make anything. Guarantee. This document is for reference only. Microsoft does not make any public or concealed forms in this document. Backoffice logo, Microsoft, Windows and Windows NT are registered trademarks or trademarks of Microsoft companies in the United States and other countries. Other products or company names mentioned herein are also trademarks of their respective owners. Microsoft Corporation, One Microsoft Way, Redmond, Wa 98052-6399, Usa Pocket Internet Explorer introduced into the world of Pocket Internet Explorer! With the formal release of Pocket PC, Microsoft's Pocket Internet Explorer also provides the most rich web experience for all similar pocket devices. The Pocket PC can display complex content. Pocket PC has a minimum of 4,096, up to 65,535 colors depending on the type, and a minimum of 4 grades, up to 16 grades. Pocket Internet Explorer has put key Internet technology standards into implementation: HTML 3.2, Secure Sockets Layer (Encryption Socket Socrat Layer, SSL) 2.0 and 3.0 for secure transaction, Microsoft JScript for web page behavior, visitors Tracking information and easier to return users and formatting frames that require user authentication sites. Pocket Internet Explorer can even provide support for ActiveX controls that have existing on the Pocket PC. Pocket Internet Explorer supports XML (Extended Markup Language) This critical technique, allowing people to deploy commercial Internet applications to the Pocket PC in a more easily manner. Pocket Internet Explorer, which is developed for Pocket PC, provides several ways to introduce web content into small screen innovations, including: "Continue Match" This adaptive adjustment function can dynamically display the Web site to the Pocket PC in the maximum visual manner. Unique compact and narrow screens. Automatic status detection feature automatically judges if the device is in an Internet connection status; if the device is not connected to the Internet, transfer the browser to the previously stored web page in a seamless manner. Pocket Internet Explorer has an unique design and implements an optimal combination of Internet Explorer 3.02 (HTML Engine), Internet Explorer 4.0 (scripting engine), and Internet Explorer 5.0 (XML engine). In view of this, we have written this white paper to help web site designers optimize their site for Pocket Internet Explorer. Detecting the Pocket Internet Explorer on the server Before starting to design the web page for the Pocket Internet Explorer, we must take into account a crucial problem.
How does the web server determine if the Pocket PC is connected to the site? If you are using Microsoft Internet Information Services 4.0 and its subsequent versions, you will find a file named Browscap.ini in the / WinNT / System32 / InetSrv directory. This file contains the description information about all known browsers, which is generated when you install the latest service packages. The following is the Pocket Internet Explorer description information you must add to the browscap.ini file: Pocket PC (Aka Rapier) [Mozilla / 2.0 (Compatible; Msie 3.02; Windows CE; 240x320)] Browser = Pocket IE Version = 4.0 Majorver = # 4 minorver = # 0 platform = Windows CE width = 240 height = 320 cookies = TRUE frames = TRUE backgroundsounds = TRUE javaapplets = FALSE javascript = TRUE vbscript = FALSE tables = TRUE activexcontrols = TRUE
Pocket Internet Explorer is actually a mix of Internet Explorer 3.02 (HTML), Internet Explorer 4.0 (Scripting), and Internet Explorer 5.0 (XML). And this is why the product is identified as Microsoft Internet Explorer 3.02, although it uses 4.0 version number in internal properties. When Pocket Internet Explorer issues a request to the HTTP server, the following specific information is included in the corresponding HTTP request title: ua-pixels: {IE 240x320} UA-color: {MONO2 | MONO4 | Color8 | Color16 | Color24 | Color32} UA-OS: {Windows CE (PCKET PC) - Version 3.0} UA-CPU = {IE MIPS R4111} ensures that the system quickly generates a moment of Pocket Internet Explorer into the site by using the following server-side script Special Optimization Page: 'Check For Windows CE (PCKET PC, Palm-Size PC, Handheld PC, Handheld PC Pro) IF (Request.ServerVariables), "Windows CE"), "Windows CE")) THEN {Add Windows CE Specific code} else {add code for other platforms} end if 'Check for Pocket PC if (InStr (Request.ServerVariables ( "HTTP_UA_OS"), "POCKET PC")) then {add Pocket PC specific code} else {add code for other Platforms} END IF can determine if Pocket Internet Explorer is using the client script (jscript): var strnav = navigator.USERAGENT; // Check for Windows CE (Pocket PC, Palm-Size PC, Handheld PC, Handheld PC Pro) var iSce = strnav.indexof ("Windows CE"); if (iSCE> -1) {// add windows ce specific code} else {// add code for other platforms} // Check for Pocket PC var isppc = strnav.indexof ("240x320"); if (iSppc> -1) {// add pocket pc specific code} else {// add code for other platforms} [b] can be supported HTML tag
In addition to individual exceptions, Pocket Internet Explorer is basically compatible with HTML 3.2. So, all HTML tags defined by this standard can be displayed in Pocket Internet Explorer. Some of the following Ratiographic conditions and technical issues must be considered: DHTML is not supported by the support framework, which always has borders and has been adjusted. CSS is not supported here, providing some HTML tags for Pocket Internet Explorer. General Principles: • Related issues of Target properties in General Markup Problems Pocket Internet Explorer cannot be derived from multiple forms. So if you use "Target = _new" in the tag, Pocket Internet Explorer will not open the second form, and this is that you can do it when you use a desktop computer. You can use the Target property to point to a named frame. The marker also supports this property. Use any other specific target ("Target = _new" or "Target = foo") will cause the Pocket Internet Explorer to produce the same behavior as in the case where the target is not specified. Pocket Internet Explorer not only does not support the _top and _parent attribute, but also does not support _Self and _blank properties. And if the target is something other than the current named frame or supported by support, it will be completely neglected with the target attribute. In this case, the browser will navigate to the frame or form pointed to by the chandis link. The browser also supports the target attribute on the Area, Base, and Form tags. · Fonts Pocket PC provides the following four fonts: Tahoma (default font for a wide font) BookDings Frutiger Linotype Courier (default font for a wide font) Other all fonts can be converted according to the principle of similarity according to the principle of similarity For the above four fonts. The practice of using tags for any set of widths can be achieved to ensure that the Pocket Internet Explorer is determined to determine the goal of wide font. The frame frame often occupies a large number of screen space, and this consumption is just to calibrate the edge of the object, so we generally do not advocate using it in the design work for Pocket Internet Explorer. And if you really have to use the frame, please control the quantity of the quantity within two scope of each screen. • Matching marks perform pages design in the correct match of HTML tag. For example: wrong way:? Error way:? Incorrect matching will result in unpredictable consequences of Pocket Internet Explorer. · BGSound Property Pocket Internet Explorer supports background sound, which provides a very "cool" special effect for the web page. Of course, Pocket Internet Explorer only supports WAV files, and such files often take up a lot of storage space. To this end, please use the sound effect moderately, and the negative impact control is within the minimum range. In addition, since Pocket Internet Explorer does not support Loop properties, you will not be able to create or use persistent background sound.
• Form field and button • Text field and text area Pocket Internet Explorer can display text fields and text area limits by the width of the Pocket PC screen. Users sometimes need to scroll horizontally in order to see text fields, but text fields always guarantee that they are completely displayed within the screen range. If you have to use text fields and want to get a simple and bright good effect, then from design Iraqi should be processed in accordance with the principles that do not exceed the PCKET PC screen. Please note that the long field and other regions are placed in the starting section of the row. • Button button is a rectangular graphic object that triggers execution of certain activities after clicking, and we usually name the button with the above-described activity related description. In most cases, the button is usually named "Submit" or "Cancel". Buttons generally follow the text process and scroll with the page. In the ideal case, the button should be designed and placed in a consistent manner, which is equally applicable to specific pages and sprockets. The number of buttons that the screen space can accommodate is limited, so, please carefully take care of the buttons placed on the screen, avoid abuse. Unless the Avantgo synchronization is used in the case of use, the button will not submit any form offline. Some events can be captured by custom event handles, and buttons are used to perform trigger operations for these events. Custom event handles are usually operated offline. As mentioned above with respect to the text field section, the display range of the button and the text area must not exceed the screen width of the Pocket PC. · The form is greatly improved by the table display data through the form. Use the width property to set the size of the table in the window. Setting the pixel value in the width property is the best way to control the size of the table. In addition, Pocket Internet Explorer supports nested forms. If the width property is omitted, the table will be drawn according to the following rules: If the "Fit to Screen" option is selected, the table will be automatically adjusted according to the screen width. If the "Fit to Screen" option is not selected, the Pocket Internet Explorer will use the 640x480 virtual screen and draw a table with a width of 640 pixels. This shows that the width value should be omitted unless there is special requirements for the width of the form or the cell. The tag supports the Align property, and this property is not supported. · Graphics and image graphics and images can enhance the page to the user's appeal, but during the application, we should meet less and fine principles, and use it when you can provide value to users. If you want to display an image greater than the workspace, Pocket Internet Explorer will follow the following rules: If the "Fit to Screen" option is turned off, Pocket Internet Explorer will display images according to the settings in the tag, which is "Height" and "width" attribute values. Or image original size (if "Height" and "Width" properties are set) displayed. If the "Fit to Screen" option is turned on: When the image is smaller than the screen width, the image is displayed according to the setting in the tag. When the image width is greater than the screen width, the image will be adjusted according to the screen size, but the adjusted image size will not be less than the original 1/2 of the size. Zooming Operations typically reducing image quality, so avoiding image width greater than the minimum width of the browsing area. · Image details Avoid using large complex images to be a wise practice because the zoom operation is likely to slightly go to the key information in the image. If you do not need to use an image in a convenient way, it is best to give up the image. If a complex image must be used, it is also possible to cut it to achieve the expected results. · Image Color Pocket Internet Explorer can display color images on color monitors. On grayscale or monochrome display device, Pocket Internet Explorer converts color images to black and white images.
The original color design of the image will directly affect the effect of Pocket Internet Explorer displaying the image on a grayscale or monochrome device. Those images with high contrast and boundary are optimally processed. · Design Image For mobile devices, the easiest and most representative image is used to create a small bitmap image with its own style, while paying attention to the screen space. Complex elements tend to make people feel messy, and therefore, you should use a concise and bright lines and shape design images. The best results are derived from simple rather than confusion. • Alternative text tag users may choose not to load images, so alternative characters that have been placed at the location of the image is very important. Remember, what you have to do is explaining the functions represented by the image, not the image. · Image Map Pocket Internet Explorer does not support image map. Please control the image size as minimize as much as possible. In addition, the image on the web page should imply the correct functionality to the user. · GIF animation Pocket Internet Explorer does not support GIF animation. Only the first frame of GIF animations can be displayed to the user, and the remaining frames that make up the animation will still be saved on the device and occupy valuable storage space. General principles, tips and techniques The following is some general principles for designing Pocket Internet Explorer. Remember: The screen size of the Pocket PC is limited to the smaller screen size when designing the application. Although the vertical and horizontal scroll bar can be used, the information should be adjusted to a page as much as possible. The Pocket Internet Explorer Theoretical resolution is 240x320, but the actual available space cannot achieve this range All Pocket PC screen resolution is 240x320. However, the Pocket PC user interface defines the area where two browsers cannot be used. The menu bar at the bottom of the screen is located on the top of the screen. The two columns occupy 26 pixels in the vertical resolution. Therefore, if you want to design a page of only one screen for the Pocket PC, the page size must not exceed 240x268. Once the height of the page exceeds 268 pixels, the vertical scroll bar will automatically appear and reduce the screen width to 229 pixels. In addition, the user can provide a vertical space of another 23 pixels by closing the address bar. However, since the page itself cannot determine the status of the address bar, the address bar is not calculated. At this time, if the horizontal scroll bar is used, the horizontal scroll bar will also appear because the Pocket Internet Explorer requires 11 pixels to display the vertical scroll bar that appears. If a page without a horizontal scroll bar is designed in some way, the vertical space of the additional 11 pixels will be obtained. The following figure shows the pixel range of each component in the Pocket Internet Explorer screen: Pocket Internet Explorer screen size Offline Browse: Pocket Internet Explorer's Important Important Upon Mobile Favorites, unless the user sets the link depth to greater than 1 Otherwise, hyperlink will not be available in offline. Therefore, remote hyperlinks should be used as little as possible, and only those most important information are provided to users. The page should be designed to work properly in the link disconnection state. The link depth means "downloading the selected page and starting from the selected page" all pages that can be reached by the N layer link. " The page cannot dynamically change the Pocket Internet Explorer does not support DHTML, so all the contents in the page are static. You can implement dynamic updates of certain pages using XML, XSL, JScript, and Document.Write methods. Functional characteristics are not necessarily necessarily that the performance of performance performance should only use those necessary features. Excessive features will cause unnecessary overloads.
Adding spaces through the GIF file Sometimes, you will find that it is difficult to add the required number of spaces to the page. If this problem is encountered, the space can be accurately inserted between the page elements through a transparent image. First, create a transparent GIF file with a size of 1x1 pixels and embed it into the document by tag. Thereafter, the image is expanded to the desired size using the "Width" and "Height" properties. One of the purposes of using the "interval" GIF file is a breaking after mandatory title. For example, suppose you follow a property, you may not want to add exact spaces by title tag or tag. At this time, you can force the cross-row and some transparent pixels are simply inserted by the previously mentioned methods. At the same time, the image size is specified as 240 pixels wide and 1 pixels high. The text in the image contains the font that does not support the Pocket Internet Explorer HTML on the page through the image, which can make the decorative page. To place text in the image, you usually need to use a font designed for your computer screen. Currently, there are several excellent 1 fonts to choose from. Among them, Verdana fonts apply to bitmaps displayed in various resolutions. Therefore, it is ideal for use on mobile devices. But remember that any text placed in a bitmap cannot establish an index on the current search engine (such as Altavista or Yahoo). Using Office 2000 as a web creation tool in four Office applications (Access 2000, Excel 2000, PowerPoint 2000, and Word 2000), only PowerPoint 2000 checks the browser version in front of the display page. When the page is submitted, it will notify the user that this page may not display correctly in the current browser. In most cases, the simple document generated by the above Office program can be displayed correctly, but it will cause problems after some complex features slightly added. In short, it is best not to use Office 2000 to create a page for the For Pocket Internet Explorer. Providing optimal performance for e-commerce Personalization page Personalization will have a huge impact on people using Web. Allow users to increase the interactivity of the site from your web page from your web page. You may have provided similar features on the Web site. For example, add a securities list, a list of urban lists in basic weather information. In addition, since the offline content is stored in the user's desktop system, the cookie function must be supported. To implement personalization in Pocket Internet Explorer to increase interactivity, add a dedicated Pocket Internet Explorer configuration to the provided content. But remember that users generally need two configurations: a useful for Pocket PC; another for desktop computers. Advertising advertising in the web page has become a universal approach. For some companies, sales advertising spaces have become the main source of income of Web sites. However, due to the content on the site may be browsed offline in Pocket Internet Explorer, there is no way to help the Web site owner accurately count the number of advertisements. The advertising bar is often linked to the homepage of the relevant company. Usually, this approach does not help users, because: unless the Pocket PC user is selected in the synchronization process is greater than 1 and allows link to other sites other than the current page where the current page is located, the relevant company's homepage will not Offline browsing. Keep in mind that the important part of the page should be the content valuable to the user, not an ad. The sight of the header Western readers is accustomed to gradually move to the lower right corner of the screen from the upper left corner of the screen. Therefore, you should put the most important information - such as title or company logo - placed on the top left of the screen; place the relevant information and links at the bottom of the page.
Typically, the first few lines of the page contain some information texts about the company or content provider. This area should be utilized in order to communicate with customers and build reliable reputation for the company. In addition, this area can also include small ads. Setting the form width in 240 pixels as mentioned in the HTML marker section, the maximum width of the Pocket Internet Explorer page is 240 pixels. Like or such a form element will not be automatically contracted by the window automatically adjusting the option according to the window according to the window, and the portion other than the screen width will not be displayed. For e-commerce customers, it is very annoyed when entering credit card information or processing shopping carts. Designing an e-commerce form design form When you design a form, you should keep in mind that the screen width is 240 pixels. The input control should be placed on a different line to avoid unnecessary scrolling. Each domain should be limited to the small screen area. If you need to display the product image selected by the customer, the related description text should be placed in the image and the latter. Providing the best performance for information sites In addition to providing the best performance required for e-commerce sites, pay attention to other points in design information: Information site should support offline browsing to avoid using those do not support offline Elements of work, such as form fields, large bitmaps, gif animations or excessive ads. Many new information sites require short feedback to the designated article. The offline user will not be able to use this feature because you need to send back information to the server. However, the Pocket PC supports sends an email message in offline, so you can add a Mailto link in the page. Concentrately focus on substantive content, do not show links that Pocket Internet Explorer users are unlikely to browse, such as video / audio links or slide showing of large images. To create a page with a new information of the article using a new information site between pages with each other, and point to the full content of the article through a link at the bottom of the page as "Click here to read more". This approach is not very effective in the offline implementation of Pocket Internet Explorer. Most users usually do not change the link depth in the Mobile Favorites (Mobile Favorites). In fact, they will remain the default (0). In the past journey, when they try to click on such a link to read the article, it will cause the "page not available" error. In addition, even if the user wants to read the entire article, it is difficult to determine the depth of the link to be set during the actual use. To avoid the above case, you can create a short introductory page and include links to all articles in this page. This approach still requires a user to change the depth of link to "1", but it makes the entire process more clearly. The prompt can be added to this page to inform the user The depth of the link should be set in the synchronization option. Write scripts With the importance of complex web applications, write client scripts become more popular. Pocket Internet Explorer supports client JavaScript 1.1 (ECMA-262). But do not support VBScript. According to conventions, Pocket Internet Explorer supports Internet Explorer 3.02 DOM (Document Object Model). Here are some questions that need to be pointed out when writing scripts in Pocket Internet Explorer: Script Error Default In the case of syntax errors in JScript, missing objects or other JScript errors will be ignored in Pocket Internet Explorer. The corresponding script will terminate without any hints. Add the following registry keys to enable an error message.
[HKEY_CURRENT_USER / SOFTWARE / Microsoft / Internet Explorer / Main] "ShowscripterRors" = DWORD: 00000001 Pocket Internet Explorer JScript insensitive case in Internet Explorer 4.0 and 5.0 JScript is case sensitive. You may want to know why the same script can operate correctly on the Pocket Internet Explorer, but it causes errors on the desktop computer's Internet Explorer, which is probably because the script is not properly case-sensitive when the script is accessing object properties, methods, events, or collections. . Here, the author is strongly recommended to correct case sensitivity when writing JScript, which can ensure extensive compatibility and facilitate debugging. No Window.open Functions Pocket Internet Explorer does not support multi-window. The call to Window.open will end in failure, do not generate any response (if the script error is turned off). Restricted Pocket Internet Explorer supports ActiveX controls and allows scripts to write scripts using the appropriate methods and properties. However, there is some restrictions compared to desktop computers: The control cannot be downloaded and installed on the Internet Explorer support for the desktop computer to download and install the ActiveX control. This approach is not supported by Pocket PC. However, the ActiveX control already existing on the PCKET PC can be referenced within the tag in the page. The ActiveX Control is not affected by the Fit To Screen (depending on the screen automatic adjustment) option Even if the Fit to Screen option has been selected and the ActiveX control itself has been adjusted according to the screen area, the control content size will not be adjusted accordingly. If you want to create an ActiveX control on the Pocket Internet Explorer web page, make sure that the client display area is designed within 240 pixels. There is no Java Virtual Machine (Java virtual machine) on the Java Applet Pocket PC, so Java Applet is not supported. Security Pocket Internet Explorer supports all universal security schemes: SSL 2.0, SSL 3.0, and Server Gate Cryptography (SGC). Pocket Internet Explorer supports 40 secure passwords by default. Supports NTLM certification and clearing method. XML supports one of the latest components of Pocket Internet Explorer is MSXml.dll, which is an Internet Explorer 5.0 component that can be used on the Pocket PC. The component allows Pocket Internet Explorer to display XML in a standard XML syntax color view, which has been widely used in desktop computers. At the same time, it also allows XML data in a more friendly manner using XSL (extended style sheet language). The difference between MSXML in Microsoft Internet Explorer 5 Microsoft XML for Pocket PC is almost identical to the corresponding features in Microsoft Internet Explorer 5. However, on the Pocket PC, some functions are not supported. The back-rear compatibility of IE4 MSXML DOM is not provided MSXML for Microsoft Internet Explorer 5 contains the functions of simulation of XML DOM in Microsoft Internet Explorer 4.
To reduce memory requirements and ROM capacity, the MSXML for Pocket PC does not contain this feature. Data Binding Pocket Internet Explorer and MSXML for Pocket PC do not support data binding. Support for the support of Data Binding requires complex HTML layout. CAUTION CSS Properties Remember, Pocket Internet Explorer does not support CSS. Please take a closer look at the XSL conversion you created and make sure it does not contain CSS elements or properties. It is especially not to use the style attribute in the HTML tag. XML parser interface You can also use Microsoft XML Parser for C or Visual Basic applications. How to use XMLDom in embedded Viusal C to import XMLDOM in the Embedded Visual C application, you can import Pocket PC Emulator (Pocket PC Simulator) MSXmlm.dlls / WCE300 / MS by following statements. Pocket PC / emulation / palm300 / windows / msxmlm.dll> raw_interfaces_only using namespace MSXML; void __stdcall _com_issue_error (HRESULT hr) {// Error handling goes here} "raw_interfaces_only" attribute is important, without it, "msxmlm.tlh" file A large number of errors will be generated. This property only creates a low-level interface description used in the C application. To avoid connector errors, using the "COM_ISSUE_ERROR ()" function is very necessary. Here is a small example of an XML code:
IXMLDOMDocumentPtr iXMLDoc; IXMLDOMElementPtr iXMLElm; IXMLDOMNodeListPtr iXMLChild; IXMLDOMNodePtr iXMLItem; short tEmpty; BSTR bStr; HRESULT hr = iXMLDoc.CreateInstance (__ uuidof (DOMDocument)); if {iXMLDoc-> loadXML (L "Joe" L (FAILED (hr)!) "Smith", & tEmpty); iXMLDoc-> get_documentElement (& iXMLElm); iXMLElm-> get_childNodes (& iXMLChild); iXMLChild-> get_item (1, & iXMLItem); iXMLItem-> get_xml (& bStr); MessageBox (NULL, bStr, TEXT ( " Caption "), MB_OK; How to use XMLDOM in Visual Basic in Visual Basic in the embedded Visual Basic. The following code snippet shows how to resolve XML in Embedded Visual Basic:
Dim xmlDoc Dim currNode Dim xml Set xmlDoc = CreateObject ( "microsoft.xmldom") xml = "Joe" xml = xml & "Smith" xmlDoc.loadXML (xml) Set currNode = xmlDoc.documentElement.childNodes.item (1) MsgBox currNode The .xml message box will appear as follows: Smith uses XMLDom in JavaScript you can even access XMLDom through the client JavaScript 1.1. The following code uses the same is written in JScript: function showPhone () {var root = Contacts.documentElement; var selectedElems = root.selectNodes ( "CONTACT [NAME = 'Bill Williams']"); var billElem = selectedElems.item (0) Var phone = billelem.childNodes.Item (3) .NodeTypedValue; Alert ("Bill Williams Phone Number IS" Phone);} Summary Pocket Internet Explorer is a powerful web browser, which provides today's web browser Almost all functions available. If you spend some time during the page design process, you will make all your customers ahead of your Internet for your INTERNet. The importance of XML on the Web is increasing. Building XML support on Pocket Internet Explorer is a major feature of Pocket Internet Explorer. By using the client JScript, you can create a powerful web application to make full use of the mobile Pocket PC.
