Friday, 10 May 2002

Hot Off the Presses PythonCard is a GUI construction kit for building cross-platform desktop applications on Windows, Mac OS X, and Linux. Release 0.6.6 includes 30 sample applications, new additions include a source code editor and a sample for creating flat file databases. This release also supports the new wxPython 2.3.3 preview for Mac OS X. All the information you need about PythonCard can be found on the project web page at: http://pythoncard.sourceforge.net/ The installation instructions and walkthroughs are available on the main documentation page: http://pythoncard.sourceforge.net/documentation.html You can download the latest release at: http://sourceforge.net/project/showfiles.php?group_id=19015 For a list of some of the samples that have been built with PythonCard and screenshots of them in action go to: http://pythoncard.sourceforge.net/samples.html A description of each sample is included in the readme.txt file in each sample directory. The kind people at SourceForge host the project: http://sourceforge.net/projects/pythoncard/ If you want to get involved the main contact point is the Mailing list: http://lists.sourceforge.net/lists/listinfo/pythoncard-users PythonCard requires Python 2.1.x or later and wxPython 2.3.2.1 or later. wxPython can be downloaded at http://www.wxpython.org/ 4:35:43 PM

Tuesday, 30 April 2002

Kevin has posted a Windows screen shot, Dan has posted a Macintosh one, here is a Linux shot of the Widget sample that ships with PythonCard; How does it look to you? 9:33:30 PM

Thursday, 11 April 2002

On the good news front, I've managed to achieve one of the things on my to do list. I've fixed the distutils support in PythonCard and we can now create source distributions for Windows and *nix as well as a Windows binary installer. Expect to see these when version 0.6.5 ships in the very near future. The down side is that this has resulted in me adding another task to my to do list. I've got to raise a bug reports for a couple of "features" I found when resolving our outstanding packaging issues. I've got workarounds but as a good open source community member it is incumbent on me to report the issues I've found. Hopefully it will help those who follow me, and may even prompt someone to provide a patch to the code. 12:18:53 PM

The PythonCard project now has a Wiki. For those not familiar with the term, try this definition. For anyone averse to hyper-linking just let me say that it is a web site written by its users, a collaborative documentation effort. This will enable anyone to add value to the project without needing to know the intricacies of cvs, or html, and gives us a common repository of useful, up to date information. There is only one drawback so far, because the PythonCard pages are actually part of the wxPyWiki (try saying that after a couple of cleansing ales) there is no way to distinguish between PythonCard entries and wxPython pages. I've started a thread on the mailing list about this but the only two options I can see are that we prefix the PythonCard entries with an identifier (such as "PC") or that we create our own stand alone Wiki. 12:14:17 PM

Monday, 18 February 2002

OK, I'm back, and I'm doing some work. Current highlights include; Fixing distutils for PythonCard. Adding toolbar support to the PythonCard framework Including support for a simple wxGrid in the PythonCard dbBrowser sample Converting the PyForm example from Programming Python 2nd Edition to use wxPython instead of Tkinter. Thats it, there is no more. If you catch me on a mailing list or newsgroup promising to do anything else before I have completed these simple tasks please feel free to chastise me roundly. 3:12:53 PM

Ah work, without it we would all be sane. Today I found myself confronted by a colleague who was of the opinion that we did not need any kind of source code control. My immediate response was one of incredulity and downright anger - "what sort of idiot would think to implement a computer system without source code control", etc. Then I took a step back and looked at the actual situation. The person making this outrageous statement is not a programmer. He is not in IT, he is someone in the finance division of the company I'm working for. He doesn't know the difference source code control and a hole in the road - and he shouldn't have to. That is one of the things his company pays me to worry about. What I should be able to do is explain to him why he can't get instantaneous bug fixes into production for his German subsidiary and why that is a good thing for his bottom line. So, I'm writing a story. I'll post a link when it is finished. 2:31:11 PM

Tuesday, 12 February 2002

Portfolio is a simple, data intensive, application to track the reducing value of my stock market portfolio. If I have but one gift in life, it is to instantly reduce the attraction and value of any instrument on a financial market by buying some of it. To further compound this tale of woe I like to daily remind myself of my reducing nominal value. What this actually means in English is that I like to keep track of the value of my shares. To date I have done this in a spreadsheet. Every day I open up my spreadsheet, I then open up Mozilla and navigate to My Yahoo! I then transpose the share prices from the portfolios section (as provided by Yahoo! Finance) into the spreadsheet and update all of the links on a summary worksheet to produce a single figure showing me how much my investments have lost me. This is a labour intensive process that computers were designed to simplify. Hence this application. I want to be able to specify my shares by exchange. I've got some Australian and some US shares so currency awareness is required. I want to record how much I paid for my shares and keep a record of their value over time. I need to be able to record stock split. I want to have the ability to record dividends, in either cash or 're-investment' shares. I want to automate the acquisition of prices. I'm only really interested in closing prices but I do not want to restrict other people to only one price sample a day. When Kevin posted the announcement of his stockprice SOAP client to the PythonCard mailing list the penny dropped and I realised that I had at my disposal all of the tools necessary to create this application. The storage will be supplied by Oracle, which I have running on Windows2000 on my laptop. The application will be written in PythonCard, it will talk to the database using cx_Oracle and may even use some native wxPython. I should be able to build a working application fairly quickly and easily and then tinker with the storage interface to my hearts content. 2:28:47 PM

Today my topic is persistence in object oriented languages. In a vain attempt to get someone (anyone) to link to this Radio blog I making this category a notepad of my experiments to add persistence to PythonCard. My first task is to build an application that talks to a relational database. Hey, I've done that already. dbBrowser is a sample that ships with PythonCard. Tick one. My second task is to integrate the relational storage with events in the framework. The purpose here is to make the storage as transparent as possible. dbBrowser is read only and doesn't address this issue. The code is modular though, with different modules for the different 'flavours' of database that it talks to. For this step I'm going to stick to a single database and concentrate on keeping the application data model seperate from the persistence mechanism. In other words, if I do this correctly you should be able to swap out the database and replace it with another without changing any of the application code, as well as using the persistence mechanism with any PythonCard application. Of course, if I do it really well you should be able to replace the relational database with any other form of storage, in particular ZODB or shelve. I'm leaving them out of it until I have a working model with a relational database. I'm also leaving them alone for now because other people are working on object storage in PythonCard. Hopefully we will all progress together and be able to join our efforts in the near future. For step two I will need to build another application. Luckily, I've got one in mind. I've even got a relational data model to go with it. In my next post I'll try and explain my sample application. 1:07:03 PM

© Copyright 2002 Andy Todd.