Hey Dmitrii —
Shoes.app is friendlier to multiple classes than you might imagine.
You can certainly implement your ImageHolder as a separate class
(defined in the same file, or not) that the Shoes::App tracks and
displays. You can even save and load your ImageHolder instances from
disk, separately from Shoes, using YAML, or PStore or SQLite...
Take a look at some of the more complicated examples on the-
shoebox.org to see how multiple classes are being successfully used.
In many cases, a global reference to the Shoes::App is set, to make it
easier to render graphics from any class.
— omygawshkenas
On Apr 14, 2008, at 7:56 AM, Dmitrii Dimandt wrote:
Hi all!
*two-page-long infatuation with shoes skipped :)*
Long-long ago I made myself an image catalog organizer using Python
and Tkinter.
The central piece of it was an "ImageHolder" component hat consisted
of a stack that contained the image itself, the image's name in a
label, the image's tags in label. Such an imageholder could be
selected/unselected (it wold change border color when clicked), it
had properties that could be manipulated (mostly related to the
contained image - such as rotation, name etc.)
I wonder how all this could be achieved using Shoes, since
everything that happens, happens in the context of the Shoes.app
