[#1263] Draft of the updated Ruby FAQ — Dave Thomas <Dave@...>

33 messages 2000/02/08

[#1376] Re: Scripting versus programming — Andrew Hunt <andy@...>

Conrad writes:

13 messages 2000/02/15

[#1508] Ruby/GTK and the mainloop — Ian Main <imain@...>

17 messages 2000/02/19
[#1544] Re: Ruby/GTK and the mainloop — Yasushi Shoji <yashi@...> 2000/02/23

Hello Ian,

[#1550] Re: Ruby/GTK and the mainloop — Ian Main <imain@...> 2000/02/23

On Wed, Feb 23, 2000 at 02:56:10AM -0500, Yasushi Shoji wrote:

[#1516] Ruby: PLEASE use comp.lang.misc for all Ruby programming/technical questions/discussions!!!! — "Conrad Schneiker" <schneiker@...>

((FYI: This was sent to the Ruby mail list.))

10 messages 2000/02/19

[#1569] Re: Ruby: constructors, new and initialise — Yukihiro Matsumoto <matz@...>

The following message is a courtesy copy of an article

12 messages 2000/02/25

[ruby-talk:01621] Re: Ruby/GTK and the mainloop

From: Masaki Fukushima <fukusima@...>
Date: 2000-02-28 08:41:52 UTC
List: ruby-talk #1621
Ian Main <imain@gtk.org> wrote:
> >  * Toolkit must provides select substitution API such as
> >    g_main_set_poll_func().  I don't know that other toolkits than
> >    GTK provide one.
> 
> and g_timeout_add for sleep () etc. right ?  This is what I was thinking.

Hmm...
We probably think a bit differently.

I have no intention of using g_timeout_add().  In my approach,
Ruby scheduler is dominant and GTK mainloop is a Ruby thread.  So
there is no need of telling timeout to GTK.

Brief description of my proposal:

 * Implement a poll_func using rb_thread_select().  The poll_func
   provides the same facility as select().

 * Register the poll_func to GTK by g_main_set_poll_func().
   Then enter GTK mainloop.

 * When GTK mainloop invokes the poll_func, the poll_func calls
   rb_thread_select() and the control comes back to Ruby
   scheduler.


Masaki Fukushima

In This Thread