From: Alex T. <al...@tw...> - 2006-06-15 23:08:40
|
Andy Todd wrote: > The usual answer is to scratch your own itch. If you're looking to > >improve your knowledge and ability with PythonCard then I'd suggest >starting with a small application that helps you out. For me it was an >address book (which I'm not releasing because it wasn't very good) and >then I moved on to a database query tool which became the dbBrowser sample. > >If you're building something that you want and/or need then it becomes >much more than a learning exercise and you'll be better for the experience. > > Also, it's generally more difficult to learn too many different things at the same time, so try to pick an area where you already know some of the other parts, so it's (mostly) PythonCard that you are learning (and/or Python and/or wxPython). For instance, if you have already written some apps that analyze some data without a GUI - is there some aspect of the data that would benefit from being visualized ? - so you could re-use your knowledge of how to read and handle the data. Or - if you really want some suggestions "out of the blue" - pick some simple game and try that. (e.g. minesweeper - not Chess !!) - do something with a database (I never touch them myself, so have no specific suggestions :-) - spell checker (i.e. a PythonCard front-end to an existing checker) (or a spell checker for PythonCard resource files ??) - extend the findfiles tool to find and replace -- Alex Tweedly http://www.tweedly.net -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.8.4/364 - Release Date: 14/06/2006 |