This preface includes:
This guide describes how to use the Web Browser Engine for the QNX Neutrino RTOS.
If you're familiar with earlier versions of the Web Browser Engine, you should read the What's New appendix to find out the Web Browser Engine has changed in this release.
This table may help you find what you need in this book:
|For information about:||See:|
|An overview of the Web Browser Engine||Overview|
|Running the Web Browser Engine Sample Application||Running the Web Browser Engine Sample Application|
|The WebView class||WebView|
|The WebNotificationDelegate class||WebNotificationDelegate|
|The WebFrame class||WebFrame|
|The GfCallbacks class in GfWindow||GfWindow|
Throughout this manual, we use certain typographical conventions todistinguish technical terms. In general, the conventions we useconform to those found in IEEE POSIX publications. The following tablesummarizes our conventions:
|Code examples||if( stream == NULL )|
|File and pathnames||/dev/null|
|Keyboard input||something you type|
|Programming data types||unsigned short|
|Programming literals||0xFF, "message string"|
We use an arrow (→) in directions for accessing menuitems, like this:
You'll find the Other... menu item under.
We use notes, cautions, and warnings to highlight importantmessages:
|Notes point out something important or useful.|
|Cautions tell you about commands or procedures that may haveunwanted or undesirable side effects.|
|Warnings tell you about commands or procedures that could bedangerous to your files, your hardware, or even yourself.|
In our documentation, we use a forward slash(/) as a delimiter in all pathnames,including those pointing to Windows files.
We also generally follow POSIX/UNIX filesystem conventions.
To obtain technical support for any QNX product, visit theSupport areaon our website (www.qnx.com).You'll find a wide range of support options, including community forums.
Copyright © 2009–2018, QNX Software Systems Limited, a subsidiary of BlackBerry Limited. All rights reserved.