I agree with you. I don't want anybody updating my apps. I have gotten several helpful suggestions along the way--which I appreciate very much--and I have been able to include these in my app update. Jeff Weiss
-----Original Message----- From: Kevin Huber [mailto:[email protected]] Sent: Monday, May 09, 2011 4:09 PM To: [email protected] Subject: Re: Package manager update question 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. > >
