From: "Marvin Gülker" <sutniuq@...>
Date: 2010-07-23T04:37:44+09:00
Subject: Re: Typical Ruby (non-rails) project structure.

Tim Pease wrote:
> On Jul 22, 2010, at 11:41 AM, Carl Jenkins wrote:
> 
>> What is/are the best-practice(s) for a Ruby project structure?
>> 
>> As I am just learning Ruby I put everything in one file but, now I am
>> learning about Modules etc..
>> 
>> In Java, classes where in packages which helped with code organization.
>> Is there a typical way to layout a Ruby project structure?
> 
> Take a look at Mr Bones. It encapsulates many ruby best-practices and 
> lots of rake tasks to take care of the day-to-day development tasks
> 
> 
> gem install bones
> 
> bones create new_project
> cd new_project
> 
> rake -T            # shows you all the available tasks
> rake bones:help    # shows you the various project configuration 
> settings
> 
> 
> Other tools in the same vein as Mr Bones are "hoe" and "jeweler"
> 
> gem install hoe
> gem install jeweler
> 
> 
> I'm slightly partial to Mr Bones being the author and all.
> 
> Blessings,
> TwP

I'm not sure that's what the OP wants. He didn't state he wanted to 
build gems, he just wanted to know how a general Ruby projekt is 
structured (an end-user desktop app maybe?). Well, if one consideres a 
gem as the standard way to write a general Ruby project... ;-)

Marvin
-- 
Posted via http://www.ruby-forum.com/.