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

Publishing to the windows store?

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

    Publishing to the windows store?

    I posted a few days ago regarding using phonegap builds to publish to the microsoft store, and have actually made some headway into this. I rebuilt the phonegap app using cordovas CLI, which gave me a solution project I can directly open in visual studio, and then use visual studio to package and send it to the store. So at least thats taken care of. However, this has spawned a slew of new problems, and was wondering if anyone could assist in figuring these out. I'm starting to believe that these problems are due to the way alpha builds apps, and I'm not entirely sure of how this can be (IF it can be) fixed...I'm getting the following...

    Code:
    File \\?\C:\Program Files\WindowsApps\Test_1.1.0.0_x64__91p0szbevdeze\www\javascript\A5jQueryWithUI.js has JavaScript syntax or other problems.
    File \\?\C:\Program Files\WindowsApps\Test_1.1.0.0_x64__91p0szbevdeze\www\javascript\a5_url.js has JavaScript syntax or other problems.
    File \\?\C:\Program Files\WindowsApps\Test_1.1.0.0_x64__91p0szbevdeze\www\javascript\a5.js has JavaScript syntax or other problems.
    File \\?\C:\Program Files\WindowsApps\Test_1.1.0.0_x64__91p0szbevdeze\www\css\iOS7\style.js has JavaScript syntax or other problems.
    File \\?\C:\Program Files\WindowsApps\Test_1.1.0.0_x64__91p0szbevdeze\www\css\Alpha\style.js has JavaScript syntax or other problems.
    File \\?\C:\Program Files\WindowsApps\Test_1.1.0.0_x64__91p0szbevdeze\www\css\A5System\Vista\theme.js has JavaScript syntax or other problems.
    File \\?\C:\Program Files\WindowsApps\Test_1.1.0.0_x64__91p0szbevdeze\www\css\A5System\default\theme.js has JavaScript syntax or other problems.
    File \\?\C:\Program Files\WindowsApps\Test_1.1.0.0_x64__91p0szbevdeze\www\cordova-js-src\platform.js has JavaScript syntax or other problems.
    File \\?\C:\Program Files\WindowsApps\Test_1.1.0.0_x64__91p0szbevdeze\www\cordova-js-src\exec.js has JavaScript syntax or other problems.
    File \\?\C:\Program Files\WindowsApps\Test_1.1.0.0_x64__91p0szbevdeze\www\cordova-js-src\confighelper.js has JavaScript syntax or other problems.
    I also have a lot of errors from A5System files, saying these aren't properly UTF-8 Encoded. Granted, these I could probably fix if I opened and resaved as UTF-8 Encoded..?


    Thanks in advance guys!

    #2
    Re: Publishing to the windows store?

    Originally posted by jjedrasik View Post

    I also have a lot of errors from A5System files, saying these aren't properly UTF-8 Encoded. Granted, these I could probably fix if I opened and resaved as UTF-8 Encoded..?


    Thanks in advance guys!
    Resaving ANSI file in UTF-8 format will not solve real problems. The problem is how Alpha handles files.


    Every file you save in Alpha is saved in ANSI encoded. So for example in UX if you write text to div and save it result is ANSI text. This means that nice feature in Alpha like UX JSON templates or if you need to write any text in any place in UX are useless if you need to have utf-8 full character set. Saving file breaks your text. Unfortunately the problem goes deeper. If you need to use any Alphas built in text manipulation functions like Upper Trim or for example search functions the end result is disaster with utf-8 text. Alpha has helpers functions but they do not solve problems. Problems continues when you want to control/manipulate utf-8 full character set user inputs.

    But data from databases are utf-8 in Alpha. Why? Because utf-8 is de facto in databases. Utf-8 is also de facto in Web and Mobile today but not in Alpha. ANSI rules. <meta charset="utf-8" /> -tag in page does not solve problem if the page is still saved in ANSI encoded. You can read from release notes what has happened with utf-8 support in AA12 during 4-5 years.

    Comment


      #3
      Re: Publishing to the windows store?

      Originally posted by kkfin View Post
      Resaving ANSI file in UTF-8 format will not solve real problems. The problem is how Alpha handles files.


      Every file you save in Alpha is saved in ANSI encoded. So for example in UX if you write text to div and save it result is ANSI text. This means that nice feature in Alpha like UX JSON templates or if you need to write any text in any place in UX are useless if you need to have utf-8 full character set. Saving file breaks your text. Unfortunately the problem goes deeper. If you need to use any Alphas built in text manipulation functions like Upper Trim or for example search functions the end result is disaster with utf-8 text. Alpha has helpers functions but they do not solve problems. Problems continues when you want to control/manipulate utf-8 full character set user inputs.

      But data from databases are utf-8 in Alpha. Why? Because utf-8 is de facto in databases. Utf-8 is also de facto in Web and Mobile today but not in Alpha. ANSI rules. <meta charset="utf-8" /> -tag in page does not solve problem if the page is still saved in ANSI encoded. You can read from release notes what has happened with utf-8 support in AA12 during 4-5 years.
      Hm...I was hoping that wouldn't the case. Is there any work around that would allow me to still use alpha and overcome this issue? The MS store seems to require that everything is UTF-8 encoded.

      Comment


        #4
        Re: Publishing to the windows store?

        Originally posted by jjedrasik View Post
        Hm...I was hoping that wouldn't the case. Is there any work around that would allow me to still use alpha and overcome this issue? The MS store seems to require that everything is UTF-8 encoded.
        There is no work around for this problem.
        I think 99% of Alpha users do not need real utf-8 support so nothing will happen. I think major of them do not even undrestand this is a problem in Alpha.

        Comment


          #5
          Re: Publishing to the windows store?

          Originally posted by kkfin View Post
          There is no work around for this problem.
          I think 99% of Alpha users do not need real utf-8 support so nothing will happen. I think major of them do not even undrestand this is a problem in Alpha.
          So basically...if the MS store needs its files encoded with utf-8, I'm outta luck entirely when it comes to using Alpha for this?

          Comment

          Working...
          X