From: ProgramDragon <programdragon@...>
Date: 2008-06-08T16:38:59+09:00
Subject: Re: GUI library/framework?

David,


        Sorry, lol.

        I am not afraid to use libraries, it's just that this is a bot 
program for deviantART's chat network, and usually the people that want to 
get them are not really that coherent in how to actually get one, so I'm 
trying to make it as simple as I can. It's just a few ruby source files that 
can be run with a batch file on Windows. It is open source, GNU GPL license. 
The user just has to download and extract the program from a zip file, 
however would that work with the Gems? It doesn't use a command prompt 
window, the main file is a .rbw file.

    One bot is installed by installing ruby, and then downloading, 
extracting it, and then installing a gem for colors, and then running it 
with a batch file. I would prefer to keep it simple as installing ruby, 
download, extract, and run. I don't mind using gems or having to install 
them, but the user that gets the program might.

--------------------------------------------------
From: "David Masover" <ninja@slaphack.com>
Sent: Sunday, June 08, 2008 12:23 AM
To: "ruby-talk ML" <ruby-talk@ruby-lang.org>
Subject: Re: GUI library/framework?

> On Sunday 08 June 2008 02:03:23 ProgramDragon wrote:
>> I think someone already asked this, but I want to confirm:
>
> In the future, try to find the old thread and reply to it instead of 
> starting
> a new one.
>
>>     I am trying to write a program with a GUI, but I don't know what GUI
>> framework is the best.
>
> Nobody knows that yet, I think. That's why there's so many of them.
>
>>     I want to be able to write this program so that the end user can 
>> install
>> ruby, then run the program and it will start with no other installation
>> needed (like installing gems, etc, however I can do the gems in the 
>> program
>> on first run if it comes down to it).
>
> That's a completely separate problem from what GUI library to use. If 
> you're
> afraid to use libraries for this reason, SOLVE THIS PROBLEM NOW, and then
> worry about GUI libraries. Simplifying your installation program is not an
> excuse for NIH syndrome -- and just think how much time you'll have to 
> polish
> it if you find that half the program you wanted is already a gem.
>
> If it's an open source project, or at least free-as-in-beer, you might
> consider simply making it a gem. Then, all your users need to do is type:
>
> gem install my_great_program
>
> and all the dependent gems will be installed.
>
>