From: Lance H. <lh...@ha...> - 2006-06-17 07:59:51
|
Alex, Thanks for the suggestions. I am new to Python and Pythoncard so anything I do will be new to me. As Andy suggested I have started to scratch and itch with an app that I found lacking and want to improve. I am sure you will all get used to me asking questions :-) Thanks Lance Alex Tweedly wrote: > 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 > |