Keep graph in memory in object form

[GoogleCodeExporter]

Keep graph in memory in object form

[GoogleCodeExporter]

r131 should help a little. Now we actually know what type of entity each draw 
command deals with. From here 
we should be able to move to creating objects for each of those entities fairly 
easily.

Original comment by [email protected] on 21 Oct 2008 at 6:20

[GoogleCodeExporter]

Original comment by [email protected] on 23 Oct 2008 at 11:10

• Changed state: Started

[GoogleCodeExporter]

As of r142, the graph is now kept in memory in a nested structure. The draw 
commands
are stored in a separate drawAttrs variable in each entity, but the draw() 
method
doesn't make use of this yet.

Original comment by [email protected] on 23 Oct 2008 at 10:41

[GoogleCodeExporter]

Safari didn't like r142. Fixed it in r148.

Original comment by [email protected] on 24 Oct 2008 at 9:50

[GoogleCodeExporter]

As of r188 the draw() method does use the drawAttrs in each entity. Now each 
entity is called upon to draw itself.

In r191 I added the Entity.getAttr() method which can be used to get an 
attribute from an entity. If the entity itself 
doesn't define that attribute, then getAttr() looks at the default values in 
each parent graph until the specified 
attribute is found. This allowed me to fix issue #13 in r193.

So I think I can close this ticket as fixed. The graph structure does exist in 
memory in canvizobj.graphs[0], Canviz 
uses it, and you can use it in your apps if you need info about the graph.

Original comment by [email protected] on 1 Nov 2008 at 7:46

• Changed state: Fixed