Re: [Siop-development] SIOP FAQ
Status: Pre-Alpha
Brought to you by:
slobberchops
From: Rapheal K. <ra...@ma...> - 2006-06-12 05:54:23
|
> > Thanks a lot Kevin. These are exactly the kind of things I need to > > focus on. I would like to make the example of Ruby using wx Windows, > > but I don't want to diss your efforts on the wxRuby stuff. I think I've > > heard it from you, in addition to an out of date Ruby site, but is it > > correct that wx support on Ruby is weak? > > Well, you could refer to "a GUI toolkit" rather than naming wx > specifically. But I actually wouldn't mind if you did use it as an > example. wxruby is "sort of working", but I haven't had the time to > "finish" it, and no other developers have stepped up to take the lead. > > Hey, if there's an easier way to make wx available to ruby apps, I might > jump ship. I'm skeptical about how easy it would be to wrap such a large > library, to bridge a few python/ruby differences, and then to make it > bearable to deploy ruby wx apps on all three major OS's. > > I'm intrigued. I would like to see something like that happen. So far, for some Python like reason, I am not able to hook up callbacks to wxWindows, although callbacks in general work over SIOP. Maybe the wxPython has a wierd way of handling setattr. This Ruby code works so far - When I figure a few more things out I will document it on the Wiki... ------------------------------------------- #!/usr/bin/env ruby require 'siop/pipe' Siop::Pipe.connect '../../scripts/siop-standard-server.py' do |bridge| bridge.fetch_namespace nil, 'wx' wx = bridge.remote_context.wx app = wx.PySimpleApp(0) frame = wx.Frame( nil, -1, "This is a test" ) frame.Show( true ) app.SetTopWindow( frame ) app.MainLoop.call end |