Plugin problems: "simply_helpful"

I read at
http://matthewman.net/2006/09/04/new-rails-feature-simply_helpful/ that
"simply_helpful" would introduce a new syntax for the form_for helper.

But even though the plugin is installed (I know that because the dom_id
and dom_class method works) it still doesn't add the id and class to the
form automatically, or point to the update/create action like it should
do, according to the forementioned blog post.

What could be wrong? Any others having problem with this plugin? There's
is nothing in the README
(http://svn.rubyonrails.org/rails/plugins/legacy/simply_helpful/).

Thanks in advance,
Datra.

I read at
http://matthewman.net/2006/09/04/new-rails-feature-simply_helpful/
that
"simply_helpful" would introduce a new syntax for the form_for helper.

But even though the plugin is installed (I know that because the
dom_id
and dom_class method works) it still doesn't add the id and class to
the
form automatically, or point to the update/create action like it
should
do, according to the forementioned blog post.

What could be wrong? Any others having problem with this plugin?
There's
is nothing in the README
(http://svn.rubyonrails.org/rails/plugins/legacy/simply_helpful/).

simply_helpful is obsolete. that functionality was rolled into rails 2
(and having both the rails 2 version and the plugin there is probably
confusing things)

Fred

Frederick Cheung wrote:

form automatically, or point to the update/create action like it
should
do, according to the forementioned blog post.

What could be wrong? Any others having problem with this plugin?
There's
is nothing in the README
(http://svn.rubyonrails.org/rails/plugins/legacy/simply_helpful/).

simply_helpful is obsolete. that functionality was rolled into rails 2
(and having both the rails 2 version and the plugin there is probably
confusing things)

Yes, if I uninstall it, the dom_id and dom_class methods still works.
But the way form_for works still doesn't change.

Any ideas?

how are your using form_for ?

Fred

Frederick Cheung wrote:

...

Yes, if I uninstall it, the dom_id and dom_class methods still
works.
But the way form_for works still doesn't change.

how are your using form_for ?

Like this (in HAML):

- form_for :list do |form|
= form.text_field :title

The output in HTML is:

<form action="/lists/new" method="post"><div
style="margin:0;padding:0"><input name="authenticity_token"
type="hidden" value="..." /></div>
<input id="list_title" name="list[title]" size="30" type="text" />
</form>

Issues: It should point to the create/update actions, not the new/
edit
actions, and the class and id is not added automatically.

If you look at the source it looks like it will only do all that stuff
if you supply an activerecord object.

Fred

Frederick Cheung wrote:

Issues: It should point to the create/update actions, not the new/
edit
actions, and the class and id is not added automatically.

If you look at the source it looks like it will only do all that stuff
if you supply an activerecord object.

Alright, I didn't know that. I've been reading different blog posts
about this plugin, but they never mentioned that.

How can I supply an ActiveRecord object?

Frederick Cheung wrote:

Issues: It should point to the create/update actions, not the new/
edit
actions, and the class and id is not added automatically.

If you look at the source it looks like it will only do all that
stuff
if you supply an activerecord object.

Alright, I didn't know that. I've been reading different blog posts
about this plugin, but they never mentioned that.

How can I supply an ActiveRecord object?

form_for @something etc...

Fred