Hi all,
I have a question about the advantages/disadvantages of using an array
of Canvases (Canvii?) as opposed to a single Canvas that's
programmatically subdivided. Consider this:
A grid- based game board that can be of a player- determined size. Each
cell will have a background color, possibly a graphic image, and be
clickable so as to change state (active, not active, etc.). When the
player saves their game the state of each cell will have to be stored to
file, and saved games will have to be read from a file as well.
I thought an array of Canvases might work better, but what kind of
issues might I run into? For example, while I imagine a 20 x 20 grid
(400 Canvas objects) would be no problem for any modern computer to
handle, what about something on the order of 100 x 100? 1000 x 1000?
An array of Canvases would also more easily allow for oddly- shaped grid
maps, I believe. Instead of a simple square 20 x 20 I could have
designs such as a plus sign, square with a hole in the middle, and so
on. Game rules (like what does a given cell do when the neighbor cell
is affected) could be added to the Canvas subclass easily.
I think a single Canvas would avoid the possible memory- related issues
an array of 1,000,000 Canvases would have, but would that outweigh
whatever disadvantages the single- Canvas approach has? A single Canvas
seems slightly less OOPish to me, too.
Thanks for any advice!
Timm
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|