Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Use "thor" instead of "main" for command line arguments processing #183

Open
donv opened this Issue May 19, 2012 · 3 comments

Comments

Projects
None yet
3 participants
Owner

donv commented May 19, 2012

What is the reason we are using the "main" gem for command line processing? It was chosen before I joined the project, so I'd be grateful to know the pros and cons.

I think the help and usage for the "ruboto" command is not good enough as they are now, and the "thor" gem looks very good.

http://whatisthor.com/

I'd like to investigate switching to thor.

@ruboto What do you think? I'll do it on a branch for proper review before a potential merge.

Owner

headius commented May 19, 2012

I am 100% in favor of using Thor instead of main.

Owner

rscottm commented May 20, 2012

Daniel picked main when he did the first cut at ruboto. I don't remember
any pros and cons being discussed. thor looks interesting. I'd support
seeing what it can do.

On Sat, May 19, 2012 at 11:30 AM, Uwe Kubosch <
reply@reply.github.com

wrote:

What is the reason we are using the "main" gem for command line
processing? It was chosen before I joined the project, so I'd be grateful
to know the pros and cons.

I think the help and usage for the "ruboto" command is not good enough as
they are now, and the "thor" gem looks very good.

http://whatisthor.com/

I'd like to investigate switching to thor.

@ruboto What do you think? I'll do it on a branch for proper review
before a potential merge.


Reply to this email directly or view it on GitHub:
#183

Owner

donv commented Aug 18, 2012

...or maybe trollop ?

@donv donv modified the milestones: 1.1.1, 1.1 May 18, 2014

@donv donv modified the milestones: 1.1.2, 1.1.1 Jul 1, 2014

@donv donv modified the milestones: 1.1.3, 1.1.2 Jul 9, 2014

@donv donv modified the milestones: 1.1.3, 1.2 Oct 13, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment