[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Fri, 26 May 2006 14:43:39 +0200
I'm cleaning up the display_list struct.
Apart from renaming to DisplayList and making
most methods private I have a couple of questions
as for content of it.
Currently the elements of the container are
display_object_info, which I'm renaming to DisplayItem.
These elements are *never* directly used by callers.
Note that the *only* user for DisplayList is the
Now, a DisplayList should store characters each with
a depth, a matrix and a color transform. These are
information worth keeping in a DisplayItem IMHO.
Anyway, the current implementation only uses the DisplayItem
class to provide reference count and a slot for use in
the underlying vector. This means that whenever a character
is added to a DisplayList, the depth assigned to the
item is forwarded, proxied, to the character object itself.
Indeed a 'character' is in our case a "DisplayCharacter"
as it includes informations about transforms, color and depth.
So, everytime a 'character' is placed in a DisplayList
it is instantiated from a character_def, which has to be
completely defined, and then the DisplayList internals
will assign the requested depth and matrices to it.
In order to simplify things, with current implementation
I'd completely drop the DisplayItem (display_object_info)
What do you think ?
/"\ ASCII Ribbon Campaign
\ / Respect for low technology.
X Keep e-mail messages readable by any computer system.
/ \ Keep it ASCII.
|[Prev in Thread]
||[Next in Thread]|
- [Gnash-dev] DisplayList,