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



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

NOOB Question about Action JavaScript VS JavaScript Functions

  • Filter
  • Time
  • Show
Clear All
new posts

  • NOOB Question about Action JavaScript VS JavaScript Functions

    I have been building an app using Action Javascript, but I have converted many of the routines to raw JavaScript functions, and have moved them to the main "JavaScript Functions" tab in the UX builder.

    Are there any reasons this should not be done? It seems to be a lot easier to stay organized having all of the functions in one place, despite the fact that none of the routines will move as a package with copied controls.


  • #2
    Re: NOOB Question about Action JavaScript VS JavaScript Functions

    Action Javascript is easily changed for whatever options are offered for that Action. Converting an Action to a function sometimes means re-creating the Action just to see what else can be set and then incorporating that into back into your function. Other than this, if there is any specific reason not to convert, I don't know it. Both the functions and the Actions are easily called. Action Javascript actions are also accessible from one place. It takes a few more clicks to get there but not a big deal. You do gain some really nice insight into coding procedures and methods when convertion Actions.


    • #3
      Re: NOOB Question about Action JavaScript VS JavaScript Functions

      Great advice, once again, Thanks Davidk!


      • #4
        Re: NOOB Question about Action JavaScript VS JavaScript Functions

        David, as a bit of an aside, Do you think there is any performance difference between Action JavaScript and the straight JavaScript functions?
        I have always wondered if there is a bunch of wrapping and unwrapping that goes on with Action JavaScript and if that has any performance impact.
        Am interested in your thoughts.



        • #5
          Re: NOOB Question about Action JavaScript VS JavaScript Functions

          If you stick with Action JavaScript you will not have to worry about the "WARNING" issue below, but you may run into the "CAUTION" condition.

          Since the AA designer doesn't say this, I think any discussion on this topic should contain the following warning:
          WARNING: functions declared in the main code section for Grids and UX under the "JavaScript Functions" category are GLOBAL to your application. You must use extreme caution when using this properties page. If you define your JS functions here then you must ensure function names are unique across your application and possibly even unique across multiple instances of this component in a running web app. The recommend way to do this is by prefixing or appending a component placeholder name to your function name. An alternative to using this properties page is to attach your JS functions to the component itself by declaring them as objects of the component in the client-side "onGridInitializeEvent" section.

          CAUTION: In some coding practices, calling your functions using either of the above recommended methods will work not work and you will have no choice but to declare your functions globally in your application, preferably under the primary component that forms the menu system of your application.

          To see a demonstration of the issue, download this zip file and unzip the components into one of the sample project workspaces or your own empty workspace. Run the "zUXMAIN" component in working preview. Click the first button and when its tab opens up click the button inside it. You will get a message saying which UX's function definition was called. Do this for the second and third buttons. All seems okay. Now go back to the first or second tab and click the button that's inside the tabbed window to see which UX's function gets called. You will see that only the last loaded UX's function gets called, no matter which UX tab you are in.

          This sample does NOT demonstrate the cautionary statement above, but I can tell you that you will find places in the alpha designer where you need to enter a javascript function name and the web server has no way of accepting placeholders for the function name and you will have to use hard-coded global function names. The global functions have to be coded very carefully to not assume anything about what component they are running in, they will have to be able to work by receiving some sort of pointer to the element or component that called them.


          • #6
            Re: NOOB Question about Action JavaScript VS JavaScript Functions

            You can run js directly, call a function, call Action Javascript, or use .runAction() to call an Action. I doubt you'd ever notice a response difference between the 4. A published page gets all parsed out and rendered.
            Last edited by Davidk; 10-05-2016, 05:59 PM.