Categories
Apple bugs

Quick survey on OS X 10.5.7 bug triggers

Update: see OS X 10.5.7 overheats some Macs.

Fellow Mac users, let’s see if we can isolate the triggers of the OS X 10.5.7 blues. If we learn the cause, others may know whether it’s safe for them to update, and we may provide Apple’s engineers with a clue on how to fix the problem in a subsequent update.

Theory 1: Migration Assistant

My affected iMacs have systems that were migrated. That is, when I bought the machines in December 2007, after running them for a while as-is to ensure that they worked properly, I ran Migration Assistant to bring over applications, preferences, network settings, and so on from my previous work machine (a non-Intel white powerbook).

Blah blah

Theory: Possibly OS X 10.5.7 update becomes unstable in the presence of a leftover something migrated from an older system.

Test: If you’re suffering from the 10.5.7 blues, did you run Migration Assistant on the afflicted machine? Did you migrate from a non-Intel machine?

Theory 2: Third-Party Stuff

When something goes wrong with a Macintosh update, a third-party add-on is often the trigger. Here are the add-ons on my sufferin’ iMacs:

Items marked “removed!” were my initial suspects. After the update, iTunes froze on sync. I reckoned the iLike plug-in was to blame, and after removing it, was able to sync again for a while.

Then the Mac froze during an iCal sync, so I removed MenuCalendarClock.

But removing these little guys didn’t fix anything. Soon enough, even without these add-ons, the Macs were freezing during iTunes sync and during MobileMe iCal sync. Eventually they froze on any app, doing anything. (Only to inexplicably resume normal operation again for hours at a time. But enough of this.)

And you? If your Mac is misbehaving after running OS X 10.5.7 update, are any of these add-ons on the machine?

[tags]OSX, bugs, OSX10.5.7, 10.5.7, apple, software, updates[/tags]

Categories
A List Apart Ajax Applications Browsers bugs chrome Design Google Microsoft

A bug in Google Chrome

Between hurricanes and hericanes, you could easily have missed the technology news. Released yesterday in public beta, Google Chrome is a standards-compliant web browser created to erode Microsoft’s browser dominance (i.e. to boost Google’s web dominance) while also rethinking what a browser is and does in the age of web apps and Google’s YouTube.

The new browser is based on Webkit, the advanced-standards-compliant, open source browser engine that powers Apple’s Safari for Mac and PC, but Chrome currently runs only in Windows. You figure that out.

Here are the new browser’s terms of service.

And here’s an important early bug report from Jeremy Jarratt: Google Chrome wrongly displays alternate styles as if active, thus “breaking” websites that use them. (Here’s more about alternate style sheets, from Paul Sowden’s groundbreaking 2001 A List Apart article.)

To compete with Microsoft, the new browser must offer what other browsers do not. The risk inherent in that proposition is a return to proprietary browser code. It is not yet clear to me whether Chrome will compete the wrong way—offering Chrome-only features based on Chrome-only code, thus prompting Microsoft to rethink its commitment to standards—or the right way.

Competing by offering features other browsers do not (easier downloads, streamlined user interface) or by consolidating other browsers’ best features (Opera’s Speed Dial, Firefox’s auto-complete) avoids this risk, as improvements—or at any rate, changes—to the browser’s user interface have no bearing on the display of existing web content.

Competing by supporting web standards ahead of the pack, although not entirely without risk, would also be a reasonable and exciting way to compete. When one browser supports a standard, it goads other browser makers into also supporting it. Because Safari, for instance, supports @font-face, Firefox is not far behind in supporting that CSS spec. @font-face raises font licensing problems, but we’ll discuss those another time. The risk that concerns us here is when a browser supports an emerging specification before it is finalized, thus, essentially, freezing the spec before it is ready. But that is the traditional dance between spec authors and browser makers.

For web standards and web content, we once again live in interesting times. Welcome, Chrome!

[tags]google, chrome, googlechrome, beta, software, browsers, standards, webbrowsers, webstandards, bugs, standards-compliant, alternatestyles, alternatecss[/tags]

Categories
CSS Standards Tools

SiteAssist Professional

Released Wednesday, August 27th, SiteAssist Professional creates entire CSS-based websites in minutes. Since that sounds ridiculous and impossible, I’ll say it again: the product creates websites in minutes, with clean markup, and nicely optimized CSS.

The software package includes 14 designs, each with 12 color schemes. You can customize everything and save your own designs. SiteAssist Professional works with Dreamweaver templates and imports from Eric Meyer’s CSS Sculptor and CSS Menu Writer .

While I wouldn’t use SiteAssist Professional to design sites for my clients, I would definitely use it to quickly mock up good-looking, standards-compliant, interactive walk-throughs. It’s also great for pro bono or friend-and-family work—any time you need to create a viable website without spending a ton of time.

The product lists for $199.99 but is available for just $149.99 during a two-week introductory special.

[tags]css, software, tools, siteassist, webassist[/tags]

Categories
Apple bugs iphone software

Maybe that’s why they call them Kodak moments

It was the last day of our daughter’s first year of school. Party time. All the three-year-olds dressed like dolls; teachers relieved and sad; parents misty-eyed, promising to stay in touch over the summer.

Our children have three teachers. One is leaving for graduate school, the second is off to have a child of her own, and the third—a wonderful woman—will have to be taken out of the school in a box.

The teachers stood together for the last time, hugging each other and our children.

Moments like these are once in a lifetime. Fortunately I carry an iPhone. Unfortunately, my iPhone’s camera is once again taking blanks instead of photographs.

For those who have just missed the photographic opportunity of a lifetime because of this unfortunate iPhone bug, here, once again, is the method that will remove the corrupted file and get your iPhone taking photos again:

  1. Sync iPhone. This also creates a backup of the notes and other items that don’t get synchronized anywhere else.
  2. Go to Settings, General, Reset: “Erase All Content and Settings.”
  3. Once complete, reconnect the iPhone to begin syncing with iTunes.
  4. iTunes will ask if you want to sync from backup. Choose not to. Instead, “Set up as new phone.” This sounds scary, but it’s really not. (You don’t lose your phone number or anything. It’s just a dumb, needlessly scary Apple label.)

From resourcesforlife.com, whose solution this is: “You will lose notes, SMS history, and iPhone settings as well as data that is normally synchronized. However, corrupted system files (such as the internal camera roll files) will be replaced with fresh non-corrupted versions and everything should work.”

I didn’t post this to complain about not getting to photograph the last day of our kid’s first year of school. Nor did I post it to take a swipe at Apple for building an amazingly creative, industry-leading product that is, however, a computer, and thus subject to bugs and glitches.

I posted it because every six months or so, when my iPhone’s camera stops working, I forget how to fix it. Now it’s on my website. When the camera starts failing around Christmastime, I’ll know just where to look.

[tags]apple, iphone, camera, software, bug, whitebox, photo, photos, disappearing[/tags]

Categories
Accessibility Adobe Applications architecture client services Code CSS Design development eric meyer Tools Web Design WebAssist work

CSS Menu Writer debuts

Launched today, WebAssist Professional’s CSS Menu Writer™ for Dreamweaver takes the pain out of creating standards-compliant horizontal or vertical navigation menus with nested fly-outs.

I got to spend an hour with the program prior to its release, and was impressed with its flexibility and extreme ease of use. For instance, creating primary and secondary menu levels is as simple as pointing to your files and folders. If the client changes the approved site structure after you’ve already created your page templates, no problem: just drag files and folders to their changed locations and CSS Menu Writer will update your navigation.

The program comes with four horizontal and four vertical menus, each in 12 different color schemes—96 menus to start—with unlimited sub-levels. You can easily create Doug-Bowman-style “sliding doors” effects, as well as doing all the obvious stuff you’d expect to be able to do, like changing menu width, height, margin, and padding; swapping backgrounds and images; and saving custom creations as new presets to reedit or share with colleagues. The program also integrates easily with Eric Meyer’s CSS Sculptor.

CSS Menu Writer costs $99.99, but if you buy before May 27, it’s just $74.99.

[tags]webdesign, tools, software, webassist, css[/tags]