Symbian3/SDK/Source/GUID-EB212C35-5416-4CA7-8091-61B45D78E220.dita
changeset 8 ae94777fff8f
parent 7 51a74ef9ed63
child 13 48780e181b38
equal deleted inserted replaced
7:51a74ef9ed63 8:ae94777fff8f
    10 <!DOCTYPE concept
    10 <!DOCTYPE concept
    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
    12 <concept id="GUID-EB212C35-5416-4CA7-8091-61B45D78E220" xml:lang="en"><title>Toolbar</title><prolog><metadata><keywords/></metadata></prolog><conbody>
    12 <concept id="GUID-EB212C35-5416-4CA7-8091-61B45D78E220" xml:lang="en"><title>Toolbar</title><prolog><metadata><keywords/></metadata></prolog><conbody>
    13 <p>The toolbar offers quick access to some of the key functions in the application
    13 <p>The toolbar offers quick access to some of the key functions in the application
    14 view. All of the functions must also be found from the <uicontrol>Options</uicontrol> menu. </p>
    14 view. All of the functions must also be found from the <uicontrol>Options</uicontrol> menu. </p>
       
    15 <note> Toolbar buttons are <xref href="GUID-8F6F6C2C-C00E-4412-A880-5EEBF7270265.dita">Generic
       
    16 buttons</xref> that have touch functionality.</note>
    15 <fig id="GUID-8F4054B9-F6F6-4328-ACFF-459B03398FAC">
    17 <fig id="GUID-8F4054B9-F6F6-4328-ACFF-459B03398FAC">
    16 <title>Toolbar</title>
    18 <title>Toolbar</title>
    17 <image href="GUID-2A4DED23-D0AB-436A-BCED-F0645FF05726_d0e71460_href.png" placement="inline"/>
    19 <image href="GUID-2A4DED23-D0AB-436A-BCED-F0645FF05726_d0e66217_href.png" placement="inline"/>
    18 </fig>
    20 </fig>
    19 <p>A tooltip is an information pop-up containing information regarding each
    21 <p>A tooltip is an information pop-up containing information regarding each
    20 button must be shown.</p>
    22 button must be shown.</p>
    21 <p>Following toolbar button types can be used:</p>
    23 <p>Following toolbar button types can be used:</p>
    22 <ul>
    24 <ul>
    44 to the reading direction  the first item is placed topmost when the toolbar
    46 to the reading direction  the first item is placed topmost when the toolbar
    45 is vertical and leftmost when the toolbar is horizontal in western languages.
    47 is vertical and leftmost when the toolbar is horizontal in western languages.
    46 The appearance of functions in Toolbar should follow the order presented below.</p>
    48 The appearance of functions in Toolbar should follow the order presented below.</p>
    47 <table id="GUID-D8D1CBB2-C07E-43EA-80E5-9163865A0B2D"><title>Appearance order
    49 <table id="GUID-D8D1CBB2-C07E-43EA-80E5-9163865A0B2D"><title>Appearance order
    48 of toolbar functions</title>
    50 of toolbar functions</title>
    49 <tgroup cols="2"><colspec colname="col1"/><colspec colname="col2"/>
    51 <tgroup cols="2"><colspec colname="col1" colwidth="0.46*"/><colspec colname="col2" colwidth="1.54*"/>
    50 <thead>
    52 <thead>
    51 <row>
    53 <row>
    52 <entry>Function type</entry>
    54 <entry>Function type</entry>
    53 <entry>Description</entry>
    55 <entry>Description</entry>
    54 </row>
    56 </row>
   103 <p>The application may decide the initial state of ON/OFF and Mode toggle
   105 <p>The application may decide the initial state of ON/OFF and Mode toggle
   104 button in application launch. They can also be reset or resumed from the previous
   106 button in application launch. They can also be reset or resumed from the previous
   105 session.</p>
   107 session.</p>
   106 <fig id="GUID-2D9D4495-4AA3-4DA8-9AC7-B989189CD2F3">
   108 <fig id="GUID-2D9D4495-4AA3-4DA8-9AC7-B989189CD2F3">
   107 <title>Toolbar button states: example of ON/OFF type of button</title>
   109 <title>Toolbar button states: example of ON/OFF type of button</title>
   108 <image href="GUID-9E0C8892-E67F-4DC9-8253-2F65611AD4C6_d0e71631_href.png" scale="50" placement="inline"/>
   110 <image href="GUID-9E0C8892-E67F-4DC9-8253-2F65611AD4C6_d0e66389_href.png" scale="50" placement="inline"/>
   109 </fig>
   111 </fig>
   110 <section id="GUID-EC526E89-570D-4611-A44D-ABDA4918805E"><title>Floating toolbar</title><p>Floating
   112 <section id="GUID-EC526E89-570D-4611-A44D-ABDA4918805E"><title>Floating toolbar</title><p>Floating
   111 toolbar is a component for showing the key functions on top of the Main pane
   113 toolbar is a component for showing the key functions on top of the Main pane
   112 or full screen content. It can be used in non-touch UI, but also in touch
   114 or full screen content. It can be used in non-touch UI, but also in touch
   113 UI.</p><p>Floating toolbar owns the focus, and thus it can be used only if
   115 UI.</p><p>Floating toolbar owns the focus, and thus it can be used only if
   118 is open by default.</p><p>Floating toolbar can also be designed to be opened
   120 is open by default.</p><p>Floating toolbar can also be designed to be opened
   119 via MSK labeled as <uicontrol>Toolbar</uicontrol>. For closing the toolbar,
   121 via MSK labeled as <uicontrol>Toolbar</uicontrol>. For closing the toolbar,
   120 there has to be then a <uicontrol>Hide</uicontrol> button or the toolbar is
   122 there has to be then a <uicontrol>Hide</uicontrol> button or the toolbar is
   121 closed after selecting a function. Navigation keys can be used as a shortcut
   123 closed after selecting a function. Navigation keys can be used as a shortcut
   122 for opening and closing the toolbar, when not used for anything else in the
   124 for opening and closing the toolbar, when not used for anything else in the
   123 view. Time-out can be used for closing the toolbar.</p><p>There
   125 view. Time-out can be used for closing the toolbar.</p><p>There can be 3-6
   124 can be 3-6 buttons in the floating toolbar depending on used resolution. Thus
   126 buttons in the floating toolbar depending on used resolution. Thus the most
   125 the most important functions must be designed to be the first ones in the
   127 important functions must be designed to be the first ones in the toolbar;
   126 toolbar; so that they are visible, for example, in case only three buttons
   128 so that they are visible, for example, in case only three buttons fit the
   127 fit the layout.  </p><p>When the toolbar is open, it owns the Selection key
   129 layout.  </p><p>When the toolbar is open, it owns the Selection key for selecting
   128 for selecting the focused toolbar button. Toolbar does not own the right and
   130 the focused toolbar button. Toolbar does not own the right and left softkeys.
   129 left softkeys. The user can move the focus over the toolbar buttons with the
   131 The user can move the focus over the toolbar buttons with the Arrow keys (left
   130 Arrow keys (left and right). The focus loops, and the toolbar itself does
   132 and right). The focus loops, and the toolbar itself does not scroll.</p></section>
   131 not scroll.</p></section>
       
   132 <section id="GUID-2010D820-45FF-464A-8C11-34A657A566B3"><title>Floating toolbar
   133 <section id="GUID-2010D820-45FF-464A-8C11-34A657A566B3"><title>Floating toolbar
   133 extension</title><p>Toolbar button can be reserved for opening a toolbar extension,
   134 extension</title><p>Toolbar button can be reserved for opening a toolbar extension,
   134 where more options can be found. Placement of the extension button within
   135 where more options can be found. Placement of the extension button within
   135 toolbar can be found from the appearance order in the table <xref href="GUID-EB212C35-5416-4CA7-8091-61B45D78E220.dita#GUID-EB212C35-5416-4CA7-8091-61B45D78E220/GUID-D8D1CBB2-C07E-43EA-80E5-9163865A0B2D">Appearance order of toolbar functions</xref>. The button has a default graphic,
   136 toolbar can be found from the appearance order in the table <xref href="GUID-EB212C35-5416-4CA7-8091-61B45D78E220.dita#GUID-EB212C35-5416-4CA7-8091-61B45D78E220/GUID-D8D1CBB2-C07E-43EA-80E5-9163865A0B2D">Appearance order of toolbar functions</xref>. The button has a default graphic,
   136 which the application can change if needed. </p><p>Toolbar extension buttons
   137 which the application can change if needed. </p><p>Toolbar extension buttons
   164 a highlight, and thus it can be used in all views (whether main pane needs
   165 a highlight, and thus it can be used in all views (whether main pane needs
   165 the highlight or not).</p><p>  Fixed toolbar cannot be opened or closed, but
   166 the highlight or not).</p><p>  Fixed toolbar cannot be opened or closed, but
   166 it is always visible. Toolbar can be hidden in case other controls are also
   167 it is always visible. Toolbar can be hidden in case other controls are also
   167 hidden (in full screen views).</p><fig id="GUID-C5A359DF-1C8F-42D3-B86F-79A49EB97D70">
   168 hidden (in full screen views).</p><fig id="GUID-C5A359DF-1C8F-42D3-B86F-79A49EB97D70">
   168 <title>Toolbar in touch UI fixed in the layout</title>
   169 <title>Toolbar in touch UI fixed in the layout</title>
   169 <image href="GUID-05C87497-738B-473C-B5B2-BE46D32225F5_d0e71711_href.png" placement="inline"/>
   170 <image href="GUID-05C87497-738B-473C-B5B2-BE46D32225F5_d0e66467_href.png" placement="inline"/>
   170 </fig></section>
   171 </fig></section>
   171 <section id="GUID-4BBFEE08-26AA-4F6E-B74A-F82BD75F3E59"><title>Toolbar extension
   172 <section id="GUID-4BBFEE08-26AA-4F6E-B74A-F82BD75F3E59"><title>Toolbar extension
   172 in touch UI</title><p>As in non-touch UI, toolbars can have extensions also
   173 in touch UI</title><p>As in non-touch UI, toolbars can have extensions also
   173 in touch UI. For floating toolbar in touch UI, the same rules apply as defined
   174 in touch UI. For floating toolbar in touch UI, the same rules apply as defined
   174 for floating toolbar extension in general. In touch UI, the toolbar extension
   175 for floating toolbar extension in general. In touch UI, the toolbar extension
   179 for example, for entering an URL or for the Find function in the browser.
   180 for example, for entering an URL or for the Find function in the browser.
   180 The most important editor field is to be the topmost and has the cursor by
   181 The most important editor field is to be the topmost and has the cursor by
   181 default.</p><note> In case editor field(s) exists, there is less space for
   182 default.</p><note> In case editor field(s) exists, there is less space for
   182 buttons in landscape layout compared to portrait layout.</note></section>
   183 buttons in landscape layout compared to portrait layout.</note></section>
   183 <section id="GUID-C01D7518-956D-41B1-8AD6-540AE70844CD"><title>Using
   184 <section id="GUID-C01D7518-956D-41B1-8AD6-540AE70844CD"><title>Using
   184 toolbars in C++ applications</title><p>The APIs to use for creating a toolbar
   185 toolbars in applications</title><p>The APIs to use for creating a toolbar
   185 are the <xref href="GUID-B05B61B8-1217-441F-BAFA-C209C8F123C5.dita">Toolbar API</xref> for
   186 are the <xref href="GUID-B05B61B8-1217-441F-BAFA-C209C8F123C5.dita">Toolbar API</xref> for
   186 the toolbar itself and the <xref href="GUID-F3EE1000-71A6-4D48-A30B-3D2357BF20FB.dita">Generic
   187 the toolbar itself and the <xref href="GUID-F3EE1000-71A6-4D48-A30B-3D2357BF20FB.dita">Generic
   187 button API</xref> for the buttons in the toolbar.</p><p>For implementation
   188 button API</xref> for the buttons in the toolbar.</p><p>For implementation
   188 information, see <xref href="GUID-95CE2206-7AE0-48C0-97A7-4E2082F9F662.dita">Enabling
   189 information, see <xref href="GUID-95CE2206-7AE0-48C0-97A7-4E2082F9F662.dita">Enabling
   189 quick access to functions with a toolbar</xref>.</p></section>
   190 quick access to functions with a toolbar</xref>.</p></section>