Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Mobile LOGIN with GEO LOCATION

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Mobile LOGIN with GEO LOCATION

    I have a mobile login UX that properly manages login and password
    and saves these to the stock Alpha security files along with any additional
    information I want (stored to a custom SQL SERVER table).

    My PhoneGap settings allow for CORDOVA libraries and specifically enable
    GPS functions.

    Unrelated to login actions I have been able to convert address to location
    information and populate on-screen fields or save the data to a table.

    What I can't seem to do is simultaneously log-in and save user-location
    information to either an onscreen field or to a table.


    This is true for both location-enabled browsers or PDA devices (via phonegap).

    I have altered my SUBMIT button to call the location-gathering form:
    {dialog.object}.submit('','',{getLocationData: true})

    Naturally I have reviewed the server-side Action Script events and settings for
    saving security data and custom data.

    Does anyone have an example of a login UX that also saves user-location info?

    I'll post one myself when I finally get it to work.

    NOTE: Found reference to the following variables in the release notes. Giving that a whirl to populate some hidden longitude/latitude fields and then use the server-side action script to save the field-contents to the remote table.

    __locationFound - true/false
    __locationLatitude - the latitude value
    __locationLongitude - the longitude value

    .

    Thanks!
    Last edited by parkjammer; 01-16-2016, 12:48 AM.

    #2
    Re: Mobile LOGIN with GEO LOCATION

    After many hours of reading, searching, and trial & error I managed to get it working. Will post a solution in the next day or so (once it's cleaned up and fully tested).

    Comment


      #3
      Re: Mobile LOGIN with GEO LOCATION

      Well done.
      Insanity: doing the same thing over and over again and expecting different results.
      Albert Einstein, (attributed)
      US (German-born) physicist (1879 - 1955)

      Comment


        #4
        Re: Mobile LOGIN with GEO LOCATION

        Interim summary of problems and solutions.

        Example or images/video to follow so that the entire thing is represented
        clearly and concisely.

        For now however, here's the short version:

        Goal:
        • Mobile UX to allow user self-registration
        • Gather user location (via GPS)
        • Save new security info (Alpha security) and additional fields (latitude, longitude, and several other fields)
        Challenge:
        • Watched all the relevant videos
        • Getting an odd and unspecific "display" error in javascript when saving
        • Able to eventually save data but lat/long were not also displaying in the UX
        • None of the videos included downloadable samples... that would have helped
        • The videos don't say how the on-screen lat/long fields are populated (only the table fields)... so there is something assumed or actively happening that is not explained
        Resolution:
        • A migration of a DBF to a SQl-Server table lost an auto-increment spec and the result was not a SQL error but this odd "display" error. Fixed now... but took a while to sort out.
        • Per videos I presumed the there would be a place/method to name the on-screen fields for population, THEN save to table.
        • I found that the action-script involved just saves to the record and you have to actively repopulate the UX fields at the tail end of the AJAX call with an "e.control.???" assignment in XBASIC populated from "e.rv.__location???" values populated by the GPS call. Took a while to sort that out.

        More to come.

        Comment

        Working...
        X