RE: [Pythoncard-users] How can I help?

[Kevin A. <al...@se...>]

> From: Jeff Griffith
>
> I can't take it anymore.  I'm dying to find a way to become involved.

Excellent. Any and every contribution is good at this point. Got any
specialty areas or particular interests?

> This afternoon I began working on documenting all the widget
> attributes and
> event triggers.  My initial plan was to code a single widget and show in
> very simple terms what the code would look like if you wanted to handle
> events triggered by that widget.

That sounds good. Even unfinished documentation is worth posting and then we
can modify and clean it up.

> While attempting this, I was still pretty unfamiliar with how to build
> python cards.  I spent 15 minutes feeling my way around the applications,
> trying things out within PyCrust.
>
> What happened next I didn't expect.  Within those first 15
> minutes I reached
> that historically elusive "aha" moment.  I was stunned at how intuitive
> programming for pythoncard was.  The Message Watcher window along with the
> Resource Editor get the credit for making it so obvious how to code cards.

Sweet!

> So now I have no desire to document every widget event and attribute.  Its
> just too obvious how everything is put together.

Well everyone has a different aha threshold, but I think most people just
have apprehension about something new, so we just need something to kick
start it for everyone else.

> So here is my question, are there any special requests of the developers.
> Can you think of anything that would be nice to have any ol'
> average joe do?
>
> Documentation, run tests, make graphics, order pizza, mow your lawn?  feed
> the cat?  Anything?!?!

Andy thinks we need a logo, but I don't subscribe to the school of "print
the t-shirts, announce the product, take the orders, design the product..."
;-) If someone ever does a logo, please no SNAKES, I would rather have John
Cleese's bald spot as a logo!

But seriously, we need to do docs, tutorials, screen shots, and lots of
samples stressing the framework to point out what needs to be added,
changed, or just plain thrown out. Just ask lots of questions (there are no
dumb questions at this point), someone will provide answers, then we'll wrap
it up as FAQs and DOCs.

ka