pythoncard-users

[Pythoncard-users] How can I help?

[Jeff G. <jgr...@hb...>]

I can't take it anymore.  I'm dying to find a way to become involved.

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.

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.

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

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?!?!

-Jeff Griffith

Just to make it handy, the old link to the assigned tasks
http://groups.yahoo.com/group/pythoncard/message/276

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

[Pythoncard-users] Icon Packs

[Jeff G. <jgr...@hb...>]

I've decided to begin work on 'icon packs' for the pythoncard project. 
If you look through the source code for the wxPython demo, you'll notice
some of the images are embedded in the code.  They use a combination of
zlib and pickle to accomplish this.  I've already started work on a
script that will store images in .py files.  This would allow icons to
be imported into your projects instead of loaded off the filesystem.  

... here is a pretend python session

>>> from icons.gtk import *
>>> saveas_icon
<object wx_image>
>>> open_icon
<object wx_image>

This would also ease the distribution of pythoncards if most all the
deliverables are .py files that py2exe could easily pack.

I'll keep you guys uptodate on its progress.

Thanks
-Jeff Griffith

RE: [Pythoncard-users] Icon Packs

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

Cool.

The Bitmap class in widget.py might have to be refactored to support what
you are working on, but then again maybe not. Bitmap should probably be put
into its own module file along with other bitmap and image manipulation
functions and classes. We can do this as you get closer. Remember that for
the most part the wxPython objects are hidden inside our own classes,
typically they are the _delegate attribute in a class. That will impact
pickling something like a Bitmap, which you probably don't want to do.

The file extension is used to automatically determine the file type right
now.

We can extend the current resource format to support other "globals" such as
what you're describing, so they could be automatically loaded and available
in an image list or dictionary.

ka

> -----Original Message-----
> From: pyt...@li...
> [mailto:pyt...@li...]On Behalf Of Jeff
> Griffith
> Sent: Thursday, August 30, 2001 12:42 PM
> To: pyt...@li...
> Subject: [Pythoncard-users] Icon Packs
>
>
>
> I've decided to begin work on 'icon packs' for the pythoncard project.
> If you look through the source code for the wxPython demo, you'll notice
> some of the images are embedded in the code.  They use a combination of
> zlib and pickle to accomplish this.  I've already started work on a
> script that will store images in .py files.  This would allow icons to
> be imported into your projects instead of loaded off the filesystem.
>
> ... here is a pretend python session
>
> >>> from icons.gtk import *
> >>> saveas_icon
> <object wx_image>
> >>> open_icon
> <object wx_image>
>
> This would also ease the distribution of pythoncards if most all the
> deliverables are .py files that py2exe could easily pack.
>
> I'll keep you guys uptodate on its progress.
>
> Thanks
> -Jeff Griffith