Re: Candidate next update is now available VS Alpha Five Version 11 Updates = conund
One thing I think needs mentioning here which may not be seen by many advanced users is:
Many of the issues/bugs that appear within the a5 software code itself effect the user that uses the GUI to do much of the heavy lifting.
If you're doing much of the work via hard coding and scripting, you tend to not run into these issues. (not using the GUI to learn by example) What I'm getting at here is the more advanced you are, the less likely you are to be "stymied" by an unknown bug...
On a pertinent note: Having watched ALL the training courses & videos numerous times, (while trying things and taking notes)... I even resolved a problem both of the instructors had encountered and never resolved during their recorded training courses. Through my trials and tribulations I solved it, reported it to Alpha, and even attempted to contact the instructors for their future benefit. (Steve Workings & James Talbott.) ~ Needless to say, I never heard back from either of them. (The bug had something to do with the way a5 resolves/ classifies (enumerates) embedded browse objects because of a scrollbar object in the X-basic explorer as I recall. They couldn't find the objects.) ~ I still have the email somewhere.....
The ideal resolution to all this would be to have Alpha modify their bug reporting service by sending users to a BBS where they could pre-classify & report issues via a drilldown menu symbolic of exactly where in the program they are experiencing the problem. (Along with details explaining exactly what is occurring. ~ A pseudo roadmap representing the actual gui itself where the issue is occurring.)
~Seems to me this approach would benefit both users, and Alpha. (It effectively eliminates Selwyn's bug report inbox.) Of course, the only negative would be that it exposes all the problems. But that's not really a problem, (IMHO) because Alpha does tend to address bugs very quickly with updates & fixes.....
One thing I think needs mentioning here which may not be seen by many advanced users is:
Many of the issues/bugs that appear within the a5 software code itself effect the user that uses the GUI to do much of the heavy lifting.
If you're doing much of the work via hard coding and scripting, you tend to not run into these issues. (not using the GUI to learn by example) What I'm getting at here is the more advanced you are, the less likely you are to be "stymied" by an unknown bug...
Case in point: Last winter, as I finally took the plunge to learn a5 "from the inside out" I continuously ran into frustrations that were presumably "transparent non-issues" by all the advanced users at that time. (Either that, or nobody bothered to report in with bugs.) This took place into May of 2011 for version 10x. The more I do with with hand coded scripting (and the less I rely on the gui & wizards), the less noticeable these problems became. Nevertheless, I had uncovered a bunch of things (that were quickly addressed & fixed) that the "pro's" obviously never encountered. (Because I was working "from the ground up.") ~ Some of these issues (I am quite certain) have been around for years!
During this period, I already had many of the fundamentals "under my belt." With much frustration, it eventually became apparent that a5 internal code was simply not doing what it was supposed to be doing. Had I had access to a BBS where issues were being reported by others, I might have saved much time & frustration. ~I can't help but wonder how many others go through this same experience which leads them to eventually just give up!
During this period, I already had many of the fundamentals "under my belt." With much frustration, it eventually became apparent that a5 internal code was simply not doing what it was supposed to be doing. Had I had access to a BBS where issues were being reported by others, I might have saved much time & frustration. ~I can't help but wonder how many others go through this same experience which leads them to eventually just give up!
On a pertinent note: Having watched ALL the training courses & videos numerous times, (while trying things and taking notes)... I even resolved a problem both of the instructors had encountered and never resolved during their recorded training courses. Through my trials and tribulations I solved it, reported it to Alpha, and even attempted to contact the instructors for their future benefit. (Steve Workings & James Talbott.) ~ Needless to say, I never heard back from either of them. (The bug had something to do with the way a5 resolves/ classifies (enumerates) embedded browse objects because of a scrollbar object in the X-basic explorer as I recall. They couldn't find the objects.) ~ I still have the email somewhere.....
Here's a situation where even the instructors were "stymied", and it had taken someone "at my level" to uncover the underlying problem. (Obviously, I've come a long way in a short time since then with a5.) Regardless, I have a very lengthy background in working with technology, programming, and computers. But it's not presently my primary income. It's more of a hobby for me right now. I'm hoping it may turn into more, but I have a lot of other seasonal obligations.)
The ideal resolution to all this would be to have Alpha modify their bug reporting service by sending users to a BBS where they could pre-classify & report issues via a drilldown menu symbolic of exactly where in the program they are experiencing the problem. (Along with details explaining exactly what is occurring. ~ A pseudo roadmap representing the actual gui itself where the issue is occurring.)
~Seems to me this approach would benefit both users, and Alpha. (It effectively eliminates Selwyn's bug report inbox.) Of course, the only negative would be that it exposes all the problems. But that's not really a problem, (IMHO) because Alpha does tend to address bugs very quickly with updates & fixes.....
Comment