This is interesting. A while ago I was asking exactly the opposite: to replace api.rubyonrails.org by the version generated with "rake doc:rails".

The reason is that it is currently very hard to point someone to some specific bit of the API since it uses frames.

Another disadvantage of using frames is that it is not cache-friendly. I tried o F5/Ctrl+F5/Shift+F5 in my Chrome browser to get the updated version of the Rails api but it didn't updated the frame page.

Only the index itself was updated.

I don't think api.rubyonrails.org should use frames. Now you want to introduce the same problems to the version generated with "rake doc:rails"? Please, don't do that.

Cheers,
Rodrigo.

Em 12-07-2012 06:15, Frederick Cheung escreveu:
Is there a reason why rake doc:rails doesn't use the (to my eyes,
nicer) sdoc template used for api.rubyonrails.org?

Happy to throw together a patch if the reasons are purely historical

Fred


--
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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core?hl=en.

Reply via email to