From: Dan S. <py...@da...> - 2002-05-28 18:29:31
|
As Chief Scribe and Tablet Keeper of the PythonCard team, I'm happy with the progress we've made recently on documentation. We now have walkthroughs that take you step by step through basics, creating an app from scratch, and adding a child window. The shell and the resourceEditor (where you do most of your work) are now reasonably thoroughly documented. The walkthroughs constitute a resourceEditor tutorial in addition to serving other purposes. We have decent installation instructions that will get better as the install process streamlines. We have a ton of great examples to learn and copy from and some wonderful tools that help you use those samples (hint: if you haven't worked with findFiles in the samples directory yet, you need to get to know it really well). So what's next? What would you, the folks who are going to make the world-class apps that put PythonCard on the map, like to see documented next? We have lots of possibilities and we'll eventually do them all. But left to my own devices, I work on the stuff I need to build my projects and that isn't always in the best interest of the community. If you have no idea what you want next, that's cool. If you need some idea-starters, here are some of the possibilities. Let us know what is most important to your work: * Component reference documenting all of the components built into PythonCard * Framework reference documenting all of the API interaction stuff, which includes components but other things as well * Samples reference gathering together in one place information about all the samples: what they do, what they use, what you can learn, etc. * More samples (please indicate what specific techniques or components you'd like to see better explained or demonstrated) * Multi-window application walk-through incorporating more complex controls, command events, and menu complexity (may turn out to be more than one walk-through or a multi-stage walk-through) I may have overlooked something terribly obvious, so let this list be a group of talking points rather than an exhaustive to-do list. |