goocanvas memory usage for model-controller

[Ed Griffiths <edgrif sanger ac uk>]

Hi,

I looked through previous posts and couldn't see anything that addressed this:

I currently work on a project that uses foocanvas, I can see obvious advantages 
to changing to goocanvas but I wanted to ask about the following scenario...

The program I work on creates a large number of canvas items, enough for memory 
usage to be something that needs to be thought about. I need to be able to split 
the canvas window 2, 3 or more times.

In foocanvas I have to duplicate the whole canvas, items and all, for each 
window resulting from the split.

In goocanvas I was hoping that the MVC split would enable me to use less memory 
but having read the architecture page I'm not so sure. It would seem that the 
model items will _not_ need to be duplicated which is what I expected and is 
great. BUT it seems there is a whole other duplicate set of canvas items that 
will need to be duplicated so I might even end up worse off than with the 
foocanvas.

Is that right or am I being an idiot.....


thanks Ed

p.s. I apologise if this has been asked before, I have looked but couldn't find 
anything.
--
  ------------------------------------------------------------------------
| Ed Griffiths, Acedb/ZMap development, Informatics Group,               |
|  The Morgan Building, Sanger Institute, Wellcome Trust Genome Campus   |
|  Hinxton, Cambridge CB10 1HH                                           |
|                                                                        |
| email: edgrif sanger ac uk  Tel: +44-1223-496844  Fax: +44-1223-494919 |
  ------------------------------------------------------------------------


--
The Wellcome Trust Sanger Institute is operated by Genome Research 
Limited, a charity registered in England with number 1021457 and a 
company registered in England with number 2742969, whose registered 
office is 215 Euston Road, London, NW1 2BE.