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



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

Simultaneous Developers

  • Filter
  • Time
  • Show
Clear All
new posts

    Simultaneous Developers

    Hi Guys. This question may have been asked but I am not able to find the link on the forum for a more recent post. Is it possible for two developers to work simultaneously on the same v11 web application? I have seen older posts advising against it for desktop apps but not addressing web apps. I thought about a dropbox or SugarSync solution but I am concerned that it could corrupt files. I am giving thought to bringing another person on to help speed up development. I would like to work in my office while at the same time dev2 is working in their office but both of us on the same app at the same time. Or at the least a checkout process for a different dev to work on a different file of the same project. Would publishing get crossed up between the two, etc? Does anyone have any experience with this? Thanks - Jeremy
    Last edited by jthornton; 05-05-2012, 06:38 PM.

    Re: Simultaneous Developers

    Developers have been working with stuff like this for decades. Unless the application environment specifically has tools for checking objects in and out, then all that's really needed is some good communication. Generally, the tables side of things will have been worked out and is fairly stable... some changes, but not alot. Any changes can be communicated back and forth. After that you're really just working on different objects. You're not both going to be developing the same grid so there really should be too much effort to keep things in check. Once an object is complete then document it, zip it and send it. You're both trading object back and forth. You both know what the other is working on. Communication and a track list of objects in development, complete etc. should do it.


      Re: Simultaneous Developers

      So in your estimation would a sync solution like dropbox or SugarSync work so long as we are not working on the same components at the same time, but different components within the same application?


        Re: Simultaneous Developers

        I'll say that we used Dropbox successfully for component work for a while, but the aex file, which has many functions in one file, proved really really hard to keep straight. I agree that if you communicate well and make sure you have your functions saved somewhere safe you should be good.


          Re: Simultaneous Developers

          Yup... what Chris said.


            Re: Simultaneous Developers

            Here's how I see the solution. It works but so far my bosses do not agree:

            (1) A single, dedicated Alpha 5 Development Computer, physically secure, connected to Internet behind a firewall.
            (2) Two (maybe three) Alpha 5 persons who act as Remote Developers.
            (3) Via either TeamViewer or MS Remote Desktop, all Developers in (2) remotely connect (via the internet) to the DC in (1).
            (4) All RDs in (2) can Add, Edit, and Publish the A5 web app from the one DC in (1).
            (5) Due care must be taken that RDs do not Edit the same components at the same time.



              Re: Simultaneous Developers

              Thanks. The only problem I see with this solution in my case is that if we are dealing with a desktop OS on the development computer then one would be limited on the remote connection to no more than one user at a time on the same desktop. If we are talking about Remote Desktop and Terminal Services such as Windows Server that might be a different story. Nevertheless, my goal is at least two developers using two copies of Alpha development working on the same project at the same time from a shared folder (even if the other has to work on different components at the same time) either in the same office or two different offices remotely. That is why I am thinking that using a sync service, performing backups of the work, and communicating between the two of us (im, txt msg, etc.) to keep from working on the same component at the same time may be the best solution for us at present. I even thought of making a little database where we would enter the name of the components being worked on with a little check in/checkout box so we would know not to work on that component and on checkin requiring notes about the changes that were made, but that may a bit over the top for now. I am however open to continued suggestions.


                Re: Simultaneous Developers

                So to be clear from others experience, it is my understanding that we can work on the same project, just not the same components (grids, dialogs, etc.) at the same time. Is that correct? I haven't tried it yet out of fear of corruption over time where it works at first and then over time the problems start to show up. Even then backups of bad data are still bad!