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

Session variables in mobile login ux not being set

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

    #16
    Re: Session variables in mobile login ux not being set

    Bump....did you solve this issue Charles? I am having the same issue with the most recent release

    Comment


      #17
      Re: Session variables in mobile login ux not being set

      Sort of Yes, first of all I was under bit of a misunderstanding between a web app and a phone gap app and session variables. If it is a web app my method of setting up the initial values with session variables works as expected. If your using Phone gap you may want to go the route that David K suggested. Like selwyn said, the phone gap app needs a callback to set session variables. I think the idea is you need to understand that the reason a phone gap application appears to run faster is because the shell is rendered from local data and you can store data on the device to make it run faster because of course there is no callback. The option in a UX to pre-render a component is a good indicator as to phone gap readiness (my opinion) so if the component is using a session variable it won't work - and jeez I hope I am not giving you bad info.
      I think you should say if your working on a PG app or a web app and then go from there as to asking what you would need to do, but again, try the state variables as David suggests...OR load your application and then use a button to populate the data and subsequent default values with session variables.
      NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

      Comment


        #18
        Re: Session variables in mobile login ux not being set

        Hi Charles......thanks for the reply. It sounds like state variables are the way to go for me. It is going to be a hybrid app that will eventually be a pg app...so I might as well plan on that from the beginning. Thanks!

        Comment


          #19
          Re: Session variables in mobile login ux not being set

          Well, if I could offer one bit of advice - don't mix the two. Develop a web app OR a pg build but do not think that you will just make it one after. Of course, you can copy the component and save it as a new name and then use that to develop the pg build but in my opinion you will want to start fresh for the pg build. I thought like you at first that I would just turn it into a pg build but to be honest the more I learn the more I think they are two entirely different animals with only some of the same moving parts. the moving parts though involving the phones hardware are what set it apart from the web app and then you throw in disconnected/offline capabilities and local storage - to me it's just NOT the same as a web application and shoudl probably be a whole different thought process from the layout to the process.
          My belief btw is that someday, we will not need a pg build as the phone's hardware will be available via the browser in every way that a desktop is and more - might be a ways off but I bet (again my opinion) that pg will be a thing of the past, an unecessary bridge, and obsolete.
          NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

          Comment


            #20
            Re: Session variables in mobile login ux not being set

            Charles,

            Thanks for you input. I certainly don't have the pg experience you have so I appreciate you taking the time to point out some key points. I am still early in the process so it is good to know now how much different the processes are between web app and pg. I have a lot more studying to do before I have a firm grasp of pg.

            My needs for the pg features are minimal so there will only be a few components that will need to be done specifically for pg. Most of the rest will be fairly plain vanilla and won't use local storage or other hardware features. The project is too massive to be done twice.....it MUST have web app first......pg would be a nice addition if I can make it happen on just a few components....if not....I will have to accept the limitations and not use pg.

            I might pick you brain in the future if that is ok...I am sure I will have tons of questions!

            Best regards,
            Greg

            Comment


              #21
              Re: Session variables in mobile login ux not being set

              Well, like you I wanted a web app first then there are certain aspects that I started thinking I should have an actual pg app for. My best advice is to start with your web app and then as your suggesting build an actual pg app for certain aspects - as a seperate UX and let Alpha build it by using the preset quick panels. In other words your first pg app should be a small test application. To me it's almost like learning a new aspect of Alpha so I started just like I did with Alpha in the beginning - create a login and a simple form for CRUD operations - then start exploring the plugins as needed and read all of the builder tips because you will find that you will need to check certain plugins for certain things to work - but again just like in the beginning of learning Alpha - start small, even though you already know how to build a UX component and a list control, you will find that you may or may not like the behavior added with offline capabilities and list pagination, etc.

              My main goal was speed - things happen faster on local apps - but I am quickly learning that my web app is actually pretty fast if designed right - thanks to Alpha.
              NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

              Comment


                #22
                Re: Session variables in mobile login ux not being set

                Great advice! Thanks so much!

                Comment

                Working...
                X