47 </ul></section> |
47 </ul></section> |
48 <section id="GUID-D8BB0841-1E27-45A0-99AF-0F0A2D0A7362"><title>Architecture</title> <p>The |
48 <section id="GUID-D8BB0841-1E27-45A0-99AF-0F0A2D0A7362"><title>Architecture</title> <p>The |
49 following diagram shows the key components in the Symbian Foundation Graphics |
49 following diagram shows the key components in the Symbian Foundation Graphics |
50 package and some closely related components in other packages. </p> <fig id="GUID-3300E986-4B93-5122-88C4-D7CC231F3BA3"> |
50 package and some closely related components in other packages. </p> <fig id="GUID-3300E986-4B93-5122-88C4-D7CC231F3BA3"> |
51 <title> Symbian^3 component architecture </title> |
51 <title> Symbian^3 component architecture </title> |
52 <image href="GUID-DD22D66C-C303-5432-9C24-71F26190FCA0_d0e191110_href.png" placement="inline"/> |
52 <image href="GUID-DD22D66C-C303-5432-9C24-71F26190FCA0_d0e184514_href.png" placement="inline"/> |
53 </fig> <p>The key ScreenPlay components are introduced below under separate |
53 </fig> <p>The key ScreenPlay components are introduced below under separate |
54 subheadings. </p> </section> |
54 subheadings. </p> </section> |
55 <section id="GUID-AB1E3E20-01A9-4090-A404-0D1FF978AF53"><title>Graphics Composition </title><p>The |
55 <section id="GUID-AB1E3E20-01A9-4090-A404-0D1FF978AF53"><title>Graphics Composition </title><p>The |
56 composition engine composes content, possibly from several different sources, |
56 composition engine composes content, possibly from several different sources, |
57 before it is displayed on the screen. Composition involves the important concepts |
57 before it is displayed on the screen. Composition involves the important concepts |
98 The diagram focuses on the more relevant components and does not attempt to |
98 The diagram focuses on the more relevant components and does not attempt to |
99 show all components in the complete solution. This solution has a dependency |
99 show all components in the complete solution. This solution has a dependency |
100 on the S60 middleware layer, in particular on the Hitchcock component (which |
100 on the S60 middleware layer, in particular on the Hitchcock component (which |
101 is in the UI Accelerator package). </p><fig id="GUID-0D91F9A6-68FC-5316-A16D-A3238F8452AD"> |
101 is in the UI Accelerator package). </p><fig id="GUID-0D91F9A6-68FC-5316-A16D-A3238F8452AD"> |
102 <title> Render stage solution A </title> |
102 <title> Render stage solution A </title> |
103 <image href="GUID-643AFF2D-3EDB-5FAB-9631-7B93FABC56B6_d0e191164_href.png" placement="inline"/> |
103 <image href="GUID-643AFF2D-3EDB-5FAB-9631-7B93FABC56B6_d0e184568_href.png" placement="inline"/> |
104 </fig><p>Another possible solution (called <i>solution B</i>) is based on |
104 </fig><p>Another possible solution (called <i>solution B</i>) is based on |
105 the DirectGDI and Graphics Resource components (which are described next), |
105 the DirectGDI and Graphics Resource components (which are described next), |
106 both of which have interface and adaptation layers. This solution is not full |
106 both of which have interface and adaptation layers. This solution is not full |
107 featured. Like the previous diagram, this diagram focuses on the more relevant |
107 featured. Like the previous diagram, this diagram focuses on the more relevant |
108 components and does not attempt to show everything. </p><fig id="GUID-6A761DC5-1141-5515-BD03-09FBFE56F2D7"> |
108 components and does not attempt to show everything. </p><fig id="GUID-6A761DC5-1141-5515-BD03-09FBFE56F2D7"> |
109 <title>Render stage solution B</title> |
109 <title>Render stage solution B</title> |
110 <image href="GUID-3DD37A41-E822-5CB6-A59E-0B309B5627D9_d0e191176_href.png" placement="inline"/> |
110 <image href="GUID-3DD37A41-E822-5CB6-A59E-0B309B5627D9_d0e184580_href.png" placement="inline"/> |
111 </fig><p>Both of these render stage solutions mean that existing Window Server |
111 </fig><p>Both of these render stage solutions mean that existing Window Server |
112 applications can take advantage of hardware acceleration if it is available |
112 applications can take advantage of hardware acceleration if it is available |
113 (and therefore run faster) without recompiling the code. </p><p>ScreenPlay |
113 (and therefore run faster) without recompiling the code. </p><p>ScreenPlay |
114 provides extensions to the Window Server client-side API, which enable mobile |
114 provides extensions to the Window Server client-side API, which enable mobile |
115 devices to respond to events from a number of pointers, including their proximity |
115 devices to respond to events from a number of pointers, including their proximity |