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

Same PhoneGap app two different UX components (Version Management)

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

  • ssmoore1
    replied
    Re: Same PhoneGap app two different UX components (Version Management)

    Thanks Jay! Very helpful tips.

    Leave a comment:


  • imjoken
    replied
    Re: Same PhoneGap app two different UX components (Version Management)

    Scott,

    When we do a major pgb update we do the following:

    1. Make a copy of the UXcomponent, give it a new name and make our changes (and use this new component in our existing pgb project).

    2. In the prior versions UX component, we add a line of code in all of our Xbasic functions (both general and Server-side functions) that immediately pops up a message telling them to update to the latest version and then stops processing. This updated prior version UX then gets published (to the app servers) after the new version is released in both app stores.

    3. As an added measure of control (but totally optional), we use a different subdomain reference in pgb for this new version (submission to pgb). That way we can choose to shut off the prior version if we want. As an example, while our domain is www.myschoolanywhere.com, we use https://pgb1.myschoolanywhere.com for v1 of the app, http://pgb2.myschoolanywhere.com for v2. It requires that you manage your DNS server entries correctly though.

    Hope this helps.
    Jay

    Leave a comment:


  • ssmoore1
    replied
    Re: Same PhoneGap app two different UX components (Version Management)

    Hey David,

    Thanks for confirming that. I will proceed along those lines and let the group know if I hit any snags. It makes sense it should work though, otherwise any major updates would be impossible because without forced updates the original app users would end up with broken apps each time a major new version was introduced.

    Cheers,

    Scott

    Leave a comment:


  • Davidk
    replied
    Re: Same PhoneGap app two different UX components (Version Management)

    I think that makes sense.

    Your existing, compiled, installed, app is calling UX1 on the server.
    Your new app will be calling UX2 on the server.

    There is no forced update process going on... so original users would never see any changes.

    If your back-end tables do not change so that they don't break Version 1... AND... you do not change Alpha Versions/Builds... then things should be ok.

    Leave a comment:


  • Same PhoneGap app two different UX components (Version Management)

    Hi Everyone,

    Just wondering if this is possible. I have a PhoneGap app (Apple Store and Google Play) that is widely used by thousands of end-users. It is a critical app and there can be no downtime. Moreover, I have no control in forcing them to upgrade.

    I would like to make a major upgrade to the app and then release a new version on the app store. The changes to the UX that is the basis for the PhoneGap app will be so significant that it will break the existing installed app.

    My question: is it possible to use different UX components for the same PhoneGap build project? I would like to use a new UX for version 2 but upload it to the existing PhoneGap project (and ultimiately as Version 2 on the app stores). That way the existing iOS and Android App would communicate with UX version 1 and the upgraded iOS and Android app would communicate with UX version 2?

    Thanks!

    Scott
Working...
X