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

Version Control Organization - Alpha Anywhere

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

  • Version Control Organization - Alpha Anywhere

    We are just moving to Alpha Anywhere to begin our mobile project and Im currently looking into how we organize ourselves within our version control system in regards to Alpha. For now, we only have a single developer working on the project, so its pretty easy to manage, but it wont stay that way for long. How do others organize the detail of an Alpha Anywhere project? Is it reasonable to be able to store the components of a project separately. For instance, what we currently do is we have each component we check out that gets placed into our development environment. I would then load the development tool, make whatever changes, then check the component back in. Is this something that can be done using the current structure of Alpha Anywhere or am I misunderstanding.

    Just to add some additional detail here. I currently have a project called "Tutorial", which has its own directory and within it has a Tutorial.WebProjects directory, with a Default.WebProjects directory. Within it, I can see my components (I have a grid component and a ux component that I built previously) as well as the settings for the project (project.settings), and a few other files (_compiled and _manifest files).

    I'd like to be able to store in version control in such a way where if I needed to, I could reconstruct the project from version control, if I had to, without checking in the entire project as an individual object (think zipped).

    Thanks in advance. Still new to Alpha and am pretty excited by its possibilities.

    3-19-2015 10-32-30 AM.jpg

  • #2
    Re: Version Control Organization - Alpha Anywhere

    Tim,
    Version control been discussed on alpha developers conference.
    Check this link http://www.alphasoftware.com/conf2014/
    and you will find Robin Bennett's Version Control and Automatic Updates (Customer Showcase) VIDEO.

    Hope this will give you the road to set your multiple developers environment with version control.

    Let me know your progress.

    Good luck!
    Eddie
    {

    Comment


    • #3
      Re: Version Control Organization - Alpha Anywhere

      Thanks for the response, Eddie. That did help some. Perhaps you could help me clarify a couple of things I saw in the video. First, it appears as if they check out the software in its entirety or at least do a "get". I have a basic understanding of SVN, but the way I understand it, it appears as if they do a "get", which simply updates the local copy of the project. No problem there. The "check out" process would place an exclusive lock on an object until the change was committed. Typically we do this by component. I noticed in their example, they actually email each other the components that were changed, from the A5Webroot directory. Im assuming these are the compiled components that would be deployed?

      Comment


      • #4
        Re: Version Control Organization - Alpha Anywhere

        YES, the developer, who is in-charge of the changes will send his deployed component files via email with the version control text file to his manger to approve it. The manger then updates his local development files using Tortoise / from SVN server. Once he tested the changes on his local machine, then he will upload the Emailed component files from webroot folder to Amazon server.
        {

        Comment


        • #5
          Re: Version Control Organization - Alpha Anywhere

          They have two version controls, SVN and a text file. SVN for development and a text file for deployed application that will get updated when they upload it to Amazon.
          In your satiation, you need to use SVN for your development to control your AA application files. Multiple developers can work on the same copy of AA project files. After each developer tested his application and new functionality locally, he/she should do "SVN commit" to SVN repository with notes. SVN will keep each developer versions, so that you can see/revert to old version whenever you needed. "SVN update" is a way that a developer GET's updated or latest AA application files from SVN repository.
          Last edited by Ferenju; 03-24-2015, 12:18 PM.
          {

          Comment

          Working...
          X