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
Devcon 2020 Goes Virtual! LEARN MORE >

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

How to Protect the Code

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    How to Protect the Code

    Is there a way to protect custom codes used in an application like the Xbasic and Javascript codes? TIA
    Last edited by JetLi; 09-01-2014, 07:34 PM.
    Tags: None
    #2
    Re: How to Protect the Code

    Protect from who? From a browser user looking at the website, or someone you give or sell your application to who has general access to the source? If the later, you cannot generally protect the Javascript but you can commit nearly all of your xbasic to an AEX file. Search on that term.
    Steve Wood
    See my profile on IADN

    Comment

      #3
      Re: How to Protect the Code

      protect from a client who has general access. I see, javascript cant be protected, its good there is an AEX for xbasic, but I think the problem with AEX is that once it is compiled it cant be modified again? please correct me if I am wrong.

      Comment

        #4
        Re: How to Protect the Code

        Originally posted by Steve Wood View Post
        Protect from who? From a browser user looking at the website, or someone you give or sell your application to who has general access to the source? If the later, you cannot generally protect the Javascript but you can commit nearly all of your xbasic to an AEX file. Search on that term.
        By the way Steve, How can we protect the alphatogo web framework. They might copy it, which of course we dont want anybody else to do it!

        Comment

          #5
          Re: How to Protect the Code

          Well the Alphatogo Framework is just a normal Alpha Web application with a few lines of code compiled as aex. You can't stop someone from copying it if they have the full source. But no one can "copy" any Web application just from viewing it in the browser. You can get the html but NO xbasic from just viewing.

          When you compile aex you still have the plain text master that you can edit and recompile. You keep the master and just put the compiled aex in the application.
          Steve Wood
          See my profile on IADN

          Comment

            #6
            Re: How to Protect the Code

            Thanks!

            Comment

              #7
              Re: How to Protect the Code

              Google on "obfuscate javascript". Or, take a look at this site: http://www.kahusecurity.com/2011/bri...ion-technique/

              Of course the problem in Alpha would be is your JavaScript is a single place where you could obfuscate it or is spread all over the place in?

              Comment

                #8
                Re: How to Protect the Code

                In most cases if someone takes your Js code it is of no use because it is only part of a larger entity that they cannot fully obtain. Also, and this is a general comment, not pointed at any one's code in particular, most often no one wants your code.
                Steve Wood
                See my profile on IADN

                Comment

                  #9
                  Re: How to Protect the Code

                  Thanks much! BTW Steve, ALpha is releasing a framework that is very similar to your alphatogo web framework, I know you are aware of that, what could be the advantage of your framework , or what are their similarities? Thanks!

                  Comment

                    #10
                    Re: How to Protect the Code

                    The SaaS Framework is focuses on the needs of multi-tenant SaaS applications and is entirely mobile design. My Framework is more for general applications and as such has many features not in the SaaS Framework. I also have two new versions coming out (October) that have additional features.
                    Steve Wood
                    See my profile on IADN

                    Comment

                      #11
                      Re: How to Protect the Code

                      Originally posted by Steve Wood View Post
                      The SaaS Framework is focuses on the needs of multi-tenant SaaS applications and is entirely mobile design. My Framework is more for general applications and as such has many features not in the SaaS Framework. I also have two new versions coming out (October) that have additional features.
                      Hi Steve, are the two new features available for those who bought your framework? less than a year? Thanks!

                      Comment

                        #12
                        Re: How to Protect the Code

                        Jetson,
                        Yes some deal for recent buyers, in October after the product release. I will also be adding a subscription (just like Alpha) for continuous update options. With Alpha Anywhere being on subscription, it allows me to just keep the Framework current with the latest Alpha Anywhere rather than deal with versions (which is a pain.) Like I am adding the new Alternate Logins (Facebook, etc.) to the Framework as configurable options. In the past when I dealt with versions I would have to say what Alpha version that feature matched up to, now I don't have to do that housekeeping.
                        Steve Wood
                        See my profile on IADN

                        Comment

                        Previous template Next
                        Working...
                        X