Re: How about a release?
Steve, in his post above, makes many good points. Just to add a few thoughts. The 8600+ (or however many there are) pages of the help file are very good in many ways. Most of the stuff in there is still very relevant. Alpha has 1200-2000(?) functions and they are well documented, as are other features. The release notes are great and very important. But that being said, there is still a problem. The problem is threefold as I see it:
1) Since v8 the new features largely covered in videos and the release notes have not been integrated into the help docs. Sure, one can view the videos (at least the ones that haven't disappeared altogether) and one can read the very useful release notes. But if you need to find something that's in the release notes, and you have no idea that it is in there buried somewhere, good luck.
2) New features are beautifully demonstrated in the videos. But they often are not documented. Many people have a hard time following the videos and applying it to their own applications. The videos are a great way to demo and inspire, but they don't obviate the need for a written description. When the videos disappear from the web, as some have in the past, you're plum out of luck.
3) Tutorials. It's not that Alpha's tutorials are useless. They're not. They have a lot of value. But they don't present one with the point of view an "outsider" or a "beginner" (regardless of skill level) may have, and thus they generally fail as a "walk though" guide. e.g. The web tutorial IS useful, but at the same time it's tough to follow. Peter Wayne's Xbasic for Everyone is a good example of a useful, user friendly "tutorial" that helps solve real-world problems. We need a lot more of that.
The bottom line for Alpha, IMHO, is they need to update and integrate the help files with all the functions and features since v8 has come out. They need to document in written language what the videos demonstrate. Merely listing the release notes in a new form won't cut it. Regurgitating the help files into the WiKi in and of itself will not resolve this fundamental problem that most of us are suffering from. Lack of complete and proper documentation is a hindrance to developers and users, as it is a barrier to potential new sales.
Steve, in his post above, makes many good points. Just to add a few thoughts. The 8600+ (or however many there are) pages of the help file are very good in many ways. Most of the stuff in there is still very relevant. Alpha has 1200-2000(?) functions and they are well documented, as are other features. The release notes are great and very important. But that being said, there is still a problem. The problem is threefold as I see it:
1) Since v8 the new features largely covered in videos and the release notes have not been integrated into the help docs. Sure, one can view the videos (at least the ones that haven't disappeared altogether) and one can read the very useful release notes. But if you need to find something that's in the release notes, and you have no idea that it is in there buried somewhere, good luck.
2) New features are beautifully demonstrated in the videos. But they often are not documented. Many people have a hard time following the videos and applying it to their own applications. The videos are a great way to demo and inspire, but they don't obviate the need for a written description. When the videos disappear from the web, as some have in the past, you're plum out of luck.
3) Tutorials. It's not that Alpha's tutorials are useless. They're not. They have a lot of value. But they don't present one with the point of view an "outsider" or a "beginner" (regardless of skill level) may have, and thus they generally fail as a "walk though" guide. e.g. The web tutorial IS useful, but at the same time it's tough to follow. Peter Wayne's Xbasic for Everyone is a good example of a useful, user friendly "tutorial" that helps solve real-world problems. We need a lot more of that.
The bottom line for Alpha, IMHO, is they need to update and integrate the help files with all the functions and features since v8 has come out. They need to document in written language what the videos demonstrate. Merely listing the release notes in a new form won't cut it. Regurgitating the help files into the WiKi in and of itself will not resolve this fundamental problem that most of us are suffering from. Lack of complete and proper documentation is a hindrance to developers and users, as it is a barrier to potential new sales.
And all with no performance hit thanks to the codeless AJAX. Even I'm impressed.
Comment