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

Multiple programmers working on same project.

Collapse
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #16
    Re: Multiple programmers working on same project.

    Originally posted by glenschild View Post
    I have been looking at github. It seems to have the potential BUT needs to be set up carefully. If you have someone working on a specific area/module they can do so without affecting the main code and it can be integrated when finished/approved. Still working through the nuances to see if it really will work.
    Glen, how did your experiment with Github as source control for Alpha work out? Can you provide more insight on the potential issues that need to be addressed to successfully implement this? We need a source and versioning control solution for multiple programmers working on an Alpha project from different locations.
    Brad Weaver, President
    ComputerAid International
    Ottawa ON Canada
    Versailles KY USA
    www.compuaid.com

    Comment

      #17
      Re: Multiple programmers working on same project.

      Originally posted by compuaid View Post
      Glen, how did your experiment with Github as source control for Alpha work out? Can you provide more insight on the potential issues that need to be addressed to successfully implement this? We need a source and versioning control solution for multiple programmers working on an Alpha project from different locations.
      Hi Brad

      Not very well! Decided it is not yet possible to use github with Alpha for this purpose. Problem is (among others) that every time you open the developer the .alb/.alm/.alx files are updated even if you are only working on a webproject. Immediately this creates conflict issues, ie you cannot check out a component without these files (or I have not figured out a way) which is not only a shame but if this could be sorted for me it would be a real game changer!.

      For now I am using dropbox which provides a way of working (not full control but...) basically a dropbox folder shared amongst developers that contains the application. First thing is that as standard practice every application I work on has the "backup on first use each day" flag switched on within Alpha so each developer has to have available the exact same location on their system for the backups eg: "c:/app_backups" . You cannot place this folder in dropbox as the full path will be different to each developer. So if you are first on you get the backup on your system therefore the backup then has to be copied to a shared location (yes on dropbox!)

      The key is that the developers have to talk to each other to make sure that each developer uniquely works on a component. This has to be carefully, and manually, managed.

      I had the opportunity to bid for some work with a truly enterprise level company over here but the inability to use github meant the door was closed pretty quickly.

      I really hope this issue will be addressed in the company development plans.

      Glen
      Glen Schild



      My Blog

      Comment

        #18
        Re: Multiple programmers working on same project.

        Thanks, Glen - that's the issue I've been hitting as well. Moving all the non-binary files back and forth is fine and even the binary files i.e. reports works as long as two developers don't both edit the same report before checking in/out the file, but the ADB/ALX/ALM issue seems insurmountable at present for version control.

        I wonder what would happen if I just did version control on the webprojects subdirectory?

        Each developer would maintain their own copy of the ADB but at least that would allow component updates to be versioned and source controlled.

        Any thoughts since you've been at this longer.

        Brad
        Brad Weaver, President
        ComputerAid International
        Ottawa ON Canada
        Versailles KY USA
        www.compuaid.com

        Comment

          #19
          Re: Multiple programmers working on same project.

          Glen,

          Here's the workaround I've come up with at the moment and it seems to be working. I create my project as normal and store the entire thing in the Master Branch including all ADB, ALM, ALX files. I then create a development branch and add a .gitignore file that ignores *.adb, *.ALM, *.ALX, *.wcp_settings.

          Now when I commit and push changes from one system, the components and manifests get updated in the repository. If I upload a different set of changes from another system for a different component, I'm required to PULL the committed changes first from the other users and merge them and then I can commit my changes. I don't get any conflicts at this point as long as we're all working on different components/reports.

          I'm still testing but it looks like this may allow using Github. I also downloaded and am using TortoiseGIT and GIT 2.14 for Windows GUI and BASH utilities to manage the repositories.
          Brad Weaver, President
          ComputerAid International
          Ottawa ON Canada
          Versailles KY USA
          www.compuaid.com

          Comment

            #20
            Re: Multiple programmers working on same project.

            Originally posted by compuaid View Post
            Glen,

            Here's the workaround I've come up with at the moment and it seems to be working. I create my project as normal and store the entire thing in the Master Branch including all ADB, ALM, ALX files. I then create a development branch and add a .gitignore file that ignores *.adb, *.ALM, *.ALX, *.wcp_settings.

            Now when I commit and push changes from one system, the components and manifests get updated in the repository. If I upload a different set of changes from another system for a different component, I'm required to PULL the committed changes first from the other users and merge them and then I can commit my changes. I don't get any conflicts at this point as long as we're all working on different components/reports.

            I'm still testing but it looks like this may allow using Github. I also downloaded and am using TortoiseGIT and GIT 2.14 for Windows GUI and BASH utilities to manage the repositories.

            I asked same question years ago to Selwyn i )2010 A5 claims Enterprise incl. $$$ is not free no source control it is still not here is a must these days

            Comment

              #21
              Re: Multiple programmers working on same project.

              Originally posted by compuaid View Post
              Glen,

              Here's the workaround I've come up with at the moment and it seems to be working. I create my project as normal and store the entire thing in the Master Branch including all ADB, ALM, ALX files. I then create a development branch and add a .gitignore file that ignores *.adb, *.ALM, *.ALX, *.wcp_settings.

              Now when I commit and push changes from one system, the components and manifests get updated in the repository. If I upload a different set of changes from another system for a different component, I'm required to PULL the committed changes first from the other users and merge them and then I can commit my changes. I don't get any conflicts at this point as long as we're all working on different components/reports.

              I'm still testing but it looks like this may allow using Github. I also downloaded and am using TortoiseGIT and GIT 2.14 for Windows GUI and BASH utilities to manage the repositories.
              Thanks Brad, worth giving it a go.
              Glen Schild



              My Blog

              Comment

              Previous 1 2 template Next
              Working...
              X