> I also have a question... as I was told there's no way of saving gtk
> windows to be reopened later in slate, but is at least possible to
> save an image with all Gtk libs loaded? As I said before, it takes
> almost 8 minutes to load gtk so I don't want to do this loading
> everytime I turn on the vm.
Yes, because of all the libraries to be parsed, it's slow to load
everything, and we should be able to avoid this overhead as much as
possible. What ideally should happen is that external Gtk widgets/
resources could adopt or inherit the pattern of ExternalResource (also
used by File, Socket, Directory, and ExternalLibrary objects), in that
there is a "locator" attribute which stores some description of how to
recreate the resource, and then startup/shutdown methods construct and
teardown the actual objects in question. The ExternalResource also
keeps a "handle" attribute for the low-level identifier that the VM
gets and then passes into the image. ExternalResources also has a
parentResource attribute which is currently used for the
ExternalFunction-ExternalLibrary relationship but basically helps
determine the part-subpart dependency structure, in that the children
depend on the parent resource being enabled before they can be
(re)created and work.
In the window's case, the "locator" might be an array specifying
dimensions, and maybe a display tree of widget children along with
their dimensions and attributes. I'm hand-waving at this point, but
does this make sense as a way to think about the problem?