Now, that does make some sense, because Macs don’t by default have a right click button and some people would not otherwise know how to access the right click menus, but there should certainly be a way to turn it off.

Does anyone know how to turn it off?

Update: I figured this one out myself, thank you very much…

The answer? A setting you can reach in Firefox by using the “about:config” function (for all your newbies, that’s type about:config in the Address Box and hit Return/Enter). If you search for “dom”, you will see an entry called “dom.disable_open_click_delay” with a default integer value of, I think, 1000. I changed it to 5000 and now have no problems dragging all sorts of stuff around in Google Calendar. Wonderful!

Another Update: So it appears that I was entirely wrong. The previously mentioned entry in the Firefox config has no effect on the issue I was dealing with. The reason Google Calendar started working was because Google modified their site’s code. Ah well, still looking for a solution for this behavior on Firefox for Mac.

Final Final Update: I just tried this again (holding down the mouse button over a web page in Firefox on Mac) and found that the functionality has either been disabled or completely removed in Firefox 2.0 RC1. Wonderful! Case closed.

Now, on to more substantive matters. There are some major areas in Apple’s OS X OS that need improvement. While Tiger (10.4) was a terrific release, it has only marginally improved through the subsequent point releases (now at the Universal 10.4.4).

Let’s get it started:

1. Safari – Chief amongst the stagnant and dire bunch is Apple’s browser. While rumors have been brewing about a myriad of new features coming in the fruit company’s upcoming Leopard release (10.5), new features are NOT what Safari needs the most. The biggest problems with Safari still lie with the rendering engine itself. Comments from Dave Hyatt and the rest of the WebCore/WebKit team on their blog make it sound like they are convinced the engine is done and are now just tidying up and getting ready for the next gen content rendering stuff. The engine is NOT DONE. Most of us who follow at least some blogs have seen puzzled posts like one from James Rocchi (then the film critic for Netflix) that he could not figure out how to post to his weblog from a film festival’s press center, because they were using macs. Are macs really that different? Do they have keyboards that look different or require fundamentally different skills to use? No. The problem was simply that the WYSIWYG functionality in Movable Type does not work in Safari – the default browser on the Mac. Robert Scoble had the same problem with Wordpress at an Apple Store. So did his son Patrick, though he was using Blogger. In all these cases (and many more), these PC users got very bad impressions of the so-called “ease of use” of the Mac, when it required that they know and remember the HTML link tag to link on their blog posts. This is the sort of problem that should be first on Apple’s list of things to fix in Safari.Why am I so riled about this? Because there is no good explanation. If they’ve already solved this problem and are simply waiting to give us the new rendering engine in Leopard, then that in and of itself is unacceptable and unprecedented. New features? Fine to use to sell a new release. Bug fixes and rendering engine improvements? Bordering on exploitative when used to sell their new release. And in fact, Apple has shown this to be their view as well. When WebCore/Webkit underwent a serious overhaul, they released the upgraded engine inside basically the same Safari as version 1.3 for current users, and that same engine, albeit with many new features in Tiger as Safari 2.0. So it would not seem that they are merely waiting for the next release to bless us faithful customers with these fixes. Which means they are simply not fixing them.There are many other issues with Safari rendering I could talk about. Apple needs to continue to work with banks and e-commerce sites to make sure that they do not lock out Safari users. There is nothing more confusing to my mom than thinking that Safari is the web, until she reaches The Gap and finds that it will not work on her nice white Mac computer. Us techies may be able to abstract the application and its particular compatibility issues away from the computer itself, but normal users don’t. If they cannot reach a website or interact with it succesfully on a Mac using Safari, then they will blame the Mac – not the application.


2. iCal – This one is not nearly as dire as the other, but is still pretty important. Calendering is an area where not much innovation is taking place and where so much innovation needs to happen. Jon Udell talked about this recently on his blog, though he was certainly not the first and will definitely not be the last to have this problem. While at least Microsoft believes they have solved the calendering space for corporations, noone has even really tried to deal with group calendering on the consumer level. That is except Apple. If you’re entire family is on Macs, you can each use iCal and subscribe to each other’s calenders, and things will basically work fine. There is not such a great web story, but then again, Apple has never really gotten the web, so that’s no surprise. What I have been hoping for (and am seeing glimmers of in the Hula project) is an Open Source web calendering initiative that would use any of the standards used by iCal for syncing to interoperate with desktop clients. This would give us the best of both the web and the desktop and once someone wrote a killer Windows client that could handle this (MS has a new Windows Calender in Vista that may play this role) things could really be peachy.So what am I asking Apple to do? Most of what I wrote above does not rely on anything that they may do or not do. Well, I would like them to push forward. While the rest of the pack are simply trying to replicate basic calendering functionality on the web, Apple should be doing what they are really good at – moving the pale a football field further. I’m not a researcher, nor am I a software dev, but I am certain that there are many ways that we can improve upon the basic calender functionality that is contained in every calendering application. I’ve seen no indication that anyone else is working on this – so I really hope Apple is.


3. iChat – Here is where I want Apple to do a bit of following, in contrast to my last point. Microsoft has already started showing off the next generations of MSN Windows Live Messenger. The piece that Apple should have gotten first, and that Microsoft seems to be jumping right into, is the collaboration over IM application. Microsoft is tackling this on two levels: on the consumer level with Windows Live Messenger and on the corporate level with Office Communicator. The fact is that Apple needs to give us a way to better collaborate over iChat with our documents and browsing.

There’s probably some more, but this has gone on long enough, so I’ll cut it off here. I’m staying realistic but here’s hoping Apple will deliver.

Something like this would be really useful on the Mac as well. While Firefox on Mac has been getting steadily better, there are many times when I want to open something specifically in Safari and an extension that passes the URL to Safari would be great. I could Applescript it, but FF does not have AppleScript support, as least not as of yet.

So, any extension devs up to the challenge?

UPDATE: Check the comments for the solution. I checked—it works.

Weird name I know, but one of the coolest things I’ve downloaded in a long while.

Anyone who manages a website knows that you spend quite a lot of time in your FTP client of choice. This is one of those few areas where I simply must have my mac, because the FTP clients out for Windows are absolutely horrible. (well, except for Windows’ built-in FTP in explorer, which is really quite good for basic tasks and puts Apple’s similar efforts to shame) All the Windows clients are a mess of buttons with no labels, and feel like they were designed by someone who couldn’t decide what he loved more: DOS or UNIX. In absolute stark contrast, Fetch has been the mac client ever since ever and it is really quite a nice program. Nowadays, though, with Mac OS X and modern Cocoa software, there are some great options like FTPeel and Interarchy. My personal favorite though, is Panic Software’s Transmit.

Transmit is not only beautifully designed and deceptively simple, but is also incredibly reliable—something of real import when we’re talking about FTP and one’s web site. The main interface looks like this:

As someone who deals quite heavily with images and photos for his web site, I really appreciate Transmit dynamic preview pane, which includes a zoom feature for images as well:

Transmit also has a really well implemented sync feature:

But for me, the absolute kicker is the Edit in External Editor feature. This allows you to specify your external editor (something else of which the mac has a great selection) in the preferences:

Then, when you go to edit a file that is on the server, it downloads it to a temp folder and opens it in your editor of choice. As soon as you make changes and hit save, it re-uploads the file to the server. Beautiful and seamless.

Update: Here’s a video of the process.

If reports are accurate, Mac users have a lot to look forward to in regards to web browsing under Mac OS X for Intel. According to sources, web browsing in general is much faster under Mac OS X for Intel than it is under the shipping version of Mac OS X for PowerPC. Web pages snap to the screen, the same way they do in Internet Explorer running on a new Pentium system, they say.

Steve totally blew it off at the time, but only a few months later iTunes 4.9 with podcasting is here and what?

It’s #1! Guess this wasn’t just the mild-mannered test Steve said it was…

All this would be fine, since the podcast is actually quite good, if only it would be available on Tuesdays! For the last few Tuesdays, the podcast listing does not even update until late Tuesday night or early Wednesday morning, and even then it gets an error when it tries to download. By the time it’s actually available, it’s Wednesday afternoon. So much for New Music Tuesdays…