[Pythoncard-users] FW: opinions on PythonCard?

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

I sent this reply to Rob Andrews of the Useless Python site today. Useless
Python is at http://www.lowerstandard.com/python/

Rather than make a separate post to the list asking people to post questions
about PythonCard, you should just read the message below and then start
asking questions :)

ka

-----Original Message-----
From: Kevin Altis [mailto:al...@se...]
Sent: Thursday, August 23, 2001 3:46 PM
To: Rob Andrews
Subject: RE: opinions on PythonCard?


> I've bookmarked your homepage and downloaded your last release. Can you
> point to any documentation (however sketchy) available at this point?
> I'm happy to help out any way I can.

The samples are the best source of how-to. I posted a a samples description
before I went to lunch that is also in cvs and will be part of the next
release.

http://www.geocrawler.com/lists/3/SourceForge/14884/0/6467674/

Last week I asked people on the list to start submitting even the most basic
questions, so that I can start putting together docs from a newbie point of
view rather than my warped framework point of view, but we got little on the
list, probably partly because we switched list locations immediately after
that post. Anyway, I'm gonna ask again, then put out my own notes in the
meantime.

There is a brief tutorial.txt in the docs directory, and numerous helpful
bits in the list archives, which I'll try and bring forward for easier
consumption. spec.py in the package directory documents the available
widgets, events, and attributes. You have to look at widget.py to see all
the methods. The easiest way to play around is to start the shell when you
launch a sample. For example, typing:
minimal -s

Other command line options are -p (Property Editor), -m (Message Watcher)
and -l (log).

If you have the shell open, then you can use command-completion to see
attributes and methods of any object.

I hope that gets you started. The biggest help to the project at this point
is probably asking mundane questions to solicit answers, which can then
become the basis for documentation.

ka