Use of HFH within javascript

[Sungsam Gong]

Hi,

Is there any way to use HFH within a javascript call?
I just want the form displayed within a pop-up window and doing some ajax stuff.
In specific, I'm using a jquery plugin (boxy) to build a dialog box
and wondering HFH can be fitted into this.

Regards,
Sung

[Rippl, Steve]

Your ajax call can hit a url in your app that returns your HFH form and it puts that html in the pop-up box.  If it's still the native window (as I think you'd get with the JQuery plugin) you'd use more javascript for the submit, if it's a separate window popup then it can be handled by the browser, some JS to close the window on successful submissions etc.  I've used this kind of thing a couple of times and it works OK I think.

--
You received this message because you are subscribed to the Google Groups "formhandler" group.
To post to this group, send email to formh...@googlegroups.com.
To unsubscribe from this group, send email to formhandler...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/formhandler?hl=en.

--
Steve Rippl
Technology Director
Woodland Public Schools
360 841 2730

[Sungsam Gong]

Thanks for this - helped me alot

[Sungsam Gong]

Hi,

One thing I just noticed is that whenever the ajax hits the url, a
hidden parameter, named '_', is passed together, which invokes a form
validation on appearance.
I think the hidden parameter is to point the DOM constructor to
prepare the jquery call.
Nothing to do with HFH, but can you think of any workaround this?

Regards,
Sung

[Rippl, Steve]

I believe $form->process is triggered whenever there's something in $c->req->params, so perhaps something like 

$form->process(...) if  !$c->req->params->{_}

or however you need to shape it...

[Sungsam Gong]

Well, managed to delete a hidden parameter on an ajax call:
delete $c->req->params->{'_'};
$form->process(params=>$c->req->params);

Next challenge is how to process the ajax form on submission - the
'posted' request designates the native URL rather than the URL where
the ajax pops up.

[Rippl, Steve]

On Tue, Sep 11, 2012 at 8:22 AM, Sungsam Gong <gong.s...@gmail.com> wrote:

Well, managed to delete a hidden parameter on an ajax call:
delete $c->req->params->{'_'};
$form->process(params=>$c->req->params);

Next challenge is how to process the ajax form on submission - the
'posted' request designates the native URL rather than the URL where
the ajax pops up.

 

Will setting the form action attribute work? https://metacpan.org/module/HTML::FormHandler::Manual::Reference#Form-Rendering

[Sungsam Gong]

Worked very well:
MyApp::MyForm->new(action=>$c->uri_for('/some_url'));

Many thanks to you.

[Sungsam Gong]

Just realised one caveat for this - no form validation within this action

[Rippl, Steve]

On Tue, Sep 11, 2012 at 9:25 AM, Sungsam Gong <gong.s...@gmail.com> wrote:

Just realised one caveat for this - no form validation within this action

I don't understand, isn't validation triggered by $form->process, or rather the pattern is normally if( $form->process(...)) {...} , it returning some true value if validation occurred successfully...

 

[Sungsam Gong]

What I meant is that after an initial loading of the form by an ajax
call, the parameters are forcefully dealt by non-default action. So no
parameter validation within the catalyst action where the form is
defined.

[Rippl, Steve]

On Tue, Sep 11, 2012 at 9:53 AM, Sungsam Gong <gong.s...@gmail.com> wrote:

What I meant is that after an initial loading of the form by an ajax
call, the parameters are forcefully dealt by non-default action. So no
parameter validation within the catalyst action where the form is
defined.

Why aren't you pointing the action back to the URL where the form was defined?  If for some reason you have to process it elsewhere you can still pull in the form and run process there can't you?

 

[Sungsam Gong]

That's true; $form->process can be pulled and called where the action
is defined.