Prev: Saving HTML as MHT
Next: LoadError: no such file to load -- tk
From: Terry Michaels on 18 Jul 2010 22:45
I read through the Shoes manual, and I understand that Shoes is an
event-oriented infrastructure. And in event-oriented programming, you
are supposed to write functions that do their job quickly and then exit,
allowing Shoes to take care of painting, mouse events, et cetera.

However, I am attempting to apply a shoes interface to a program that
was not written to be event-oriented. Most of the run-time is spent
inside various functions that do not exit quickly. Do I need to rewrite
my program engine, or is there some hidden Shoes call I can make that
would cause the app to take care of its graphical and event maintenance?
--
Posted via http://www.ruby-forum.com/.

From: Steve Klabnik on 19 Jul 2010 00:12
[Note: parts of this message were removed to make it a legal post.]

I believe the right way to do this would be to use a Thread that runs in the
background, but I'm not 100% sure. So I'm crossposting this response (as
well as your individual post) to the shoes mailing list so that maybe one of
them can help answer.

On Sun, Jul 18, 2010 at 10:45 PM, Terry Michaels <spare(a)frigidcode.com>wrote:

> I read through the Shoes manual, and I understand that Shoes is an
> event-oriented infrastructure. And in event-oriented programming, you
> are supposed to write functions that do their job quickly and then exit,
> allowing Shoes to take care of painting, mouse events, et cetera.
>
> However, I am attempting to apply a shoes interface to a program that
> was not written to be event-oriented. Most of the run-time is spent
> inside various functions that do not exit quickly. Do I need to rewrite
> my program engine, or is there some hidden Shoes call I can make that
> would cause the app to take care of its graphical and event maintenance?
> --
> Posted via http://www.ruby-forum.com/.
>
>

 | 
Pages: 1
Prev: Saving HTML as MHT
Next: LoadError: no such file to load -- tk