Logged in User Name Friendly Get

[Davidk]

Re: Logged in User Name Friendly Get

Embedded components work well. There are parent and child methods which easily let you gain access to the controls in embedded components. The ControlBar is highly configurable and allows for multiple views... one for the Login screen... change it for everything else... updating sections of it as you go. There are so many possibilities to present this stuff. Don't think you need to follow one path just because someone else says it can't be done... or is difficult.

[carlbsmith]

Re: Logged in User Name Friendly Get

Would love to know how you make the control bar disappear on login, and reappear for everything else. I've been playing with it a good bit, and working with disclosure lists, etc. But I know there is still a good bit it can do that I am not familiar with yet.

[Davidk]

Re: Logged in User Name Friendly Get

Not disappear... just change a title in the ControlBar to "Login" or something. No buttons... just an App Title or Login or both.

[carlbsmith]

Re: Logged in User Name Friendly Get

That could work. So how do you change the control bar to be different for a login screen? I mean, I know how to make a control bar layout, but what actually triggers the control bar to be different for a login vs main application?

[gregincolumbus]

Re: Logged in User Name Friendly Get

Carl,

You use a different layout. There are even action javascript steps to allow you to programmatically change what layout appears. So the default layout for your app would be the one with just the title in an html item. If you don't want anything to appear, then set the data for the html item to  

Then on your after login event you could have the app change the layout (again using action javascript "controlbar" actions).....to the main one with your other items.

The video below shows how to do that

https://www.viddler.com/v/82baaadf

[Davidk]

Re: Logged in User Name Friendly Get

Have a look at the ControlBar videos... all excellent. Specifically for what you're asking about... UXCB--2 Updating ControlBar Data - Dynamic Text. Just one way to use the ControlBar.

[carlbsmith]

Re: Logged in User Name Friendly Get

Thanks for all of the information. The video looks very promising, I will give it a look. So can I throw in a slight twist. Suppose I go with the route ids-dave mentioned above for grabbing the username and displaying that, would that functionality still work if I also incorporate touch ID? I'm still working through that, and the template that Alpha provides for touch ID is a little disappointing to me because it does not seem to do anything with the login information. But suppose I get touch ID working, would grabbing that username field still be effective? I am wondering if the touch ID would allow the user to login with stored credentials without ever actually entering anything in that username field. That is the direction I am wanting to head, so just trying to think out loud on that I guess. Thanks.

[carlbsmith]

Re: Logged in User Name Friendly Get

I'm going a slightly different route with the "logged in as" message. I wrote an xbasic function as follows:

function getlogin as c (e as p)

dim session.UserID as c
dim user as c

session.UserID = a5ws_getcurrentuser()
user = "var ele = {dialog.object}.getPointer('logged_in_as'); ele.innerHTML = '"+js_escape(session.UserID)+"';"
getlogin = user
end function

I created a label with the variable name "logged_in_as", and have a client-side event for "onInitializeComplete that fires an ajaxcallback:

{dialog.object}.ajaxCallback('','','getlogin','','',{deviceOfflineFunction: function() { }});

What I have noticed is that this seems to work ok for testing in a web browser. I say ok because sometimes the username value does not appear and I have to refresh the browser for it to appear. But what I also notice is that when I create a phonegap build, I can't get the username to appear at all. Wondering if there is a better place to trigger this xbasic function. Perhaps as a server side event instead of client side? Any thoughts would be appreciated. I wanted to write it this way as apposed to some of the suggestions above because I think it plays better into my long term plan of incorporating touch ID. But again, open to suggestions. Thanks!