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

Difference Between Developer Preview Browser Versions And Installed Versions

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

    Difference Between Developer Preview Browser Versions And Installed Versions

    This is just an observation, but when I run the following bowser.js code in the developer it returns different browser versions than the actual browser versions installed on the development machine.
    Code:
    {dialog.Object}.setValue('Result','Browser is '  + bowser.name + ' ' + bowser.version);
    In Working Preview and Live Preview, it returns IE version 7. Running in the browser it returns the actual installed browser version 11.

    LivePreviewIE.png BrowserIE.png

    Same thing with Chrome, the versions don't match.


    Wondering if this is a limitation of bowser.js inside Alpha or is there really a version difference? Version 7 versus version 11 is huge. Or I could be doing this wrong.
    Attached a tiny sample component if anyone wants to take a look.
    Attached Files
    Last edited by iRadiate; 08-27-2019, 03:12 PM.
    Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

    #2
    Re: Difference Between Developer Preview Browser Versions And Installed Versions

    Doesn't look like a limitation of the JS code. What you see is the internal version of chrome/IE within Alpha's IDE (if I'm not mistaken).

    I almost never use live/working preview during development. I always publish locally and have my app up on a second monitor to see progress/changes. What I get in working/live preview is sometimes not what I experience in an actual browser. I know Alpha will probably say it's the same but that hasn't been my experience.
    Mike Brown - Contact Me
    Programmatic Technologies, LLC
    Programmatic-Technologies.com
    Independent Developer & Consultant​​

    Comment


      #3
      Re: Difference Between Developer Preview Browser Versions And Installed Versions

      Originally posted by mikeallenbrown View Post
      Doesn't look like a limitation of the JS code. What you see is the internal version of chrome/IE within Alpha's IDE (if I'm not mistaken).

      I almost never use live/working preview during development. I always publish locally and have my app up on a second monitor to see progress/changes. What I get in working/live preview is sometimes not what I experience in an actual browser. I know Alpha will probably say it's the same but that hasn't been my experience.
      Kind of what I thought. That's been my experience as well Mike. Though I do use the working/live preview very frequently.
      Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

      Comment


        #4
        Re: Difference Between Developer Preview Browser Versions And Installed Versions

        I usually do the live/working preview alot when I developing the layout itself, then edit the styles after I publish it in dev tools so I would say its a mix for me. final testing is always done via an actual published component then I add it to the final product and test again.
        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


          #5
          Re: Difference Between Developer Preview Browser Versions And Installed Versions

          Originally posted by mikeallenbrown View Post
          I know Alpha will probably say it's the same but that hasn't been my experience.
          There is no such claim. They are not a full browser environment and have their limitations. https://documentation.alphasoftware....g%20components
          Alpha Anywhere latest pre-release

          Comment


            #6
            Re: Difference Between Developer Preview Browser Versions And Installed Versions

            I basically do not use components and Alphas built in IDE I just use for pure xbasic when needed. Why that is long story.

            But I use Alphas built in development server for testing and actually I have realtime-live development environment. So I do not have to publish anything when I develop. Everything is realtime: HTML, javascipt and xbasic browser output and all with Alpha development server. You can check here an gif I made. Note also that the encoding of first.a5w page is utf-8 not ansi like in Alpha. The utf-8 means that for Alpha server foreign characters are not a problem anymore.
            Last edited by kkfin; 09-05-2019, 02:39 PM. Reason: new gif

            Comment

            Working...
            X