[#1215] Tk widget demo; English Tk docs?; Java 1.2 Swing — "Conrad Schneiker" <schneiker@...>
Hi,
[#1218] Trivial FAQ bug — Dave Thomas <Dave@...>
[#1229] A vote for old behavior — Dave Thomas <Dave@...>
[#1232] Any FAQ requests, updates, ... — Dave Thomas <Dave@...>
[#1233] Singleton classes — Dave Thomas <Dave@...>
[#1263] Draft of the updated Ruby FAQ — Dave Thomas <Dave@...>
[#1307] Ruby/GTK 0.23 released — Hiroshi IGARASHI <igarashi@...>
Hi all,
From: Hiroshi IGARASHI <igarashi@ueda.info.waseda.ac.jp>
From: "Conrad Schneiker" <schneiker@jump.net>
On Fri, Feb 18, 2000 at 09:37:27PM -0500, Yasushi Shoji wrote:
[#1322] FAQ: Ruby acronyms — "Conrad Schneiker" <schneiker@...>
In the spirit of TABWTDI (there are better ways to do it), I'd like to
[#1341] Vim syntax file — Mirko Nasato <mirko.nasato@...>
Hi,
On Mon, Feb 14, 2000 at 05:44:39PM +0100, Mirko Nasato wrote:
[#1354] Say hi (bis) — Pixel <pixel_@...>
hi all,
[#1355] nice sample for functional stuff — Pixel <pixel_@...>
what about having map in standard (and map_index too)?
[#1373] Ruby Language Reference Manual--Glossary — "Conrad Schneiker" <schneiker@...>
I was going to print the Ruby Language Reference Manual when I noticed that
[#1376] Re: Scripting versus programming — Andrew Hunt <andy@...>
Conrad writes:
[#1379] Re: Yield — Andrew Hunt <andy@...>
>From: "Conrad Schneiker" <schneiker@jump.net>
[#1384] Re: Say Hi — mengx@...
My suggestion was to try to find a more comfortable method name (to me, and
[#1392] Re: Some Questions - Parameterised Types / Invariants — Andrew Hunt <andy@...>
>1. Parameterised Types / Template Classes
[#1398] Bignum aset — Andrew Hunt <Andy@...>
[#1488] Discussion happens on news.groups — Clemens Hintze <c.hintze@...>
Hi,
[#1508] Ruby/GTK and the mainloop — Ian Main <imain@...>
Hello Ian,
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.))
From: "Conrad Schneiker" <schneiker@jump.net>
[#1528] ruby <=> python — Quinn Dunkan <quinn@...>
Hello! I'm new to ruby-talk, and mostly new to ruby. I'm making a document
[#1551] Ruby thread scheduling buglet — Ian Main <imain@...>
[#1569] Re: Ruby: constructors, new and initialise — Yukihiro Matsumoto <matz@...>
The following message is a courtesy copy of an article
[#1591] Certain char's not recognized by "." in regex? — Wes Nakamura <wknaka@...>
[#1592] Race condition in Singleton — Dave Thomas <Dave@...>
[ruby-talk:01642] Re: New Ruby projects
Great idea! I support this effort. If anyone is capable of doing this, but needs the proper development tools, let me know, and I will see what I can do to finance them... I will also provide a website domain and server space to assist in its own growth. I have an interest in seeing something like this done, and have no problem keeping it open source. If anyone else has good ideas, let's hear about them and try to get them moving... Guy N. Hurst Conrad Schneiker wrote: > ... > However, a recent survey/comparison of Python GUI modules, > > http://www.nl.linux.org/~gerrit/gui.html > > indicates that there is growing support to supplant Tkinter with wxPython as > the default Python GUI. (There has been voluminous and intense discussion of > such Python GUI issues in the comp.lang.python newsgroup within the past > couple of week.) > > Anyway, more information about wxWindows may be found here: > > http://www.wxwindows.org > > I think it would be very useful to produce a Ruby/wxwin module for Ruby. > Since the wxPython module has been around for a while, it might be worth > looking into it for good ideas prior to doing a Ruby version. (I don't know > it there would be any problems with the C++ implementation of wxwindows > versus what I think is Ruby's primarily C interface support. I haven't > looked into either one. I'm sure the Pragmatic Duo could surmount any > problems here, if there are any.) > > I also think it would be a very good thing to adopt such a module as the > default Ruby GUI, meaning that it would be included as part of the standard > distribution. This would make it much easier for people to develop, support, > and "sell" Ruby/GUI projects internally and externally. (Even more so if > there were a PGTR chapter on it. :-) > > Conrad