[#3741] Re: Why it's quiet -- standard distribution issues — Aleksi Niemel<aleksi.niemela@...>
I think it's the feature of the mailing list archive to create a threads of
[#3756] RE: XMP on comments — Aleksi Niemel<aleksi.niemela@...>
> require "xmp"
[#3766] modulo and remainder — Dave Thomas <Dave@...>
[#3776] Kernel.rand — Aleksi Niemel<aleksi.niemela@...>
How about defining:
[#3781] Widening out discussions — Dave Thomas <Dave@...>
[#3795] Re: Array.uniq! returning nil — Aleksi Niemel<aleksi.niemela@...>
> As matz said in [ruby-talk:3785] and Dave said in [ruby-talk:1229],
Hi, Aleksi,
[#3823] Re: Array.pick — Aleksi Niemel<aleksi.niemela@...>
> > Just a general comment--a brief statement of purpose and using
[#3827] JRuby? — Aleksi Niemel<aleksi.niemela@...>
Is there or will there be Ruby equivalent of JPython?
[#3882] Re: Array.uniq! returning nil — Aleksi Niemel<aleksi.niemela@...>
> |look too strange, confusing, or cryptic. Maybe just @, $, %, &.
Hi,
[#3918] A question about variable names... — Dave Thomas <Dave@...>
[#3935] If your company uses Pallets, Skids, Boxes, Lumber, etc. — pallets2@...
[#3956] Tk PhotoImage options — andy@... (Andrew Hunt)
Hi all,
[#3971] Thread and File do not work together — "Michael Neumann" <neumann@...>
following example do not work correctly with my ruby
[#3986] Re: Principle of least effort -- another Ruby virtue. — Andrew Hunt <andy@...>
> Principle of Least Effort.
Hi,
[#4005] Re: Pluggable functions and blocks — Aleksi Niemel<aleksi.niemela@...>
Aleksi makes a question:
[#4008] Ruby installation instructions for Windows — Aleksi Niemel<aleksi.niemela@...>
I had to write these instructions for my friends. I thought it might be nice
[#4043] What are you using Ruby for? — Dave Thomas <Dave@...>
On 15 Jul 2000 22:08:50 -0500,
Hi,
[#4057] Re: What are you using Ruby for? — Aleksi Niemel<aleksi.niemela@...>
Johann:
[#4082] Re: What are you using Ruby for? — Aleksi Niemel<aleksi.niemela@...>
[#4091] 'each' and 'in' — hal9000@...
I just recently realized why the default
[#4107] Re: 'each' and 'in' -- special char problem? — schneik@...
[#4114] Method signature - a question for the group — Dave Thomas <Dave@...>
[#4139] Facilitating Ruby self-propagation with the rig-it autopolymorph application. — Conrad Schneiker <schneik@...>
Hi,
[#4158] Getting Tk to work on Windows — "Michael Neumann" <neumann@...>
Hi....
[#4178] Partly converted English Ruby/Tk widget demo working. — Conrad Schneiker <schneik@...>
Hi,
[#4234] @ variables not updated within method? — Hugh Sasse Staff Elec Eng <hgs@...>
Hugh Sasse Staff Elec Eng <hgs@dmu.ac.uk> writes:
On 27 Jul 2000, Dave Thomas wrote:
[#4267] Ruby.next, Perl6, Python 3000, Tcl++, etc. -- Any opportunities for common implementation code? — "Conrad Schneiker" <schneiker@...>
Hi,
"Conrad Schneiker" wrote:
[ruby-talk:04150] Re: Tryit (The Ruby Yielding Innovation Toolkit)
Hi, Dave Thomas wrote: > Conrad Schneiker <schneik@austin.ibm.com> writes: > > > Somewhat in the spirit of Hal's self-replicating Ruby programs, I've > > been thinking for some time about what sort of Ruby application would > > facilitate the multiplicative propagation of Ruby. > > Well, you could build it into Microsoft Outlook, and then write a > virus ;-) > > > What I have in mind is RIG-IT, Which I've renamed tryit (The Ruby Yielding Innovation Toolkit) > I think this is a cool idea. You paint a picture of a kind of > drag-n-drop-build-a-tool tool, which sounds ideally suited to > Ruby. Does Ruby/Tk (which was what I was planning to start with for maximum portability and availability) support drag-n-drop? It would be cool if it did. What I actually had in mind was a little less ambitious, but now that you mention it, I recall that SpecPerl (nee SpecTcl, an abandoned and subsequently open-sourced very simple-minded Tcl/Tk GUI builder) used a mode system so that pairs of point-n-clicks did a sort of drag-n-drop emulation. > It'll be interesting to get the right component structure to > allow the various sub-components to play together sensibly as users > drag them in to configurations not conceived of at design time. That may take a couple of tries. As a simpler and perhaps trivial first step, I was thinking of simply making it easy for users to edit (in a property popup) anything they could see. > It > might also be an idea to design it from the start to allow the > components to be distributed across heterogenous machines, as > management of those environments is still a challenge. Very good point. > The project sounds like fun. Hopefully. My main concert is to Ruby fun for new users to play with right out-of-the-box, and to do so in a way that would demonstrate Ruby's capabilities, and to initially introduce people to Ruby by means of experimental modifications, versus having to learn to write stuff from scratch. Any idea where I can get a working copy of the Ruby widget demo for Ruby 1.5? -- Conrad Schneiker (This note is unofficial and subject to improvement without notice.)