You Are Here:

Community: Wiki

This page was last modified on 6 September 2009, at 17:55.

Browser Control API

From Forum Nokia Wiki

Reviewer Approved   

Contents

Introduction

The browser for S60 enables mobile phone users to browse the World Wide Web. Web pages can be implemented in Hypertext Markup Language (HTML), Extended Hypertext Markup Language (XHTML), or Wireless Markup Language (WML). A Browser Control is a browser that you embed into an application to enable users to view Web content from within that application. The host application can control the way the Browser Control displays the Web content, dialogs, softkeys, scroll bars, and so on. The Browser Control API enables developers to do the following:

  • Display XHTML, HTML, WML, CSS, or scripted content inside an application
  • Customize the Browser Control for your specific application. For example,
    • Draw scroll bars
    • Design options menus
    • Display notification messages
    • Customize softkeys
    • Change the display size of a Web page

Environmental Requirements

The Browser Control API is compatible with any application that complies with S60 3rd Edition.

Standards Compliance

The Browser Control API complies with the following standards:

  • ECMA Script Mobile Profile
  • HTML 4.0.1
  • Java Script
  • Wireless CSS
  • WML 1.3
  • WML Script
  • XHTML Mobile Profile

Browser Control Functionality

Basic Browser Control functionality includes:

  • Downloading and displaying Web content
  • Display application content, through (LoadDataL function)
  • Resolving links
  • Retrieving the following information about the downloaded content:
  • Display size needed to see all of the content (ContentSize function)
  • WML options associated with the current page(WMLOptionMenuItemsL function)
  • Value of a specified browser setting (BrowserSettingL function)
  • Indication of whether or not a particular URL is in the cache (IsUrlInCache function)
  • Information about the page, such as its title, URL, and content (PageInfoLC function)
  • Indication of whether there is a previous or next element in the history stack (NavigationAvailable function)
  • Build version of the Browser Control (VersionInfoLC function)
  • Number of images in the current page (ImageCountL function)
  • Type of focused element (FocusedElementType function)
  • Minimum size of the Browser Control (MinimumSize function)

Getting Started with the Browser Control

When using the browser control in your application, you need to use the CBrCtlInterface interface. For this interface you need to include brctlinterface.h in your cpp file.

#include <brctlinterface.h>

you also need to link against browserengine.lib

which you can do by putting the following in your MMP file.

LIBRARY browserengine.lib

The file brctrlinterface.h is filled with usefull comments, its probably better to read that file in order to get more familiarity with the browser control creation and usage.

To create an instance of the browser control you need to use the CreateBrowserControlL function. This function takes quite a lot of parameters, however all of these are explained in the Browser Control API Developers Guide.

The third parameter to this function is TBrCtlDefs::TBrCtlCapabilities, this is an enum which is defined in the brctldefs.h file. Where TBrCtlDefs is a C++ class that holds all the browser defines etc.

Related Links

For more information see: Browser Control API Developer's Guide

Related Wiki Articles

No related wiki articles found

Rate This

 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZidentifierQSxhttpE3aE2fE2fwikiE2eforumE2enokiaE2ecomE2findeE78E2ephpE2fE44etectingE5fMobileE5fE44evicesE5fonE5fWebE5fServicesX qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfntypeZCommunityContentQ qdcZtypeQUqfntypeZE52esourceQ qdcZtypeQUqfntypeZWebpageQ qdcZtypeQUqfntypeZWikiContentQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qfnZtopicQUqfnTopicZbrowsingQ qfnZtopicQUqfnTopicZwebE5ftechnologyQ qfnZtypeQUqfntypeZCommunityContentQ qfnZtypeQUqfntypeZE52esourceQ qfnZtypeQUqfntypeZWebpageQ qfnZtypeQUqfntypeZWikiContentQ qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfntypeZCommunityContentQ qrdfZtypeQUqfntypeZE52esourceQ qrdfZtypeQUqfntypeZWebpageQ qrdfZtypeQUqfntypeZWikiContentQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ
RDF Facets: qfnZuserE5FtagQSxapiX qfnZuserE5FtagQSxbrowserX qfnZuserE5FtagQSxcontrolX