I'm for to totally drop styles for the scaffolding like Frank suggested and run hooks instead. External gems could use that to modify the scafolding process, like twitter-bootstrap-rails does. The default style should never be used in production anyway.
On Friday, 17 October 2014 01:55:06 UTC, Claudio B. wrote: > > Jason, I understand what you mean. > > My main point was not to introduce Bootstrap into Rails; I agree with you > that the smaller the number of dependencies, the better. > > My point is that scaffold.css already exists in Rails, and it *could be > improved*. > > If the scaffold generator was not already part of Rails, then I would > agree 100% with you. > But it's there, and probably for a reason: to help newbies (and everyone > else) spin off a new project quite rapidly. > > If you remove Bootstrap from the equation, and just think about the > scaffold templating, what is your opinion? > > Do you think that it should actually be *removed* from Rails, since you > describe Rails as "an advanced server-side technology". > Or do you think it should be kept there and, eventually, improved? > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
