>>> from PyQt4 import QtCore
Traceback (most recent call last):
  File "", line 1, in 
ImportError: dlopen(/Library/Python/2.6/site-packages/PyQt4/QtCore.so, 2): Symbol not found: _sipQtConnect
  Referenced from: /Library/Python/2.6/site-packages/PyQt4/QtCore.so
  Expected in: flat namespace
 in /Library/Python/2.6/site-packages/PyQt4/QtCore.so

Some quick searching led me to this post, which implied that hacking PyQt’s configure.py file to force the architecture to be 64-bit would do the trick.
So where it says:

for a in sipcfg.arch.split():
    if a == 'i386':
        qmake_archs.append('x86_64')
    elif a == 'x86_64':
        qmake_archs.append('x86_64')
    elif a == 'ppc':
qmake_archs.append('ppc')

Replace qmake_archs.append('x86') with qmake_archs.append('x86_64').
Now PyQt works again.

The Google Map link is helpful to see where your location is relative to the current NWS weather station.

• Download version 1.18 for the Blackberry Curve or similar.
• Download version 1.19 for Blackberry Storm.

“There was a database cluster failure earlier this morning. System admins are working on the issue now. It should be available shortly.”

Ugh. This has been a crazy week for my little Blackberry weather app. The National Weather Service has decided to change the formatting of their current conditions XML file. The original product description (pdf) displays the temperatures as integers, but as of this morning NWS has started pushing temperatures with an additional digit of precision. This causes the temperature in the application icon to overflow its maximum size of three digits. Some users will see “NWS” instead of the temperature and some will see “err.” To be fair, the schema for the current conditions feed  indicates temperature is a decimal type, but I naively treated all values as string data for the sake of simplicity.

I have a fix that will strip the extra digits off of the temperature for display in the application icon. I plan to release this as a new version tonight.

UPDATE 6/1/2009: There’s a problem with the app icon appearing too small on Blackberry Storms.

Version 1.1 of my free Blackberry weather application includes the following upgrades and enhancements:

• Current conditions are displayed as the application’s rollover icon
• Links to nearest NWS radar and forecast discussions
• Links to NWS alert and warning bulletins
• The application no longer blocks when fetching weather
• Added a user preference for the minimum font size
• The location database is stored more efficiently, resulting in a smaller overall application size

This update is available for over-the-air install here.
A build for the Blackberry Storm is available here.

Over-the-air install is here.

Back in August I upgraded my phone to a Blackberry 8330 “Curve” from Verizon. I was disappointed with many of the free weather applications on offer so I decided to write my own that uses data provided by the National Weather Service and Google to display weather information for the United States and most world cities.

The result of this work is NWSClient, a Java app that displays current conditions, forecast weather, and alerts and warnings. I am distributing this application for free under the terms of the Gnu General Public License.

Please download NWSClient and try it out. Documentation and features list are here.

1. Backup your original jEdit.app application bundle (I called mine jEdit.orig.app).
2. Open up jEdit.app (right click and do “Show Package Contents”). Navigate to “Contents” > “Resources” > “Java” and copy the jedit.jar file to your Desktop.
3. Open up /Developer/Applications/Utilities/Jar Bundler.app.
4. Next to the text field that says “Main Class” click the “Choose…” button and navigate to the jedit.jar copy that you just made on the Desktop.
   
5. Make sure “Use Macintosh Menu Bar” is checked and press the “Create Application Button” at the bottom. Call the application “myJedit” or something else that distinguishes it from the original.
6. Open up your new jEdit application bundle (”myJedit.app”) using “Show Package Contents” and navigate to Contents/Mac OS. Inside here you should see a file called “JavaApplicationStub.”
7. Copy “JavaApplicationStub” from your new jEdit bundle (”myJedit”) to the Contents/Mac OS directory in your original jEdit.app bundle.
8. Inside the original Contents/Mac OS directory you should see an alias called “jedit.” Rename this “jedit.bad” or something similar.
9. Go one level up in the jEdit.app bundle to “Contents” and open up the “Info.plist” file. This open up using the Property List Editor (it lives in /Developer/Applications/Utilities).
   
10. Expand the tree and change the ‘CFBundleExecutable’ string from ‘jedit’ to ‘JavaApplicationLauncher’.

That’s it! Close up the jEdit.app bundle and double click on it. jEdit should start normally as it used to, complete with the Mac Menu bar. Additionally, if you’ve installed the jedit shell script for launching jEdit from the terminal that should still work as well.

It’s not the prettiest solution but it keeps me going for now until a better fix is released.

UPDATE:
Someone in the Apple forums pointed out that simply copying the destination of the jEdit.app/Contents/MacOS/jedit symlink, which points to

/System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/MacOS/JavaApplicationStub

back into jEdit.app/Contents/MacOS/jedit (replacing the symlink with a copy) also makes the jEdit application bundle work again. This method has considerably fewer steps than mine.

Apparently this file is functionally the same as the one generated by Jar builder. It seems Java developers went for the symlink method specifically to avoid problems created whenever Apple would go and update Java. With this update the symlink doesn’t seem to work again.