The problem with the current FinkCommander is that I’m trying to interface a Perl program (fink) with python. The only way to do this properly is to call the perl command a bunch and hope that it doesn’t cause your processor usage to spike like no tommorrow. So, the best and most logical thing is to rewrite FinkCommander with CamelBones. This way, I can interact directly with fink’s classes and display them with a cocoa window! The other problem is, I don’t know perl all that well, but then again, I didn’t know pyobjc/objc that well either.

Ever since the initial debate over the coining of the term Open Source in 1998, and with the help of Mozilla, the idea has become a major aspect in application development, distribution, and viewing. With the need of technologies to accomplish these tasks, many version control systems, easy to use documentation, bug tracking, and timeline support tools have been created to manage these open source projects. One of the most well known and, let’s throw modesty to the side, the best tools that can accomplish these tasks is Trac. But alas, Trac has it’s downfall. IT IS IMPOSSIBLE TO INSTALL! Well, I shouldn’t say that, for a novice or a person who doesn’t not have full access control to your web server *like Dreamhost*. First, you have to direct Trac to a mod_python installation *Trac is written in the all mighty Python, a smart choice*, then install an HTML template system, and to top that making sure you have SQLite enabled. A jumble of steps, but totally worth it if you can do it.



For others, there is an alternative. Collaboa is a Wiki, SVN UI, Ticket Manager, and a Mile Stone manager, basically a lighter clone of Trac. This project is written in a much friendlier web framework, Rails. Since the project uses Rails, its written in Ruby, contrary to Trac’s usage of Python. Many other minor changes differentiate the two projects, leaving you with a choice of your own for your Open Source Project.

Programming is by far, a journey. Not like the shoe store, but an actual journey. When working on a new version of PyLauncher, 2.0, I came across a problem. How can I create my own custom NSRunAlertPanel when an error, or exception in Python, has occurred? Behold! There is a solution!

One of the best parts about exceptions are that you can declare what you want to Python to do for each exception that could happen. Let’s look at an example:

#!/usr/local/bin/python2.4
import ofs
import sys
from AppKit import *

I tried to import a module that wasn’t there, and got an error like this:

Traceback (most recent call last):
  File "
“, line 1, in -toplevel-
    import ofs
ImportError: No module named ofs

Whoops! Now, to make this look better or make it easier on people who are novices, you can control what to do if Python encounters this exception:

try:
	import ofs
except ImportError:
	print "Module ofs not found"

Viola! Now, here’s what I wrote to incorporate a custom NSRunAlertPanel if an exception occured:

from AppKit import *
from Foundation import *

try:
	return app(x).launch()
except:
	NSRunAlertPanel("Title of Window", "Message", "Default Button", "Other buttons, can be None if you want", "other stuff or None")

Today’s it folks. If anything new is going to be released by Apple this year, it will be presented here, at the World Wide Developer’s Conference ‘07. The Keynote, will be presented in a little over 2 hours, but sadly, no live Video streaming this year. Instead, sites like MacRumors will have automatic updating picture feed from inside the presentation room here..



I’m not exactly sure what to expect from this year’s Keynote, as they can be so unpredictable, like last year’s. I would hope it’s not concentrated on the iPhone, as that is the least of Apple’s importance. Constant delay’s in Leopard are staining Apple’s record, especially in it’s own tight-nit user group.