Aaron pointed out that App Central is intended for distribution more than collaboration. In fact, what we're talking about now is version control; and systems exist for that, Source Forge being just one. Version control systems have ways of handling simultaneous code updates from multiple people, management of permissions for who can read/write versus just read code, etc.
I think it would be handy for App Central to allow multiple "committers," as we call them in version control lingo; but I can certainly understand GW's not wanting to get into the business of managing everyone's development cycle. For one thing, they'd either have to pick one or more existing software packages to support or become their own unique brand of something that already comes in plenty of flavors. One might think, as I did earlier today, that all GW would have to do would be to allow uploads from any number of pre-authorized people to an author's project. But considering that all uploads have version numbers and that these would have to sync across all contributors to one project, the plot thickens enough to make it difficult to make App Central handle this problem without in effect becoming a source code repository and version control server at the same time. Just my thoughts. On Mon, May 09, 2011 at 05:09:10PM -0400, Kevin Huber wrote: Hi: I am not quite sure if I understand what you guys are talkingg about, here, but the way I read it is that you would like the ability to update each other's apps. Personally, I would think that would lead to mass confusion. For instance, suppose I was to update someone's app, and therefore, I would have to change some of their code. Then a third person wants to add something else, and so on. The author may find that his or her script no longer does what he or she intended, or he might just need to update it to work with the latest version of Window-eyes. He is going to have a difficult time following all the new code that has been put into his script by two or three other scripters. If a scripter feels that some changes should be made to someone elses script to make it work more efficeiently, he can contact the script author. This is Only my opinion, of course, but I think it is worth pondering.. Kevin Huber On 5/9/11, Aaron Smith <[email protected]> wrote: > On 5/9/2011 11:47 AM, Jared Wright wrote: >> Since you mentioned it, I still think one to one ties between apps and >> authors is a flaw. These should be able to be one to many relationships. > Can you expound on this a bit? As you know, there are several of us here > who do Window-Eyes app development, and we have one GW Micro account on > AC. Each of us know how to log in and update packages. IOW, we > collaborate. Right? > > Aaron > > -- > Aaron Smith > Web Development * App Development * Product Support Specialist > GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825 > 260-489-3671 * gwmicro.com > > To insure that you receive proper support, please include all past > correspondence (where applicable), and any relevant information > pertinent to your situation when submitting a problem report to the GW > Micro Technical Support Team. > > -- Doug Lee, Senior Accessibility Programmer SSB BART Group - Accessibility-on-Demand mailto:[email protected] http://www.ssbbartgroup.com "While they were saying among themselves it cannot be done, it was done." --Helen Keller
