On Sunday, May 25, 2014 1:40:40 PM UTC-4, Ruby-Forum.com User wrote:
with the application, and that’s why I invented the action “manage” in
controller". Do you recommend me to investigate into “generate scaffold”
parameters (such as path_names:) and examples of usage. Right now, when
I really want to know how something is done in Rails, I google for it,
hoping that someone else had the same problem. This often works out, but
I would be more happy if I had a documentation of the Rails classes and
methods, in a similar way as it is for Ruby and the standard functions
and -classes. Is this available, or is Rails in the flux so much that we
can’t expect this yet?
Posted via http://www.ruby-forum.com/.
OK, this gives me some more information, but I’m still not completely
I understand the application. It sounds like a given user can have one
more?) dictionaries associated with the user and that each dictionary
one or (probably) many idioms associated with it. In this case, dict is
resource. If I read this right, in your initial application a user
create a dictionary. I’m assuming that you may, in later development,
the option to edit a dictionary (which is different from editing an
or delete a dictionary. However, you also have elements such as import
export that are not standard CRUD actions. You’ve included them in an
action manage, but I have a feeling that import and export may be also
separate actions. I’m making some assumptions here which I frequently
to do when answering posts on this list, and if I’ve assumed
that will affect my answer.
In that case, you would need to extend the resource to include actions
addition to the standard new, create, edit, update, show, index, and
destroy actions. In this case, let’s assume we want to add the action
manage. You would do that as follows:
resources :dicts do
This differs from path_names. path_names changes the name of the path
does not otherwise affect the routing or actions associated with the
resource. The above code adds manage as a separate action, and creates
appropriate routing and named paths to go with it.
With respect to the scaffold generator, yes, I believe it is worth
but there are developers that would disagree and don’t use it. Some of
tutorials, such as the railstutorial.org tutorial that is commonly
referenced on this list, have you use the controller generator and model
generator so that you learn the concepts involved by being forced to
manually create a lot of the elements. I believe this is appropriate
good approach for a tutorial. Likewise, the same tutorial takes you
through the steps of manually creating a user resource and
Again, you should, IMO, understand these concepts. However, there are
some ways to make your development more efficient once you have mastered
these concepts. The scaffold is one of them. Typically, I start with a
scaffold and generally modify it to fit the particular needs of that
resource. Likewise, I don’t usually (never) roll my own authentication,
use the Devise gem.
With respect to documentation, it is true, Rails changes quickly (IMO,
mostly for the better) and sometimes the documentation will lag a bit.
believe, in general, the Edge Guides are well done and would recommend
them. There are a few cases where they may not be as comprehensive as
might need. There is one other resource I would recommend. The Rails
Way is a book you can buy from leanpub.com. I don’t have any
to the book or that site, but if you buy it from them, you automatically
get any updates to the book and they update fairly regularly. This is,
IMO, an excellent reference. I would not use it to learn Rails basics.
It’s fairly advanced and would not be appropriate until you have
the basics through a tutorial, but it covers the topics you asked about
better than any other resource I know of. Hopefully, others have some
input here as I’m sure there are resources I’m not aware of. The
Railscasts are also good, but I’m not sure if they’re being maintained
updated at the moment.
The classes and methods themselves are documented in the Rails API
(api.rubyonrails.org). For example, at
api.rubyonrails.org/classes/ActionView/Helpers/Urlhelper.html you will
all the methods and options for button_to, link_to, mail_to, etc. that
use in view rendering.