|
2
|
1 |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
|
|
2 |
<html>
|
|
|
3 |
<head>
|
|
|
4 |
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
|
|
|
5 |
<meta http-equiv="Content-Style-Type" content="text/css" />
|
|
|
6 |
<title>Creating Custom Components</title>
|
|
|
7 |
<link rel="StyleSheet" href="../../book.css" type="text/css"/>
|
|
|
8 |
<style type="text/css">
|
|
|
9 |
<!--
|
|
|
10 |
.style1 {font-size: 12px}
|
|
|
11 |
-->
|
|
|
12 |
</style>
|
|
|
13 |
</head>
|
|
|
14 |
<body bgcolor="#FFFFFF">
|
|
|
15 |
<h1>Creating Custom Components</h1>
|
|
|
16 |
<p>The following section provides information on creating your own custom components that appear in the UI Designer and can be used when creating a UI design for your application. First some background information is provided about the basic design of components and how they interact with the UI Designer.</p>
|
|
|
17 |
<h2>Overview</h2>
|
|
|
18 |
<p>A UI designer project contains a set of .uidesign files. There is one for each design "view", for example the top-level visual container. There is also a .uidesign file (application.uidesign) for the application as a whole, which includes the AppUi.</p>
|
|
|
19 |
<p>A .uidesign file represents a data model and contains the configuration of a single container or form. The contents of each data model are the persistent state of a set of component instances. Each component instance can have properties, event bindings, and localized strings. Component instances come from the set of available components for a project; based on the selected SDK. Components are listed in the Palette of the UI Designer. Additional component instances are added as the user edits a UI design. Custom components created by a user will also appear in the UI Designer Palette.</p>
|
|
|
20 |
<p>Much of the functionality of the UI Designer is built on components, including determining compatibility across containers, rendering the simulated UI appearance, and generating source code. At the very least, components can be defined by property values, a source code template, and containment rules. Code may also be provided, either in JavaScript or Java, to implement user-defined behavior. However, more complex designs can be implemented into the creation of components.</p>
|
|
|
21 |
<h5>Related Topics</h5>
|
|
|
22 |
<ul>
|
|
|
23 |
<li><a href="cc_architecture.htm">Custom Component Architecture</a></li>
|
|
|
24 |
<li><a href="cc_new_components.htm">Developing New Components</a></li>
|
|
|
25 |
</ul>
|
|
|
26 |
<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div></div>
|
|
|
27 |
|
|
|
28 |
</body>
|
|
|
29 |
</html>
|