Sean Linsley

@mrienstra I expect he never replied? :/

That means either forcing everyone to use one, or supporting all of the popular ones. That's a non-trivial amount of work for maintainers and people using AA, so I want...

Yeah, we'd probably want to use the built-in JSON API to look up records. I've done this recently: ``` coffee select1 = fieldset.find 'select:first' # Companies select2 = fieldset.find 'select:last'...

[We override it](https://github.com/gregbell/active_admin/blob/7ad6ec39d959c70f580d7eb74fd84b57143e56e7/lib/active_admin/form_builder.rb#L99-L118) :)

I'm going to take this off of the 1.0.0 milestone because this is blocked by #2638 & Kaminari

Hmm, actually this issue is specific to associations so it isn't really blocked by #2638. I'll put this back on the milestone. For the different subjects you mentioned, I'm not...

This ticket is all about resolving the performance issues caused by the association dropdowns we currently build for filters and forms. If we can add a feature like searchable AJAX...

Curiously, helpers will reload if you manually define them ``` ruby ActiveAdmin.register Blah do controller { helper BlahHelper } end ```

Well this is interesting: ``` ruby div method(:helpers).source_location # ...gems/arbre-1.0.1/lib/arbre/element.rb21 div method(:helpers).owner # Arbre::Element div helpers.method(:blah).source_location # ...app/helpers/blah_helper.rb12 div helpers.method(:blah).owner # BlahHelper div "#{blah} -> #{helpers.blah}" # 1 -> 1...

Okay, so maybe not. Here's an experiment strictly from `rails console`: ``` ruby app_1 = ApplicationController.object_id derived_1 = UsersController.ancestors.detect {|a| a.to_s =~ /Appli/}.object_id derived_1 == app_1 # => true reload!...