From: Steve C. <stn...@xm...> - 2005-06-28 03:31:46
|
On our local python user's group mailing list, I shot my mouth off that PythonCard was great (which it definitely is). Now I've been asked to do a presentation. Curses! In addition to Kevin's "Keeping it simple with PythonCard" ... what would _you_ like to see in a presentation? I don't feel like I can speak with much authority about the internals or in-depth comparisons to other tools; it will be much more focused on the user's perspective. The target audience is a Python UG, with varying levels of expertise. I was thinking of covering the following: * a walk-through of the tutorials (this might drop off, since it'd be duplicating the stuff discussed in the tutorials) * a comparison between a simple application written in PythonCard vs. straight wxPython. * a brief list of 'why choose pythoncard' (hit some of the highpoints of the recent 'who is pythoncard's intended audience' thread). * a brief example of directly using wxPython inside a PythonCard application (anyone have a link to a straightforward example?). -Steve |
From: Andy T. <an...@ha...> - 2005-06-28 11:04:01
|
Steve Christensen wrote: > On our local python user's group mailing list, I shot my mouth off that > PythonCard was great (which it definitely is). Now I've been asked to do > a presentation. Curses! > > In addition to Kevin's "Keeping it simple with PythonCard" ... what > would _you_ like to see in a presentation? I don't feel like I can > speak with much authority about the internals or in-depth comparisons to > other tools; it will be much more focused on the user's perspective. > > The target audience is a Python UG, with varying levels of expertise. > > > I was thinking of covering the following: > > * a walk-through of the tutorials (this might drop off, since it'd be > duplicating the stuff discussed in the tutorials) > > * a comparison between a simple application written in PythonCard vs. > straight wxPython. > > * a brief list of 'why choose pythoncard' (hit some of the highpoints of > the recent 'who is pythoncard's intended audience' thread). > > * a brief example of directly using wxPython inside a PythonCard > application (anyone have a link to a straightforward example?). > > > -Steve > Whenever I've done this kind of thing I've found that interactive demos are the best way to show PythonCard's strengths. Stick to one of the early walkthroughs by Dan Shafer with detours into the tools (resource editor, code editor and runtime shell) and you will soon find that time flies. If you wan't some great material this document by Patrick O'Brien from 2002 is a great resource; http://www.onlamp.com/pub/a/python/2002/07/18/pycrust.html Regards, Andy -- -------------------------------------------------------------------------------- From the desk of Andrew J Todd esq - http://www.halfcooked.com/ |
From: Alex T. <al...@tw...> - 2005-06-28 21:55:55
|
Andy Todd wrote: > Steve Christensen wrote: > >> On our local python user's group mailing list, I shot my mouth off that >> PythonCard was great (which it definitely is). Now I've been asked to do >> a presentation. Curses! >> >> I was thinking of covering the following: >> >> * a walk-through of the tutorials (this might drop off, since it'd be >> duplicating the stuff discussed in the tutorials) >> >> * a comparison between a simple application written in PythonCard vs. >> straight wxPython. >> Remember it's as much the difference in process as the difference in the resulting code that matters. >> * a brief list of 'why choose pythoncard' (hit some of the highpoints of >> the recent 'who is pythoncard's intended audience' thread). >> * a brief example of directly using wxPython inside a PythonCard >> application (anyone have a link to a straightforward example?). >> One aspect of that is using sizers - part of wxPython but not Pythoncard - a good simple example is the FindFiles utility. I'd also mention the ability to customize the built-in components if needed - see the recent example on multicolumn lists. > > Whenever I've done this kind of thing I've found that interactive > demos are the best way to show PythonCard's strengths. Stick to one of > the early walkthroughs by Dan Shafer with detours into the tools > (resource editor, code editor and runtime shell) and you will soon > find that time flies. > > If you wan't some great material this document by Patrick O'Brien from > 2002 is a great resource; > > http://www.onlamp.com/pub/a/python/2002/07/18/pycrust.html > I'd agree 100% with that. Do not underestimate how much of your allotted time it will take to get through even a simple example, given a couple of questions as you go; demonstrations to a mixed audience need to be much slower than if you were just doing it for yourself. -- Alex Tweedly http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.323 / Virus Database: 267.8.2/29 - Release Date: 27/06/2005 |