This release fixes a mistake I made in the GUI RPC calls to get the core client status.

I’ve also added Sparkle to do software updates. So from now on BMB2 will (optionally) notify you when new updates are available and allow you to download them.

In Snow Leopard Apple added additional restrictions on apps running with setuid (which both BOINC Manager and BOINCMenubar 2 did). So now I don’t install BMB2 with setuid and as a result have gotten rid of the installer altogether (that was the only reason BMB2 needed it). This time just copy BOINCMenubar 2 to the Applications folder. For the next update Sparkle will automatically put BMB2 in the correct place.

What this also means is that non-admin users will need to enter the BOINC GUI password to allow BMB2 to communicate with BONC running on the local machine. This is different from the current BOINC Manager which requires you to add the non-admin users to a special group for them to have access.

I have a fair bit of free time at the moment so hopefully updates will happen more than once every 5 months. :)

Also, I have added a popup menu to the BOINC preferences that makes it easier to change the host you are viewing/editing. This way you don’t have to go to the menu and switch the host there to see it’s preferences.

I have also added a crash reporter, the open source FeedbackReporter.

Apple creates and collects crash reports but does not send them to the developer. The next time BOINCMenubar is run after a crash it will ask you to send in the report. You can add a comment describing what you were trying to do when it crashed and you can look at the information that will be sent (open the details section).

Sending the report is not mandatory, but these reports will help me to improve BOINCMenubar.
If BOINCMenubar has crashed anytime in the past then the first time you run this version it will ask you to send in the report. After that it will only ask when there is a more recent crash.

Apple creates and collects crash reports but does not send them to the developer. The next time BOINCMenubar is run after a crash it will ask you to send in the report. You can add a comment describing what you were trying to do when it crashed and you can look at the information that will be sent (open the details section).

If BOINCMenubar has crashed anytime in the past then the first time you run this version it will ask you to send in the report. After that it will only ask when there is a more recent crash.

Sending the report is not mandatory, but these reports will help me to improve BOINCMenubar.

If you have found any other situations that BOINCMenubar 2 crashes please let me know.

I don’t have any forums or other feedback methods set up right now so if you are having any problems or have any suggestions then send me an email and I’ll get on it (bugs have priority).

I just released a minor update that fixes a few bugs. At this point I have fixed all of the bugs that I am aware of.

My current ideas/plans for 0.2.x:

• Add a “Always Connected” option to hosts. Then the Growl notifications will include all you your hosts instead of just the current one in the menu.
• A “All Connected Hosts” item in the Host submenu that will total all the projects and tasks for all of your hosts and show that in the menu.
• An activity window that shows the running active tasks. Probably two modes, one that that shows all the running tasks at once, and the second shows one task at a time and the display scrolls up to show the next one every few seconds (useful for the All Connected Hosts option above because there may be a large number of tasks running).

Do you have any more ideas?