devices.html

qtopiaphone英文帮助,用于初学者和开发人员,初学者可以用来学习,开发人员可以用来资料查询.

</h4>
<a name="4-4-1"></a><p> Some keys are always intercepted before they reach an application. If a pointer device is
available an application can do a keyboard grab to get these keys.
<p> <ul>
<li>Key_F30</li>
<li>Key_F31</li>
<li>Key_F32</li>
<li>Key_F33</li>
<li>Key_F34</li>
<li>Key_F35</li>
<li>Key_NumLock</li>
<li>Key_CapsLock</li>
<li>Key_Menu</li>
<li>Key_Call</li>
<li>Key_Hangup</li>
</ul>
<p> <h4> Keys that are sometimes intercepted
</h4>
<a name="4-4-2"></a><p> <ul>
<li><em>Key_Escape</em> Rejects active dialog</li>
<li><em>Key_F33</em> Accepts active dialog</li>
<li><em>Key_Back</em> Accepts active dialog</li>
<li><em>Key_Context1</em> When behaving as Key_Menu</li>
</ul>
<p> While the screen lock is active (sim card pin required for example) the applications will only be allowed keys such as Key_Back and Key_No.  This is to reduce the chance of anyone accessing the phone's data while the sim-card pin is still required.
<p> <h2> Configuration of Hardware Buttons
</h2>
<a name="5"></a><p> The configuration of hardware buttons for a device is defined
by the etc/defaultbuttons-&lt;platform-spec&gt;.conf files.
<p> The file is divided into sections.
<p> See the existing files, especially the generic file, for guidance.
<p> <h4> User Defineable Button Mappings
</h4>
<a name="5-1"></a><p> The format of the button-mapping section of the file is as follows:
<p> <pre>
[Button]
Count=&lt;number of button records below&gt;
[Button&lt;button number counting from 0&gt;]
Name=&lt;name of the button (in english)&gt;
Name[ja]=&lt;japanese translations of the button name&gt;
Name[&lt;lang&gt;]=&lt;other lang translations of the button name etc&gt;
Key=&lt;associated key code emitted by the button eg. F9&gt;
PressedActionService=&lt;name of default service associated with press&gt;
PressedActionMessage=&lt;message to send to service (refer to services for details)&gt;
HeldActionService=&lt;name of default service associated with press&gt;
HeldActionMessage=&lt;message to send to service (refer to services for details)&gt;
</pre>
 
<p> An example of what this may look like in a real example is:
<p> <pre>
[Button]
Count=2
[Button0]
Name=Calendar Button
Name[ja]=???
Key=F9
PressedActionService=Calendar
PressedActionMessage=raiseToday()
HeldActionService=Calendar
HeldActionMessage=raise()
[Button1]
Name=Contacts Button
Name[ja]=???
Key=F10
PressedActionService=Contacts
PressedActionMessage=raise()
HeldActionService=Contacts
HeldActionMessage=beamBusinessCard()
</pre>
 
<p> Images of the buttons, which should correspond
to the appearance of the device hardware, are in pics/Button/<i>n</i>.png, with
<i>n</i> corresponding to the button number in the configuration file.
<p> <h3> Phone Launcher Menu
</h3>
<a name="5-2"></a><p> The launcher menu on a phone is often a 3 by 4 grid, corresponding
to the positioning of the keys 1 to 9, *, 0, and #.
<p> The format of the launcher menu section of the file is as follows:
<p> <pre>
[Menu]
Rows=&lt;rows of icons&gt;
Columns=&lt;columns of icons&gt;
Map=&lt;one character for each icon, left to right, top to bottom&gt;
Default=&lt;character of initially focussed icon&gt;
&lt;character&gt;=&lt;desktop file or directory&gt;
... for each character in Map.
</pre>
 
<p> An example of what this may look like in a real example is:
<p> <pre>
[Menu]
Rows=3
Columns=3
Map=123456789
Default=5
1=
2=Applications/datebook.desktop
3=Games
4=
5=Applications/addressbook.desktop
6=Settings
7=
8=Applications
9=Documents
</pre>
 
<p> <h3> Phone Buttons
</h3>
<a name="5-3"></a><p> The dialing and other buttons of a phone are configured by the "SystemButtons",
"TextButtons", "PhoneTextButtons", and "LocaleTextButtons" sections
of the defaultbuttons.conf file.
<p> The format of the SystemButtons section of the file is as follows:
<p> <pre>
[SystemButtons]
Count=n
Key0=Name of Qt key code, e.g. Menu, Select, Context1
... for each system button on the device 0 to n
</pre>
 
<p> An example of what this may look like in a real example is:
<p> <pre>
[SystemButtons]
Count=5
Key0=Menu
Key1=Select
Key2=Back
Key3=Call
Key4=Hangup
</pre>
 
<p> The TextButtons section defines all text and actions
associated with each button. For
example, the "2" key is associated with "2", as well as the letters
"a", "b", "c", and all variants of those letters.
<p> The LocaleTextButtons section is like the TextButtons section, except it
only defines the text associated with the current language. The texts in
these sections are translated in the standard way for <a href="config.html">Config</a> files.
<p> The PhoneTextButtons section defines all phone number text and actions
associated with each button.
For example, the "*" key might choose between any of the characters "*", "+", and "p"
(for pause).
<p> The format of the TextButtons, PhoneTextButtons, and LocaleTextButtons
sections of the file are similar, as follows:
<p> <pre>
[TextButtons]
Buttons=0123456789*#
Tap0= ...
Hold0= ...
...
</pre>
 
<p> For each button listed in "Buttons", define:
<p> <ul>
<li> Tap<em>X</em> - the action to do when key <em>X</em> is pressed and released.
This is either:
<ul>
<li> '<em>text</em> - insert character from <em>text</em>.
<li> "<em>text</em> - insert character from <em>text</em>, while showing all options.
<li> space - insert a space.
<li> symbol - popup symbol selector.
<li> modify - choose between alternatives.
<li> mode - change mode or language.
<li> shift - toggle upper/lowercase.
</ul>
<li> Hold<em>X</em> - the action to do when key <em>X</em> is held down. This is the
same as for Tap, except "<em>text</em> is not supported.
</ul>
<p> Character insertions where the first character is punctuation are treated specially.
The details of the special treatment are internal.
<p> <h3> Phone SoftKey Positioning
</h3>
<a name="5-4"></a><p> The format of the soft-key positioning section of the file is as follows:
<p> <pre>
[SoftKeys]
Count=n
Key0=Name of Qt key code, e.g. Menu, Select, Context1
Indent0=Left or Right indent of softkey label
Align0=Alignment of softkey label (1=Left, 2=Right, 4=HCenter, 8=Top, 16=Bottom 32=VCenter)
... for each soft key 0 to n
</pre>
 
<p> An example of what this may look like in a real example is:
<p> <pre>
[SoftKeys]
Key0=Menu
Indent0=4
Align0=33
Key1=Select
Indent1=0
Align1=36
Key2=Back
Indent2=4
Align2=34
</pre>
 
<p> <h2> Non-installed Components
</h2>
<a name="6"></a><p> There are a number of applications/features supplied with Qtopia that are
not intended to be shipped with production devices:
<p> <ul>
<li> Rotation Setting - This is provided to test and demonstrate Qtopia's ability
to display in different orientations. This may be helpful during development
if the device uses the transformation display driver.
<li> Shutdown Setting - This is provided as a development tool.  It should
not be necessary on a production device.  It can be removed by deleting
apps/Settings/quit.desktop, on most devices it is expected that there is
a physical power button, therefore the user is not expected to ever manually
run or shutdown Qtopia.
<li> screensize applet - allows changing the maximum window size for testing
different screensizes quickly during development. This is a
development tool only which is also not intended for end users. 
<li> Terminal - This is provided as a development tool. It may be reasonable to
provide this as a seperate installable package for advanced users who are
familiar with Linux however it is not expected that the majority of users will
find this tool at all useful, only confusing. Therefore it is recommended this
program is not included.
<li> File Manager - Provided as a development tool. Qtopia is functional without
it using just Qtopia's document model.
Adding
the File Browser can make it possible for users to add and remove files from the
device in a way which does not correspond to Qtopia's document model which can break the
interface. We therefore do not recommend this program should be included on a device
to ensure a consistent document model in addition to protecting critical user and system
files and settings.
</ul>
<p> <h2> Unsupported Components
</h2>
<a name="7"></a><p> The following applications are unsupported 3rd party applications/ports
intended purely to demonstrate the flexibility of Qtopia:
<p> <ul>
<li> VNC Viewer
</ul>
<p> <h2> Required Plugins
</h2>
<a name="8"></a><p> If Qtopia crashes twice in quick succession "Safe Mode" will be entered and
no plugins will be loaded in case the crash was caused by a misbehaving
plugin.  In some cases there are plugins that are required for correct
operation of the device.  These plugins can be specified in the .directory
file in $QPEDIR/plugins/&lt;type&gt;/.directory.  For example, if the simple8
text codec is always required:
<p> <pre>
[Desktop Entry]
Name=Text Codecs
Comment=Provides support for various international languages.
Required=simple8
Apply=QPE/System restart()
</pre>
 
<p> <h2> Power Management
</h2>
<a name="9"></a><p> A number of points should be considered when integrating Qtopia with a
device that has power management.
<p> <ul>
<li> Qtopia controls the power state (using pen and key
input to restart timeouts), not the kernel.
<li> The system's "Power" key just sends a key to Qtopia, which
then does the actual suspend.
<li> Qtopia supports multiple shutdown levels. By default these
are On, Light Dim, LightOff, and Suspend. Additional levels
can be added with a small amount of coding.
<li> Qtopia calls platform-specific functions to set lighting level
for 'dimming' and turning off the light.
<li> Qtopia runs the 'apm' command to suspend.
<li> The system's <tt>at</tt> daemon is used to unsuspend upon RTC alarms.
<li> The system's <tt>at</tt> daemon is used to write the RTC clock
(because on some systems only one process can manipulate the RTC).
</ul>
<p> <h2> Removable Storage Cards
</h2>
<a name="10"></a><p> Files from external devices such as SD and CF cards
are automatically scanned on insertion and supported documents are mapped in to Qtopia's
document view. 
<p> The insertion will be triggered when the Qtopia library receives one of the following messages via the QPE/Card QCOP channel:
<p> <ul>
<li> mtabChanged() - Sent when /etc/mtab have changed. 
<li> stabChanged() - Sent when /var/run/stab, /var/state/pcmcia/stab, or /var/lib/pcmcia/stab have changed.
</ul>
<p> If the automatic detection is inadequate due to the specifics of your
device, you may <em>alternatively</em> provide file
/opt/Qtopia/etc/default/Storage.conf, with a group for each
relevant device in /etc/mtab, with settings
of this form:
<p> <pre>
[/dev/hda1]
Name = Internal Storage
Removable = 0
[/dev/sda1]
Name = Card
Removable = 1
</pre>
 
<p> With the above, /dev/hda1 will be internal storage, and
when /dev/sda1 is mounted (eg. by Linux Hotplug system),
a storage location named "Card" will be available to the user: any
documents there will appear on the Documents page. This file can
be translated as with any Qtopia <a href="config.html">Config</a> file.
<p> 
<!-- eof -->
<p><address><hr><div align="center">
<table width="100%" cellspacing="0" border="0">
<tr>
<td>Copyright &copy; 2001-2004 Trolltech
<td><a href="http://www.trolltech.com/trademarks.html">Trademarks</a>
<td align="right"><div align="right">Qtopia version 2.0.0</div>
</table></div></address></body>
</html>