From: Jeff G. <jgr...@hb...> - 2001-08-30 02:16:27
|
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 |