Try designing your external files as modules, too, that get included into your Shoes.app block.
See: http://help.shoooes.net/Rules.html And check out some of the apps in the shoebox. On Sat, Dec 13, 2008 at 21:05, Christopher Small <[email protected]> wrote: > > I did something similar to what you are describing without making a widget. > I was storing the Shoes objects in class attributes of an outside class, but > did all the creating and storing of these objects from within the Shoes.app > block. For my application this was a pretty clean approach. If this would be > messy for yours, then perhaps a widget is the way to go. > > Cheers > > Chris > > > > On Dec 13, 2008, at 4:47 PM, Jordan Applewhite wrote: > >> I'm trying to make a class that has an array of paras, stacks, or some >> other Shoes object. Then, I want to instantiate that class from the file >> that contains Shoes.app and append those elements to a slot therein. I'm >> having a difficult time figuring out how to get my class to recognize the >> shoes objects and methods. I've tried requiring different shoes source >> files and using the $app variable found in the expert-tankspank.rb sample >> (is $app part of the Ruby language or is it a Shoes construct?). How do >> you use shoes elements in your classes outside of the main Shoes.app file? >> >> I'm so very confused. Halp! >> >> Thanks! > > -- alexander rakoczy
