The Building Custom Widgets guide is intended for Photon programmers who want to create custom widgets.
|If you're familiar with earlier versions of Photon, you should read the What's New appendix to find out what has changed in this version..
This manual contains everything you need to know about building your own Photon widgets. Sample code is used throughout this manual to demonstrate new concepts.
|When you want to:
|Learn about widget concepts, attributes, and behavior
|Initialize a widget class, set up a widget instance structure, or set application resources
|Life Cycle of a Widget
|Define a widget class, its resources, methods, or actions
|Anatomy of a Widget
|Choose a widget superclass to base your custom widget on
|Using Widget Superclasses
|Customize a list widget
|Creating a List Widget
|Customize a tree widget
|Creating a Tree Widget
|Add a custom widget to the PhAB widget palette
|Binding Widgets into PhAB
|Manage widgets using the supplied convenience functions
|Widget Building Library API
|Create a custom PhAB resource editor for your widget's resources
|Creating custom resource editors
|Read about the resource editor plugin API
|The resource editor API
|See an example of a resource editor plugin
|Resource editor plugin example
|Read widget-building tips
|Miscellaneous Widget-Building Tips
|Find out what's new in this release
|Look up Photon terms
Throughout this manual, we use certain typographical conventions to distinguish technical terms. In general, the conventions we use conform to those found in IEEE POSIX publications. The following table summarizes our conventions:
|if( stream == NULL )
|File and pathnames
|something you type
|Programming data types
|0xFF, "message string"
We use an arrow (→) in directions for accessing menu items, like this:
You'll find the Other... menu item under.
We use notes, cautions, and warnings to highlight important messages:
|Notes point out something important or useful.
|Cautions tell you about commands or procedures that may have unwanted or undesirable side effects.
|Warnings tell you about commands or procedures that could be dangerous 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.
At the top and bottom of our HTML docs, you'll see some or all of these buttons:
|Use this button:
|To the previous part of the document.
|“Up” in the document:
|To the keyword index.
|To the next part of the document.
To obtain technical support for any QNX product, visit the Support area on our website (www.qnx.com). You'll find a wide range of support options, including community forums.
Copyright ©1996–2010, QNX Software Systems. All rights reserved.