Park on 1st field on form by default

rbross

Hello,

I have a form with one field on it and you still have to press Tab to move to that field or click it with the mouse.
Is there a piece of js we can add someplace so when the form opens it is parked on the field?

customaware

https://awareimdevelopers.com/2017/07/23/place-cursor-in-1st-field-on-a-form/

rbross

NICE!
I like code when you don't have to replace anything with an AwareIM tag!
Just cut and paste...
Thanks Mark

BLOMASKY

Wouldn't this be NICE if it was just a checkbox in the form design? Yes, it works FINE, but why do we have to paste in about 20 lines of code to do this? YO VLAD!, How about a checkbox (ok, you guys call it TICK I think) to do this.

Bruce

BLOMASKY

How come the cursor going to the 1st field is NOT the default? Where the heck should the cursor be?

(Feel free to ignore most of my posts the rest of this week. On vacation @ Lake George NY with my grandsons. Right now, down in lobby sipping some nice Titos Vodka over ice.)

Bruce

rbross

BLOMASKY wrote
How come the cursor going to the 1st field is NOT the default? Where the heck should the cursor be?
Bruce

Agreed. It would be nice it just defaulted to the first field. After all, it allows you to set the tab order but still doesn't park on the first field.

rbross

BLOMASKY wrote
Wouldn't this be NICE if it was just a checkbox in the form design? Yes, it works FINE, but why do we have to paste in about 20 lines of code to do this? YO VLAD!, How about a checkbox (ok, you guys call it TICK I think) to do this.

Bruce

Ditto

BenHayat

@ Bruce [Lee]
Not Sure Vlad reads every single forum post. PLEASE send this request to support directly with your solution, so they can add it in.

Thanks!

johntalbott

I vote we let Vlad stay focused on bigger fish, as it's easy to make this a "global" one and done for all forms.

Put the below in a custom js file

function setupDefaultFocus() {
	
AwareApp_FormParser.prototype.setFocus = function (sectionName) {
	if (this.m_fields) {
		var firstTabIdx = null,
		focusSet = false;
		for (var i = 0, len = this.m_fields.length; i < len; ++i) {
			var f = this.m_fields[i];
			var tabIndex = f.getTabIndex();
			if (tabIndex && tabIndex == "1") {
				firstTabIdx = f;
				if ((!sectionName || sectionName == f.getSectionName()) && f.setFocus())
					focusSet = true;
				break;
			}
		}
		if (!focusSet) {
			for (var i = 0, len = this.m_fields.length; i < len; ++i) {
				var f = this.m_fields[i];
				if (f != firstTabIdx && (!sectionName || sectionName == f.getSectionName()) && f.setFocus())
					break;
			}
		}
	}
}	

}

In the Init Script of a VP content panel call the set up function. It doesn't matter which panel, we're just using it as a place to execute the code before forms are being rendered.

 setupDefaultFocus()

Kick your feed up, drink some vodka ... while Vlad focuses on consuming/exposing REST services.

BenHayat

johntalbott wrote
I vote we let Vlad stay focused on bigger fish, as it's easy to make this a "global" one and done for all forms..

Thank you John for your participation. I/we appreciate your contributions.

BLOMASKY

johntalbott wrote
I vote we let Vlad stay focused on bigger fish, as it's easy to make this a "global" one and done for all forms.

In the Init Script of a VP content panel call the set up function. It doesn't matter which panel, we're just using it as a place to execute the code before forms are being rendered.
 setupDefaultFocus()
Kick your feed up, drink some vodka ... while Vlad focuses on consuming/exposing REST services.

John, you are a gentleman and a scholar and I am sure, much better looking than me. A question, do we have to put this in EVERY VP that is being called in our app, or just one to initialize this?

You are right, this is NOT high on the importance list, but I assume this is low lying fruit and perhaps would take 20 min of our most talented Vlad.

Trust me on the drinking of vodka. Pretty sure my blood is very sterile after all the alcohol being consumed Hic.. Hic.

But, being semi serious now. Lets talk about REST, and specifically consuming (calling) a REST service. It would seem to me that the biggest issue is that most REST services that return a result do that in a JSON object. So, the biggest issue is how to decode that into something that Aware can understand. Without a significant change to the way aware maps and stores data, This might not be so easy. (Many JSON result sets look like nested arrays. Optional nested arrays!) Of course, Vlad CAN do most anything!

I think it might be FUN to have a voice chat (sort of like our fun webinars) to focus and discuss options with exposing Aware functions as REST services. I have accomplishing what I need via a Node REST server and SQL scripts and stored procedures. Perhaps others have found work-a-rounds also?

Bruce

johntalbott

BLOMASKY wrote
A question, do we have to put this in EVERY VP that is being called in our app, or just one to initialize this?

It should be just the first VP only.

BLOMASKY wrote
You are right, this is NOT high on the importance list, but I assume this is low lying fruit and perhaps would take 20 min of our most talented Vlad.

Eh .. not so much. I can count on one finger, the number of times a 20 min change was actually a 20 min change. And that was my wife changing her shoes.

Plus I'm sure there are at 1000 other 20 min changes that could be made. They all take time and add up quickly. At any rate, it's a distraction from the bigger fish that can't be addressed with a code snippet in this forum.

BLOMASKY wrote
But, being semi serious now. Lets talk about REST, and specifically consuming (calling) a REST service. It would seem to me that the biggest issue is that most REST services that return a result do that in a JSON object. So, the biggest issue is how to decode that into something that Aware can understand. Without a significant change to the way aware maps and stores data, This might not be so easy. (Many JSON result sets look like nested arrays. Optional nested arrays!) Of course, Vlad CAN do most anything!

Yes, there will be a lot more than 20 minutes of work involved. That's what makes it a big fish.

I've looked at work-arounds and I will have to go that route unless something changes with AIM soon. Work-arounds at the service level using Node or another platform introduces a whole other level of moving parts that eats away at the value of AIM. The ability to leverage the AIM rules engine goes away.

The bottom line on this topic is ... the world shifted to REST years ago. AIM is way behind the curve. The need to change is inevitable.

BLOMASKY wrote
I think it might be FUN to have a voice chat (sort of like our fun webinars) to focus and discuss options with exposing Aware functions as REST services. I have accomplishing what I need via a Node REST server and SQL scripts and stored procedures. Perhaps others have found work-a-rounds also?
Bruce

Fire it up.

btw ... it took me way longer than 20 mins to post this response.

rbross

After adding the snippet of code :
Why won't Aware park on a date field if it is the first field on the form, it is starting on the second field.
Even if you set the tab order it still won't start on a date field, it starts on the second field.

"AwareApp_FormParser.prototype.setFocus=function(sectionName) {
if (this.m_fields ) {
var firstTabIdx = null, focusSet = false;
for (var i = 0, len = this.m_fields.length; i < len; ++ i) {
var f = this.m_fields ;
var tabIndex = f.getTabIndex ();
if (tabIndex && tabIndex == "1") {
firstTabIdx = f;
if ((! sectionName sectionName == f.getSectionName ()) && f.setFocus ())
focusSet = true;
break;
}
}
if (! focusSet) {
for (var i = 0, len = this.m_fields.length; i < len; ++ i) {
var f = this.m_fields ;
if (f != firstTabIdx && (! sectionName sectionName == f.getSectionName ()) && f.setFocus ())
break;
}
}
}
}"