So, just to recap the flow of this conversation for myself:
a) We, as developers *of* Rails (or at least those who lurk here), realize that
we're not the primary target of scaffolding. So, while it could be moved to gem
for pros, it would be hard on new developers if it wasn't baked in and
hi
I spent 4 years using Rails as a teaching language both inside and outside a
local University. We stopped telling students that scaffolding even existed
after two semesters. It wash't that, as you might except, we had a problem with
generating code instead of doing work by hand. Instead we saw t
>
> Isn't "name 'bob'" the syntax for passing "bob" as an argument into the
> "name" method? Or has that all changed too?
>
> If I saw "name 'bob'", I would think that there's a method named "name"
> defined somewhere.
>
> def name(str)
> # do something with str
> end
>
>
Sounds like a great
I think the appropriate question to ask is "of Rails developers unit testing
their javascript, who is *not* using Jasmine"
I definitely get the impression that
* most people are not unit testing their javascript application code, instead
relying on integration tests to catch errors
* among thos
As I mentioned, I only recall seeing it from quite some time back.
Have been unable to relocate it.
2010/2/26 Prem Sichanugrist :
> Could you please point out to the ticket that was rejected?
>
> On 27 ก.พ. 2553, at 2:43, Trek wrote:
>
>> Every once in a while I get bit when hand crafting a checkb
I've been using Rails to teach web application development at the
University level since 2005. The very first thing we do in the section
about routing is entirely zero out the routes.rb file to be an empty
routing block.
This comes from several semesters of working with default routes
available an
:if_nil doesn't describe all cases. The collection could be not nil
(e.g. an empty array) and you'd still want the blank slate to show.
I'd suggest something related to blankness since it's the "blank
slate" and both [ ].blank? and nil.blank? return true.
render :partial => "post", :collection =
On Thu, Aug 27, 2009 at 2:50 PM, Luciano G.
Panaro wrote:
>
> On Aug 27, 2:18 pm, Trek Glowacki wrote:
>> I like the concept and think it should be expanded to other
>> associations. We already define certain attributes of associated
>> objects for selecting, the symmetr
I like the concept and think it should be expanded to other
associations. We already define certain attributes of associated
objects for selecting, the symmetry of having build/create defaults is
handy.
I could use it on a current project right now:
has_many :trial_memberships, :conditions => {:s
Hi,
rubyonrails-core is for discussing the development _of_ Rails.
Repost this on rubyonrails-t...@googlegroups.com for help with
development _using_ Rails.
Additionally, you may want to see
http://wonderfullyflawed.com/2009/02/17/rails-forms-microformat/ for a
detailed explanation of what HTML
I always assumed that AR::Base and AC::Base's name came from the concept of
an abstract base class. I think ::Base is a fine name for the top-most
superclass in a module, but that might just be a side effect of previous
experience.
-Trek
On Thu, Oct 9, 2008 at 12:42 PM, Manfred Stienstra <[EMAIL
I'd just suggest letting :other_name (or whatever the correct term
shakes out to be) take an array
map.resources :people, :other_names => ['folks', 'gentes','personoj']
do |person|
person.resources :comments
end
This pattern can support multiple aliasing in segment paths for people
who ne
12 matches
Mail list logo
