The Daydream Blog

Note that this article is intended for developers and may not be of interest to a wider audience

If you, like me, have migrated from using Subversion to Git, you may be missing the ability to link commits with FogBugz cases. I have adapted the Subversion integration post commit hook to work with Git.

It should be noted that integration with repositories hosted on GitHub can be found by clicking on this link, to appropriately enough, GitHub (via a blog post on FogBugz). These instructions are for use with local repositories.

I have simply taken the Subverson integration script, that is available at this link on the FogBugz website and adapted it for use with Git.

To use, follow the instructions below:

• Install Perl in the unlikely situation that it is not already installed on your system
• Install wget. On Mac OS X, you can install via MacPorts by simply typing sudo port install wget in a Terminal window.
• Download post-commit and logBugDataGit.pl by clicking on this link to GitFogBugz.zip
• Unzip the archive and copy the two scripts to your [Path To Project]/.git/hooks directory and make sure they are both executable
• Edit logBugDataGit.pl as follows:
  • If you are using the free FogBugz version set $BUGZ_URL_FINAL to https://yourdomain.fogbugz.com and set $IS_TRIAL to 1.
  • If you host your own FogBugz installation, set $BUGZ_SERVER to your domain without http:// and set $IS_TRIAL to 0.

That’s it, there is not step 6!

In a recent post, Martin Pilkington of M Cubed Software challenged Mac developers to make their apps accessible by the end of 2009. I think this is an excellent suggestion and I will take up the challenge for Differencia.

In Martin’s post and the comments there are some links to great resources to get going with accessibility:

Apple’s Accessibility Developer Page.

Assistive Technology for the Mac Resources

Assistive Ware Videos

At WWDC ’06 I went to the Accessibility session and it was the best Hands-On sesssion I’ve been to at WWDC. The 2006 Session video does not seem to be available any more, but the 2008 session can be found from the link below. It requires access to ADC on iTunes, you may need to log into ADC on iTunes first, or simply look for session 326.

WWDC ’08 – Session 326 – Application Accessibility

The 2006 session had an excellent sample application, Dicey, that takes you through stages of increased accessibility. It can be found here:

Dicey Sample Code

However I would like to extend Martin’s challenge. Most independent Mac software developers sell their products exclusively via the web. Therefore for their software to be fully accessible, Mac developers need to make their websites accessible as well.

Information on this can be found at W3C, the web’s standards body, and elsewhere:

W3C’s Accesibility Initiative

Dive Into Accessibility Guide

I would call on all Mac developers to take up the Mac Accessibility Challenge.

Note this article is intended for developers and may be of limited interest to our wider client base.

Last week saw the release of Cornerstone, a new Subversion GUI client for the Mac from Zennaware. After initial testing, I am quite excited about Cornerstone, as it breaks new ground for Version Control Graphical Clients.

Historically, graphical version control clients have simply put a GUI on top of the command line tools. It is disappointing that there is little or no thought given to the problems that developers want to solve with their source control systems. Developers of these applications seem to completely forget the issues they themselves face.

Cornerstone’s most impressive feature and one that I have discussed extensively in the #macsb IRC channel is it’s timeline. You can easily go forward and back through the history of a file and see changes for each subsequent version. Whilst this falls short of my wishes for a source control timeline, it is a massive step in the right direction.

Cornerstone’s source code diff tool looks great, but still cannot identify when a method has simply moved within a file. If you change the method as well as move it, which is quite common, the changes are not clearly highlighted in Cornerstone, Xcode or any other diff tool I have come across on the Mac. I had already decided that a future version of Differencia will act as a source-code aware diff tool.

Whilst there are a long list of feature requests I have already for Cornerstone, after only a day’s use, it is a huge relief to find that someone is taking source control seriously.

Apple has clearly focused a lot of effort on targeting the iPhone at the enterprise market. A significant amount of emphasis in the iPhone 2.0 update is towards features demanded by existing and potential enterprise clients.

The iPhone will undoubtedly be a success in the enterprise market. Anyone who doubts that is kidding themselves or trying to downplay the iPhone for marketing their own products.

The question is whether success with the iPhone will lead to increased enterprise Mac sales. There has been a long debate as to whether the iPod Halo effect exists. Will there be an Enterprise iPhone Halo effect.

The key factor is that enterprise IT departments will have to purchase Macs and learn Mac development tools to develop custom, internal, iPhone apps. Whilst many enterprises have a small number of Macs in their design, web and media departments, having Macs in their IT departments is much more likely to lead to a wider uptake of Macs.

Although administration and development functions are normally quite separate in enterprise IT departments, administrators are going to make considerably more effort to better integrate Macs into their environment for IT users, than for design or media users. Once IT administrators are confident that they can integrate Macs into their infrastructure, the door is opened for wider scale adoption. With significant misgivings over Vista, readily available Mac VM software and continuing Windows security concerns, removing the biggest barrier to entry – a Mac cynical IT department, will lead to a significant increase in the number of Macs in enterprise.

There is another key user group that will help to drive adoption – gadget hungry executives. As key executives increasingly purchase Macs for their own use, they will demand full access to their corporate infrastructure. Again IT departments will prioritise keeping this user group happy, further weakening barriers to entry.

Combined with the “one” feature of Snow Leopard being better Exchange integration, Apple stands well placed to take advantage of a “perfect storm” of iPhone developers, executive decision makers and a weakened Microsoft to finally make that breach into the enterprise computing market. The question is whether they will listen to enterprise demands for the Mac, in the same way as they have listened to their iPhone demands.

It also opens an opportunity for Mac software developers to develop enterprise class business software, a market segment where the Mac currently suffers. Products like Differencia will hopefully be well placed to help Apple win new business.

There is a meeting scheduled for Scottish based Mac developers attending WWDC. Initial plans are for meeting at the Thirsty Bear on Sunday, 8th June at 6PM. Exact timings may change.

If you are interested, please email david at macmacdev dot com. Further details and updates can be found at the MacMacDev website.

There are already 8-9 attendees, so a healthy number. More the merrier, so please let David know if you would like to come along too.

There is one feature, in all of the apps that I use, that continues to impress me and makes a huge difference to my workflow. CSSEdit from MacRabbit does what it says on the tin – it edits CSS files, that define layout for modern web pages. For initiates, CSS seems like some arcane data file format pre-dating XML, but CSSEdit makes it easy to master.

Selecting a numerical field in CSSEdit such as Margin, Padding or Width, allows you to adjust the positioning of elements on your webpage. The live preview shows your changes immediately.

But the stand out feature is that if you hover your mouse over the selected field, you can use the mouse’s scroll wheel to adjust the value. This makes it phenomenally easy to fine tune the position of elements, to make them pixel perfect.

I primarily use Coda for my web development and although Coda has a built in CSS editor, it just doesn’t compare to CSSEdit. Which is perhaps why Panic, Coda’s creators, wanted to include CSSEdit within Coda, in the same way as they incorporate SubEthaEdit as the text editor in the app. It is a shame the two parties were not able to come to an agreement.

Here’s kudos to MacRabbit for great attention to detail, that makes a huge difference to users. Whilst Mac software developers need to remember the 80-20 rule to deliver, we still need to remember the other 20%. It should only been delayed to deliver the 80%, but still needs to be tackled to make our apps that extra bit special for our users.