File: tutorial4.html

package info (click to toggle)
entity 0.7.2-6
  • links: PTS
  • area: main
  • in suites: woody
  • size: 5,352 kB
  • ctags: 5,272
  • sloc: ansic: 61,707; sh: 7,921; makefile: 732; perl: 399
file content (59 lines) | stat: -rw-r--r-- 2,103 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Data Structures</TITLE>
</HEAD>
<BODY text="#000000" bgcolor="#ffffff">

<A HREF="tutorial.html"><EM> Entity Introduction </EM></A>
 <b>:</b> <EM>Data Structures</EM><BR>
<b>Previous:</b> <A HREF="tutorial3.html"><EM>Using XML</EM></A><BR>
<b>Next:</b> <A HREF="tutorial5.html"><EM>Getting Started.</EM></A>


<HR NOSHADE>
  <H2><A NAME="4"></A>4. Data Structures</H2>
<p>The XML tree is translated into a live tree of objects, but these objects
may be thought of as if you were manipulating the XML tree directly.
The structures/concepts that make up this tree are:</p>

<p>
<ul>
<li><code>ENode</code><p>This is the basic in-memory node, it has attributes
and stores the information about the item it builds
when it is added to the tree.  An enode is displayed
as 'element.name', when element is the type of node,
and name is the name attribute, if no name attribute
is set, name will be an underscore and a unique
number.  ex 'button._342'.  This is mapped into a Class
in most languages, which you can use to bind to a node
in a running Entity application.  See the ENode API
reference below for more details.</p>
</li>
<li><code>Attribute</code><p>This is an attribute of the enode, within the renderers
functions are registered for when an attribute is set or
requested.  In OO speak, these act as methods of the class of
the node type.</p>
</li>
<li><code>Path</code><p>A Path is how to describe where an enode is in the
program, it starts at the root and progresses down the
tree of enodes, putting the element.name
representation seperated by '/'s until it gets the the
destination enode.  In most languages if you print an
enode it will give its path.</p>
</li>
</ul>
</p>


 <HR NOSHADE>
<A HREF="tutorial.html"><EM> Entity Introduction </EM></A>
 <b>:</b> <EM>Data Structures</EM><BR>
<b>Previous:</b> <A HREF="tutorial3.html"><EM>Using XML</EM></A><BR>
<b>Next:</b> <A HREF="tutorial5.html"><EM>Getting Started.</EM></A>



</BODY>
</HTML>