Organize DevKit downloads by supported Ruby version on the Downloads page

44 views
Skip to first unread message

Andrew Pennebaker

unread,
May 9, 2013, 1:04:10 PM5/9/13
to rubyin...@googlegroups.com
Can we more clearly delineate the different DevKit downloads to avoid this?

Luis Lavena

unread,
May 9, 2013, 2:38:15 PM5/9/13
to rubyin...@googlegroups.com
Hello,

On Thu, May 9, 2013 at 2:04 PM, Andrew Pennebaker <andrew.p...@gmail.com> wrote:
Can we more clearly delineate the different DevKit downloads to avoid this?


Top of downloads page:


WHICH DEVELOPMENT KIT?

Down this page, several and different versions of Development Kits (DevKit) are listed. Please download the right one for your version of Ruby:

Ruby 1.8.6 to 1.9.3: tdm-32-4.5.2
Ruby 2.0.0: mingw64-32-4.7.2
Ruby 2.0.0 x64 (64bits): mingw64-64-4.7.2 

What else do you suggest?

-- 
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry

Andrew Pennebaker

unread,
May 9, 2013, 3:39:05 PM5/9/13
to rubyin...@googlegroups.com
Perhaps display the download links in a table like 7zip does.

| Ruby version | DevKit version     |
|------------------------------------------------
|1.8.6 - 1.9.3   | tdm-32-4.5.2       |
-------------------------------------------------
|2.0                | mingw64-32-4.7.2|
-------------------------------------------------
|2.0 x64          | mingw64-64-4.7.2|


--
You received this message because you are subscribed to a topic in the Google Groups "RubyInstaller" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rubyinstaller/2r167b3ZFXU/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to rubyinstalle...@googlegroups.com.
To post to this group, send email to rubyin...@googlegroups.com.
Visit this group at http://groups.google.com/group/rubyinstaller?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Cheers,

Andrew Pennebaker

Richard Campbell

unread,
May 9, 2013, 11:18:28 PM5/9/13
to rubyin...@googlegroups.com
I would go further, create 2 separate pages, one for 1.9.3 downloads and one for 2.0.0 downloads.  Users can choose which version, and on that page they can download both the devkit and that version of ruby.  Luis if you or those involved have no web development experience, i'll gladly take your site, convert it to a rails app, and perform those said changes.  Let me know, just looking to help...

Luis Lavena

unread,
May 10, 2013, 9:36:08 AM5/10/13
to rubyin...@googlegroups.com
Hello Richard,

On Fri, May 10, 2013 at 12:18 AM, Richard Campbell <bet...@gmail.com> wrote:
I would go further, create 2 separate pages, one for 1.9.3 downloads and one for 2.0.0 downloads.  Users can choose which version, and on that page they can download both the devkit and that version of ruby.  Luis if you or those involved have no web development experience, i'll gladly take your site, convert it to a rails app, and perform those said changes.  Let me know, just looking to help...


Well, making the entire thing a rails application just for 2 pages seems way too much.

The current website is a Radiant CMS powered site. I can provide you the DB backup of the pages if you want to setup that locally and work on it.

My idea the entire time was to turn the website into a static site so we can work in text files and we can accept more easily pull requests with modifications.

Thing is that a static website has no power to track stats of downloads or anything like that.

So went the Sinatra route instead:


But as you can guess from the last commit (a year ago) that didn't move forward, specially since I lack the time between work and other stuff I do for Ruby.

I would accept offers that implement either a Sinatra or middleman versions of a static website.

Thank you.
-- 

Justin Baker

unread,
May 10, 2013, 12:44:52 PM5/10/13
to rubyin...@googlegroups.com
On Friday, May 10, 2013 8:36:08 AM UTC-5, Luis Lavena wrote:
On Fri, May 10, 2013 at 12:18 AM, Richard Campbell <bet...@gmail.com> wrote:
I would go further, create 2 separate pages, one for 1.9.3 downloads and one for 2.0.0 downloads.  Users can choose which version, and on that page they can download both the devkit and that version of ruby.  Luis if you or those involved have no web development experience, i'll gladly take your site, convert it to a rails app, and perform those said changes.  Let me know, just looking to help...
 
 
Well, making the entire thing a rails application just for 2 pages seems way too much.

The current website is a Radiant CMS powered site. I can provide you the DB backup of the pages if you want to setup that locally and work on it.

My idea the entire time was to turn the website into a static site so we can work in text files and we can accept more easily pull requests with modifications.

Thing is that a static website has no power to track stats of downloads or anything like that.

So went the Sinatra route instead:


But as you can guess from the last commit (a year ago) that didn't move forward, specially since I lack the time between work and other stuff I do for Ruby.

I would accept offers that implement either a Sinatra or middleman versions of a static website.
 
I'm going to throw my 2cents in here and suggest that maybe we're trying to solve the wrong problem.
 
I think that we need to look at the DevKit itself and figure out how to solve the installation problem from the inside out instead of the outside in.
 
Right now, we use the DevKit to change the Ruby Install itself, which is causing issues like this if we want/need to upgrade the DevKit.
I'm going to say that, instead of spending energy to look at ways to make the website more clear for a confusing problem, we should make the problem less confusing.
 
It's a little more complex than just making a Sinatra site work and editing it though.
Also tedious enough that I haven't made the time to work on it myself.
 
Anyway just my thoughts,
 
Justin
 
Reply all
Reply to author
Forward
0 new messages