Yeah, I agree that new RailsDoc API needs a revemp. fxn, I know that you've review a lot of commits regarding the documentation. I got a commit access in docrails. Those documentation are generated from lifo/docrails right? Will take a look to see if I can make a change on anything then.
On 30 ?.?. 2553, at 18:17, Xavier Noria wrote: > On Mon, Aug 30, 2010 at 12:38 PM, Leiking <jinleileik...@gmail.com> wrote: > >> railsapi.com is a better choice. > > Unfortunately that's true. > > The API needs a revamp, and I think it needs a revamp beyond a nicer > and searchable template, wrote some thoughts about it a while back > here. > > With all the work going on in Rails 3 focus has been content. In the > future I'd like to see an API as awesome as Rails. In my view > historically their design quality have not been on par. That has to > change. > > It is all open source though, it will fixed if people are interested > in working on it. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To post to this group, send email to rubyonrails-c...@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-core+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
