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

Embedded UX Components in PhoneGap apps

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

    Embedded UX Components in PhoneGap apps

    Ok, I'm confused about something concerning embedded child UX components in PhoneGap apps.
    I'm thinking of trying it out to break up one large UX component. However, I need the application to work offline at times.

    I see a "Precomputed" option in the properties for an Embedded Object:"Method for opening UX in a PhoneGap or Static HTML app"
    I think that if I want everything to work offline, I'll have to use that method.

    I'll be testing it out of course but I wanted to know if I'm going in a totally wrong direction.

    This is were things are clear for me...

    When building the PhoneGap app with the builder, you specify the initial UX component and the URL For All Ajax Callbacks.
    Does that mean that both the Parent and Child UX's need to be published under the same application server application?
    I know that it is possible to set the PhoneGap Ajax Callback URL Dynamically at Runtime, do you have to put that code in something like onInitializeBegin for each component?
    Or because I need to precompute it, does the build process automatically merge the child html into the main index.html on the PhoneGap side and then merge the child UX server code into the parent one as far as the app server app that gets published?

    If so, I don't see the benefit of going in this direction (since I haven't split up the UX's yet).

    [Edit]: I've seen that there is a PhoneGap Multiview Plugin. Has anyone looked into that or even got it working in the AlphaAnywhere environment? I would imagine that you need to produce multiple html pages and I don't see how I would produce them and then submit them to PhoneGap build.
    Last edited by jgrannis; 05-03-2018, 05:30 PM.

    #2
    Re: Embedded UX Components in PhoneGap apps

    This may help a bit...
    https://www.alphasoftware.com/docume...pplication.xml

    Pre-rendered Child components are included as files in the PGB build... but (usually) not rendered until asked for. A pre-computed child file is opened and rendered into the DOM when accessed.

    Once you're done with the child, you can destroy it... removing it from the DOM... in an attempt to keep your app running well.

    The Dynamic Ajax Callback stuff is actually, and usually, quite separate. It doesn't have to be, but usually is.

    You set the URL for the Callbacks in the Alpha PGB Builder and that URL is used, by default, by any UX components within the app... including pre-computed child components. If you have a complex server setup then you can use the Dynamic features of the Callback URL.

    I wouldn't bother with the MultiView plugin... Alpha has enough trouble with 1 Webview. As well, there's been no activity on that plugin in a year... and about 2 million things have happened to PGB within the last year.
    Last edited by Davidk; 05-03-2018, 06:02 PM.

    Comment


      #3
      Re: Embedded UX Components in PhoneGap apps

      Thanks! I don't know how I missed that page in the documentation.
      And thanks for the DOM information. Seeing the multiple reflows (mostly forced by the code simply asking for information about the window size) competing with the other javascript code every time I switch panels was the thing that got me really motivated to look into this.

      Comment

      Working...
      X