Save form without redrawing form

johntalbott

AIM redraws a form when it is saved. Has anyone found a way around it? Basically I'd like to save the form data via AJAX.

ACDC

Basically I'd like to save the form data via AJAX.

good luck on that one.

I have been wishing for a more elegant form behaviour for years. I have resigned myself to the fact that it's not technically possible within the scope of how AwareIM works, otherwise it would have been done

Although when setting a form pop up to Modeless its seems to behave more elegantly

pureist

Assume you've tried:
AwareApp.saveForm (this)
I never tred it, but when I tried:
startProcessFromForm (processName, renderOption, htmlElem, saveFlag)
When the saveFlag was set to True, the form appeared save in the 'background' without any visual change/flicker/repaint. Maybe this is similar in operation to above.

I could have imagined it though.

BLOMASKY

I have NO clue if this works, but in my notes, I have the following example of how to save a form when a field loses focus. perhaps this is useful???

var f = parser.getField("AttributeNameOfTextFieldLosingFocus");
$("#" + f.getId ()).focusout (function () {
// do something when focus is lost. To save the form, for example
parser.saveForm ();

});

johntalbott

parser.saveForm () & AwareApp.saveForm (this)

Yes. I've tried both of these. Behind the scenes they do the same thing as a standard Save Form operation which leads to the POST and redraw the form.

It's odd that an AJAX based / SPA application does so much UI redrawing. It appears that the typical (more elegant) approach crossed someone's mind at some point. This comment is straight out of the formSave event handler in the formParser code. 😉

		// for now we will always re-create everything. If we decide not to we need
			// to make sure that:
			// 1. We bind the parser to the new object (whether it is a new one or not)
			// 2. We set or reset values in the fiels. If it is update we need to clear the
			//    dirty flag in each field by setting original value to be the new value
			// 3. For new objects we need to re-bind all the grids and remove any contents

ACDC

It appears that the typical (more elegant) approach crossed someone's mind at some point.

Maybe we can revive the concept, I would pay(chip in) to have this developed as a feature option on a form

mrbdrm

this is causing me alot of trouble with multi select. the field will reset every time i save the form
i will pay for this feature too.

hpl123

johntalbott

Yes .. I'd contribute as well.

pureist

The aspect of the UI/UX to which this redrawing issue relates - inelegance, was a reason we didn't purchase Aware.

I'd bet there are many organizations for whom this aspect ranked high in their purchasing decision, and despite Aware's 'nuts and bolts' being GREAT, nevertheless ultimately opted for a development tool which required more work, more time, and more cost, than if using Aware (because its nuts and bolts are not as good/expedient as Aware's) but which ultimately produced an app having a more elegant, refined, subtle, slick, etc., user experience/UI than would have been possible if using Aware.

But I live in hope that one day..

I recognize and appreciate the enormous complexity involved in an application development application such as Aware, but the reality of present-day is that, while in the past function at the expense of form was often acceptable, nowadays everyone expects function and form without any compromise on either.

End-user experience is paramount.