Simply put, IE6 shouldn’t get any hate. Nor should it receive any love, either.

The best thing the web standards community (and any other smart web folk) can do is stop complaining about an ancient browser whose developer waited too long to replace, and just stop supporting it altogether.

One of the benefits of web standards is that our documents are marked up correctly before we reach the presentational stage. One of the benefits of IE6 (et al) is that we can target specific versions using Conditional Comments. The combination of the two means we can still send our content to old browsers, but not have to bother with the presentation, thus saving ourselves hours of needless headaches and frustrations, while not punishing the users of said old browsers by denying them access to our content.

There’s constant discussion about whether or not to continue support for IE6, and the only reason ever given these days in favor of supporting that browser is its market share. That market share is diminishing, and we’ve already reached the second beta of IE8, so let’s start dropping it already. Make the argument against supporting IE6, to your clients, your boss, your team—whoever needs to hear it, keep applying pressure and don’t back down.

It’s time to stop supporting IE6. Period.

This article has very kindly been translated to Serbo-Croatian language by Jovana Milutinovich from Webhostinggeeks.com.

There has been plenty of discussion about the pros and cons of single-line style sheets, and I’ve been including them as an option when teaching CSS management and organization in my Web Design World presentations in Chicago, Seattle, and later this year in Las Vegas (at WebBuilder) and Boston.

It’s a matter of preference

As a fellow Sidebar-ian (Sidebarbarian?) Steve has been trying to convince me to use the single-line approach for a while of course, and Bryan and Jon have also become fans of this formatting style for their own work. Although they are enamored with it, I haven’t taken to it yet, still preferring to write my style sheets using the “normal” indented formatting most of us are used to.

Now, before anyone gets their knickers in a twist about why they love, hate, “can’t live without” or “will die before they try” single-line formatting, let’s just take a step back and remember one thing: it isn’t anything special, just an alternate formatting style that doesn’t affect the way the browser interprets the style sheet one iota. It’s a personal preference—remember that before jumping on or off this particular bandwagon.

Always keep your options open

Now that I’ve got that out of my system, let’s talk practicality: there are indeed benefits to be had when using single-line CSS formatting—for example, I find it can make a difference after a project has been completed, at which point I’m usually more interested in visually scanning a style sheet for the selectors first, and then for a particular property I’m interested in editing. This is where I’ve found single-line formatting can come in handy.

But my editor already does that!

This is the point where some people will start going on about how you could just use Textmate’s “foldings” feature to get the same visual result (without altering your file), or how CSS Edit has a handy list of all the selectors in a column on the left side of its window, or that you could always use your editor’s “find” command and search for the selector you want to edit. Yet while those are all perfectly logical, sane suggestions, they don’t account for flexibility and choice.

Just another way of doing things

Much like Jon Hicks with his harem of web browsers, I tend to be a bit of a “text editor polygamist”, bouncing from Textmate to CSS Edit to Coda to BBEdit to Transmit’s text editor and a host of CLI editors, mostly depending on my mood (though sometimes contextual if I’m at a computer that doesn’t have a particular application—a WindowsXP box with nothing but Notepad, for instance). It’s the times when I’m using an editor that doesn’t have “foldings” or pretty columns of selectors that I start to appreciate single-line CSS when making quick edits, so I’ve started converting style sheets to a “simple” single-line format (without the left-aligned tab blocks to start each rule’s properties) once they are ready to go live.

Patterns fit for a kilt

Editors like Textmate and BBEdit have built-in commands for formatting (the standard, multi-line approach) or compressing (the entire style sheet on one line, ostensibly to reduce file size by stripping white space) CSS, but no way to convert to single-line formatting and Textmate’s “Format CSS Compressed” bundle can format your stylesheet to a single line per-rule, though it’s all squished together, making it difficult to scan due to a lack of whitespace. Converting a style sheet by hand every time would be much too time-consuming to bother with, but that’s where regular expressions come to the rescue.

In Textmate, you can record a macro using each of these regex patterns as a separate step (I’m sure other editors have a similar feature, so please feel free to post details in the comments below). This allowed me to create a “Format CSS Single-line” command, complete with a keyboard shortcut, which enables an easy switch between multi- and single-line formatting.

Unfortunately, as of this writing Textmate macros cannot be exported and shared For those using Textmate, getting the macro is a simple matter of downloading, expanding and double-clicking this file:

• Download the “Format CSS Single-line” Textmate macro » (ZIP, 1KB)

While similar to “Format CSS Compressed”, this macro retains a single blank line where your original contained two or more blank lines (helpful if you group your rules), and adds whitespace that matches my standard formatting preferences (which I find makes it easier to scan quickly). To switch between each formatting style, just run each command in turn (via the Bundles menu or the keyboard shortcuts).

However, that wouldn’t be much use to everyone who doesn’t use Textmate, so here are the respective groups of regex I used for the conversion:

\n{3,}
\n\n

[ \t]+
 
(?m)([;:])\s+
$1

\s*}
 }

\s*{\s*
 { 

[ \t]*,[ \t]*
,

@import(.*?);
@import$1;\n\n

What’s missing

In Textmate and BBEdit I can return to multi-line formatting with a single command, but that might not be as simple in other editors. What I’d love to see is a pair of shell scripts that convert from multi- to single-line and back, and possibly a web-based processor that does the same (paste your style sheet into a textarea, select your formatting, hit “process” and the script produces the result). If anyone would like to take on those tasks, I’ll happily update this post to link to the products of your labor.

And in the end…

If you’ve never tried single-line formatting, this makes it easy to experiment without committing yourself (and I do recommend giving it a try—you may be surprised once you’ve worked with it a few times).

Ultimately, because I can return to multi-line with a single command my primary text editor should I ever feel like it, automating the switch from multi- to single-line is a convenient way to get the benefits of single-line formatting without backing myself or my clients into a formatting corner.

After throwing together a quick little hover/tab widget for my previous article, I thought I’d share how it was made, in case you find a need for it someday.

Bulletproof lists

The widget in question is just a simple unordered list, with each list item containing an anchor and an image—we want the images in this case because I want them to display in my RSS feed and for anyone who can’t (or chooses not to) view the styled version of this site.

Note: Feel free to reference images in the stylesheet rather than inline if that suits your purposes.

See the widget in use in my previous article, or check out this demo.

The code

First, the markup (with URLs truncated to save trees):

  
One 
  
Two 
  
Three 

Simple, uncluttered, uncomplicated.

Next, the CSS:

ul#hover-tab-thingy {
  position:relative;
  padding:0;
  width:500px;
  height:498px; }
#hover-tab-thingy li {
  float:left;
  list-style:none; }
#hover-tab-thingy li a {
  float:left;
  padding:9px 21px;
  background-color:#eee;
  color:#999;
  font-size:9px;
  text-align:center;
  text-transform:uppercase;
  border-right:1px solid #fff; }
#hover-tab-thingy li a:hover {
  background-color:#f60;
  color:#fff; }
li#one a,
li#one a:hover {
  background-color:#e5e5e5;
  color:#555; }
#hover-tab-thingy li a img {
  position:absolute;
  left:0;
  top:30px;
  width:500px;
  height:460px;
  clear:left;
  margin-left:-9999px;
  padding:1px;
  border:3px solid #e5e5e5; }
li#one a img,
#hover-tab-thingy li a:hover img {
  margin-left:0; }
li#two a:hover img,
li#three a:hover img {
  border-color:#f60; }

This is all fairly straightforward, so here are the highlights that may help when duplicating this on your own:

1. The entire idea is that you have tabs that are each associated with content (images in this case) which are made visible when the user hovers over the tab. There are more things you could do with this, but that’s your job, grasshopper.
2. The tabs are floated; the content elements (img in this case) clear the floats.
3. The content elements are set to position:absolute, so they can appear in the same location for each tab. To accomplish this, the ul is set to position:relative (in short: an absolutely positioned element will be positioned relative to its nearest positioned ancestor—see Doug Bowman’s great write up for more), and it’s probably a good idea if the dimensions of your ul (the container for your content) have a lot in common with those of your content elements.
4. IE6 has a problem reverting elements that set display:block on :hover to their original state (e.g. display:none). To counter this, use a negative left margin as the default positioning, and then set margin-left:0; on the hover state, which works in all modern browsers.
5. The width and height is specific to my example (the dimensions of the images I used), ditto for the padding on the tabs and the top positioning on the img elements (to push them below the tabs). Bend them to your will.

Wrap-up

This may be something that you’ll find use for on a regular basis—one of those tiny snippets of reusable “stuff” that you’ll be glad you don’t have to type every time.

“…by normalizing the space between like elements, aligning elements along similar spatial planes, moderately increasing the space between stacked items and paying attention to how elements are framed by negative space, we can get what is, in my opinion, a significantly more attractive Gmail interface.” —Khoi Vinh

This is something I’ve wanted to see for a while in Gmail, and in fact had presented a few examples last year (July 2007) as part of my interview process at Google (I really must write about my series of amazing job interviews last summer, but I’ll leave that for another time). After reading—and commenting—on Khoi’s post, I had intended to publish my variation on Google’s mid-2007 interface, but as the dedication to blogging continues to elude me, this too fell a few pages back in the Moleskine to-do list—until now.

The Setup

I took a slightly different approach than Khoi, though my goals were similar:

• Give all elements more room to breathe
• Make it easier to target navigation and oft-used links
• Normalize alignment of text and other elements
• Do it all without drastically altering the appearance of the interface

That last goal was important and acted as a guide to the rest: I wanted to present improvements that could be made right away without causing a negative reaction among Gmail users.

Rather than adjust the line height of the main message area, I decided to bring as many of the other elements in line with that as I could. You’ll notice spacing improvements within each line however, reclaiming some poorly used horizontal space. Like Khoi, I felt the message lines were a bit crowded, so to give the impression of more room in those lines, I removed the grey horizontal lines between each item and allowed the background color to bleed through (all they need is some separation—further emphasis on those lines just adds weight). The result is that it feels like there’s a bit more space, without actually adding any.

The main navigation lost its underlines (again, removing unnecessary visual weight—the “this is a link” cue is superfluous here) and gained space (matching the baseline of the message list). The “Compose Mail” link got an extra highlight by way of a background; the extra padding makes it the only navigation item that doesn’t align with the baseline, but that also gives it a little more contrast vertically, thus it stands out more without having to scream for attention. Less important text links within the message area were made slightly smaller (but kept their underlines), and “Mark as read” was pulled out of the drop-down menu and given its own button: I had spent a week or so watching people use Gmail before doing this exercise, and that was the second most frequent action users needed (right behind “Delete”) but was hidden in the drop-down.

Finally, all rounded corners were cleaned up a bit, footer text was aligned to the baseline, and the message list was enclosed on the right side (maybe it’s just me, but it’s always bugged me how those lines just run right to the edge).

Reveal Already!

• Before
• After
• After (with baseline)

I’m still happy with how this turned out a year later, and it was well received by the Google interview crew. Compare the before and after images, and you’ll also notice that the improved spacing in this example actually reduces the overall height of the page, allowing two additional message lines to fit in the space of the original.

Both Khoi’s and my realign leave almost all the original elements of the interface intact—this is very important when making changes (even if only suggested ones) to such a popular application, and the same goes for any product, publication or web site that is part of a person’s daily routine.

Whether Gmail incorporates any of these suggestions is out of our hands, but it’s still nice to have the chance to compare.

Note: many changes have already been made to the Gmail interface over the last year, and even in the last few months since Khoi posted his example. Not all are improvements, but at least someone’s making an attempt.

Note: The article itself is full of some solid information and quotes some bright minds—well worth picking up if you get the chance (as is the rest of the issue).

EJS: Please could you tell us a bit about yourself and your work with logos so far?

DR: I’ve always loved logos, and some of my earliest experiments with design were logotypes (I tend to prefer type-driven logos with minimal imagery). I don’t get as many opportunities to design logos for clients as I’d like, but I do a fair amount for friends and personal projects, sometimes for imaginary ideas just as an excuse to design a logo or logotype.

EJS: Which logo (that you’ve designed) are you most proud of and why?

DR: I’m torn between the current logo for SuperfluousBanter and a logo I did a few years ago for a real estate company that by brother was starting. I put most of the work I do into two categories: design for myself, and design for others—so those are my current favorites from each category.

In the case of SuperfluousBanter’s current logo (there have been a few over the years), the “sb” mark on an orange field sporting a lighter spiral (with the counter of the “b” over the center of the spiral) has a nice balance of symmetry and asymmetry at the same time, without getting complicated.

With the logo for the real estate firm, the business name was that of the main partner in the company, so it required a visual mark in addition to the logotype in order to communicate the type of business. Not that it was groundbreaking in any way, but the mark does its job well, without being too complicated—the more basic the shapes, the easier it is to recognize an image at a glance (important for property signage), and the better its reproduction at various high- and low-resolutions. The qualities of the mark that make it my favorite are similar to those of the SuperfluousBanter mark: a combination of symmetry and asymmetry that results in balance (it’s extremely important to have all three), and in this case, the end result was almost exactly what I pictured in my head before even sketching the first rough.

EJS: Can you name an all-time favourite (web-related) logo that someone else has designed? Why do you like it so much?

DR: It’s hard to decide, but I’ll go with Dan Cederholm’s Cork’d logo. I like Dan’s style in general, but the Cork’d logo is just elegant in its own little way (recurring theme: combination of symmetry and asymmetry resulting in an overall balance). I wear the t-shirt so much that I’ve almost worn it out ;)

EJS: What do you consider to be the current trends in web industry logo design? Are they good or bad?

DR: While there are still a lot of “web 2.0” design trends everywhere (not just online, either), in my experience these design trends result almost as much from client demand as from designers imposing those trends on their work. As I said before, I’m a fan of type-driven logos, with simple, straight-forward visual marks to support the type. Aside from the drop-shadows, bevels and other standard design clichés, I don’t think there are any awful trends per se (some people might say there’s been enough rounded type and bright, happy colors, but if a client wants their brand to be ‘friendly’ etc., more often than not it’s the right direction), but I could still do without blatant 3-D or an over abundance of filter effects. And let’s not get into the pros and cons of reflections…

EJS: Where do you get your inspiration from and can you recommend any good places of inspiration or resources (books, websites, designers, etc.)?

DR: I’m constantly searching for new sources of inspiration—my personal preference is to find as much as possible offline rather than use the web. Not only does it give my eyes some needed respite from the glare of the screen, but I find my reactions are different when reading a book, sifting through old album covers, digging through piles of magazines—the tactile experience engages more senses, and that helps get the creative juices flowing for me. As for specific resources, I think it’s useful to have good examples around (for comparison if nothing else), and the Logo Lounge series of books is a good place to start for more recent designs. A similar resource online is LogoPond (though I wouldn’t personally subject in-progress work to public examination like some users of the site). If you can find books about logo design and branding written/printed prior to the mid-1980’s, you’ll find some great examples of how to design marks without going overboard (a simple mark that reproduces well in black after being faxed will likely translate quite nicely to the web).

EJS: How do you approach the logo-designing process? Is there a system (maybe in 6 steps) that you can recommend?

DR: While I don’t have a fixed set of steps in place for any of my work (I like to think it helps avoid patterns and forces me to think from a fresh perspective on every project), I do tend to go about the problem-solving process the same way each time:

• Find out as much as you can about the client/product/organization/person/service that the logo will represent. Without that input, a logo is just some text, lines and color.
• Research other brands in the same market—I used to use this step as motivation to “design a better logo” or “beat the competition” but I feel that was misguided. Now I use it primarily to get a feel for what is already successful, and to know what to avoid visually in order to create something unique.
• Sketch and Play—this step is the most random for me: sometimes I’m sketching with pencil in a Moleskine, other times I’m messing around in Photoshop or Illustrator, and a few times the good ideas have come on the requisite cocktail napkin or in the margins of a magazine. The experimentation is the fun part—it’s not always needed (if you see the final logo in your head the first time inspiration hits, get to a computer as quickly as possible and just draw the thing!), but when you’re waiting for the lightning to strike it’s a good way to try things out.
• Design in black and white until you have your logotype and/or mark, then add color and adjust as needed.
• Once you have something, print it out. A lot. I tend to do most digital logo work in Illustrator so everything is vector and easily printed at various sizes. Print variations in type weight/style, as well as inverted versions of your logotype and mark. Print large versions and paste them to the wall, or lay them out on the floor. Look at them for a few hours, or a day, or a few days—as much time as it takes you to really let things sink in.
• If it’s paid work, don’t deliver final art until receiving final payment. If it’s for a friend, give them a CD over dinner.

EJS: What tools feature in your logo-making process (and how prominently, like mainly Illustrator and only a bit of Photoshop?), and can you name any that people might not know about (i.e: any apps outside of the Adobe family)?

DR: I guess I already answered that for the most part. Illustrator is my primary weapon, though anything that allows vector illustration should be fine (even if you’re designing a logo for a web site—there’s nothing worse than designing a kick-ass logo in Photoshop at 72dpi and then realizing that you have to recreate it from scratch as vector art because the client wants to make t-shirts).

EJS: What problems have you encountered in designing logos and how do you avoid them?

DR: Aside from figuring out the starting point (always a moving target from project to project), clients and their expectations/preferences are the biggest problem. That’s a bigger topic of discussion, but I retain as much creative control as possible, and let my clients know up front that I expect them to trust my opinions. If you’re firm with your client from the beginning, their expectations will fall more closely in line with yours.

EJS: What general tips can you offer for other logo designers out there?

DR: Play. A lot. Look for sources of inspiration that may not seem immediately obvious—if you’re stuck for ideas on a logo for a children’s book, start digging through some heavy metal album covers, or a stack of performance car magazines, or some swimwear catalogs. The contrast can do wonders for your subconscious.

EJS: How would you define a good logo? What elements does it need?

DR: Though I have my own, subjective thoughts on this, I’m sure not many would disagree that a good logo is one that communicates the intended message effectively. Usually that message helps define the brand in an easily digestible way. So a successful logo is one that can represent the brand (whether it’s an individual, a small non-profit organization, or a multi-national corporation).

When it comes to the actual visual elements, I prefer logos that do the above described job without being complicated. Striking the correct balance between typography, color, shapes and symmetry isn’t something that can be quantified—it will be different for every logo. I find that the logos that pique my interest the most are those with some level of balanced asymmetry: if you split a logo down the center of either axis, it should not result in a mirror image. Type is a straightforward way to achieve this, since you can very easily balance the letterforms without creating a mirror image. In fact, you’d have to work very hard to achieve that effect, to the extent that if it was the intended effect, it would likely be a more creative end result (and as such, become a successful exception to the mirror rule), for example the ambigrams of John Langdon.

EJS: What would you consider to be mistakes in logo design, be them your own or made by others?

DR: A level of detail that precludes low-resolution or small-size reproduction, including color and type selection in some cases. This is a potential issue with the preponderance of photorealistic logos that are becoming increasingly popular with software companies, but I’m starting to see it creep into other uses. I also feel like typeface selection is often not given as much careful consideration as it requires. Of course, logos can still be successful without being “perfect” by any one person’s definition.

Many thanks again to Elliot and the editors of .net Magazine.

]]> https://superfluousbanter.org/archives/2008/06/some-thoughts-on-logo-design/feed/ 10 491 https://superfluousbanter.org/archives/2008/02/email-doesnt-scale/ https://superfluousbanter.org/archives/2008/02/email-doesnt-scale/#comments Thu, 28 Feb 2008 00:07:40 +0000 http://superfluousbanter.org/archives/2008/02/email-doesnt-scale/ why it fails for me. That is, until reading Tantek's latest on the subject...]]> I’ve been wanting to write about my problems with email for a while now, but keep coming up short when it comes to explaining exactly why it fails for me. That is, until reading Tantek’s latest on the subject:

“I’m probably responding to less than 1 in 10 emails that are sent directly to me, even fewer of those that are sent to a set of people or a list. The usability of email for me has deteriorated so much that I exclaimed on Twitter recently: EMAIL shall henceforth be known as EFAIL.”

He goes on to explain his thoughts on why point to point communications do not scale, and how emails in general are becoming too bloated (the lack of a singular focus in many emails I receive definitely impacts my likelihood of responding), as well as how 1:many or 1:all mediums are superior to 1:1 methods (e.g. email). This is exactly what I’ve been trying to figure out how to say.

Semi-solutions

Tantek certainly isn’t the first to write about the the problems with email – Mike Davidson’s solution last year was to reduce the length and detail of replies to a specific number of sentences, but that hasn’t allowed me to make a sufficient dent in my inbox.

Similarly, Inbox Zero (a process many of my friends use to keep the noise down) just doesn’t seem to work for me. Plus, having an empty inbox won’t stop people from communicating with me via email when they should be using another medium.

It’s not you, it’s me

Both Inbox Zero and Sentenc.es aim to reduce the impact of the full inbox by making it easier to empty on a regular basis, but for me that doesn’t solve the problem as I see it–it isn’t a matter of finding a way to work around what email has become, it’s just that email is being used improperly, and I’d rather use other methods of communication that are more appropriate to the type and relevance of the message.

How do we fix it?

Email isn’t broken for everyone (or at least, if it is they don’t realize it yet), but I find more people becoming frustrated with email every week. Add the whole SPAM problem into the mix (over the last 6 months, more and more of my valid incoming/outgoing messages are getting caught by SPAM filters than ever) and I just see email continuing its downward spiral.

I’m not sure of the solution – as long as my clients continue to send me emails and expect a response, I’m a bit nervous to tell them to shove it (it’s hard enough to get them to all use Basecamp instead for project communication, let alone stop using a method that still works for them), but perhaps that’s what it will come down to. Tantek’s article ends with a list of suggestions that can serve as a decent starting point, and his Email Reduction project is also worth checking out.

Does email = efail for you? How do you feel about the future of email?

]]> https://superfluousbanter.org/archives/2008/02/email-doesnt-scale/feed/ 6 486 https://superfluousbanter.org/archives/2007/10/pink-for-october/ https://superfluousbanter.org/archives/2007/10/pink-for-october/#comments Tue, 02 Oct 2007 22:17:28 +0000 http://superfluousbanter.org/archives/2007/10/pink-for-october/ October. I'm doing this, along with many other sites, to support Breast Cancer Awareness Month.]]> As you may have noticed (if you’re viewing this site in a standard browser), I’ve ditched orange in favor of pink, and things will stay that way for the rest of October. I’m doing this, along with many other sites, to support Breast Cancer Awareness Month.

For more information on this project (created by Matthew Oliphant), check out the Pink for October site.

]]> https://superfluousbanter.org/archives/2007/10/pink-for-october/feed/ 11 484 https://superfluousbanter.org/archives/2007/09/sidebar-creative-interviewed-by-digital-web/ https://superfluousbanter.org/archives/2007/09/sidebar-creative-interviewed-by-digital-web/#comments Tue, 25 Sep 2007 05:50:20 +0000 http://superfluousbanter.org/archives/2007/09/sidebar-creative-interviewed-by-digital-web/ Matthew Pennell of Digital Web Magazine recently sat down with the boys from Sidebar Creative for a group chat about our little design collective.]]> Matthew Pennell of Digital Web Magazine recently sat down with the boys from Sidebar Creative for a group chat about our little design collective.

We talk about what goes on behind the scenes, our approach to creating web apps (including our first venture, MyMileMarker), and our plans for the future.

Working with Sidebar has been a wonderful experience since we started in January, and this interview offers you a glimpse of our personalities and some insight into why it works.

]]> https://superfluousbanter.org/archives/2007/09/sidebar-creative-interviewed-by-digital-web/feed/ 2 482 https://superfluousbanter.org/archives/2007/09/customize-your-iphone-summerboard/ https://superfluousbanter.org/archives/2007/09/customize-your-iphone-summerboard/#comments Fri, 14 Sep 2007 06:33:03 +0000 http://superfluousbanter.org/archives/2007/09/customize-your-iphone-summerboard/ Update: SummerBoard 2.1+ makes much of this tutorial inaccurate, but the theme instructions still work. I’ll be writing an updated tutorial shortly to reflect the changes and additions.

Note: Before following this tutorial, make sure you have everything you need »

The first tutorial in this series covered using DockSwap to change your iPhone’s Dock background, specifically replacing it with one that matches the Dock on the iPod Touch:

This was fine and dandy until yesterday, when a new version of SummerBoard (an app which allows customization of the iPhone’s SpringBoard, or home screen) was released. This new version supports themes and various other settings, but most importantly it appears to prevent DockSwap from doing its job. Thankfully, we can now take advantage of SummerBoard’s new theme support to set a custom Dock background, home screen wallpaper, or both.

Summer lovin’

First thing’s first: fire up Installer.app on your iPhone and install SummerBoard (the current version as of this writing is 2.0). If you already have DockSwap installed, there’s no reason to uninstall it; it just doesn’t affect any change when you use it. However, if you’d like to save some space, you can go ahead and remove it.

SummerBoard 2.0 offers the following home screen (aka SpringBoard) customization goodness:

• Scrolling application icons
• Scroll Snap (for each row of icons)
• Wallpaper under home screen icons
• Themes (Dock and wallpaper images)
• Mini Dock (which does exactly what it says)

In addition to those main features, there are extra settings which give you additional control over your home screen:

There isn’t much need to describe in detail what each of these settings does, plus it’s much more fun if you just play around with them and see for yourself.

Simple themes

SummerBoard 2.0 includes four themes by default:

• Default (aka how your iPhone shipped)
• Leopard
• Panther
• SummerBoard

Each theme is comprised of three images (pixel dimensions follow each file name):

• Dock.png (320×91)
• MiniDock.png (320×37)
• Wallpaper.png (320×480)

Creating your own custom theme is simply a matter of creating each of those images, placing them in a folder and then copying that folder to the proper location on your iPhone.

Adding a custom theme

There’s really no end to the number of custom themes you can create using an image editor and some free time, so I’ll leave that process to you (after all, this isn’t an image editing tutorial). We will, however, walk through the simple process of transferring a custom theme to your iPhone.

First, we need a custom theme—for this example, I’ve created a theme based on the iPod Touch home screen, complete with plain black wallpaper (in case don’t want your “lock screen” image showing up behind your icons). For those of you who already followed my earlier tutorial on replacing your Dock background (see the Dock screenshot at the beginning of this tutorial), this will allow you to have the same look with SummerBoard 2.0 installed:

• Download the “Touch” theme » (ZIP, 48KB)

After decompressing the archive, you will have a folder named “Touch” that contains the required image files.

Next, connect to your iPhone via SFTP (read the instructions if needed), and navigate into Library/SummerBoard/Themes (the full path is /private/var/root/Library/SummerBoard/Themes), where you’ll see the directories of the four pre-installed themes mentioned earlier. Once there, upload the entire “Touch” folder (its path should be /private/var/root/Library/SummerBoard/Themes/Touch).

Now return to your iPhone’s home screen (press the “Home” button) and launch SMBPrefs, then press “Theme” and select “Touch” (the theme we just uploaded). Press the “Home” button once more to return to your home screen and see the new theme in place, looking something like this:

Share your customizations

If you feel inspired and create a cool theme, upload an archive to your site or other file repository and link to it in the comments of this entry. At some point in the near future, iPhone customization sites will begin to support themes, but until then it’ll be fun to pass them around.

Even if you prefer to not share your custom images, be a good sport and share any cool customizations with the entire class by posting screenshots of your customizations to Flickr and adding them to the iPhone Customization group.

]]> https://superfluousbanter.org/archives/2007/09/customize-your-iphone-summerboard/feed/ 62 480 https://superfluousbanter.org/archives/2007/09/customize-your-iphone-dockswap/ https://superfluousbanter.org/archives/2007/09/customize-your-iphone-dockswap/#comments Tue, 11 Sep 2007 04:55:26 +0000 http://superfluousbanter.org/archives/2007/09/customize-your-iphone-dockswap/ Update: “DockSwap” is now known as “Customize”. Also, for more theme-like options, you may want to use Summerboard instead »

Note: Before following this tutorial, make sure you have everything you need »

With the introduction of the iPod Touch, many iPhone owners (myself included) let slip a few quiet “ooohs” and “ahhs” at the more Leopard-esque Dock background behind the 4 main application icons:

Initially, I just resigned myself to the hope that Apple would update the look of the Dock in the next major iPhone Software Update. But then a few days ago, a new application appeared in the Installer.app list: DockSwap, along with some custom Dock background images. Bleeding-edge developers be praised! Of course, I had to install it and make my own custom background, and this tutorial is a result.

Before and after

By following the steps below, we’re going to take our iPhone Dock from its default style:

to a shiny new “iPhone Touch” version:

We won’t be replacing the default applications or icons in this tutorial, though I plan to cover launchers and SpringBoard customization in the future.

Get DockSwap

Before we dig into the graphics, launch Installer.app on your iPhone, and install DockSwap. There are also some custom background images for DockSwap, so go ahead and install them if you want to play around with some alternate options.

Do not touch?

When I started writing this tutorial, the default package of custom Dock backgrounds did not include any iPod Touch versions, however this has since been remedied. For those of you who don’t want to create a custom version (e.g. changing the background color to something other than black) or haven’t customized the four default iPhone application icons (Phone, Mail, Safari, iPod), you can just install the custom images and use one of the included iPod Touch background images—however, as of this writing, I still prefer my version since it is closer to the real iPod Touch background.

The template

To make it as easy as possible to customize the dock image, I’ve created a simple, layered Photoshop file that includes the default set of icons, a customizable background color layer, and the other elements in separate layers in case you want to play around on your own:

• Download the PSD » (ZIP, 68KB)

If you don’t have Photoshop, I’ve also created two PNGs, one with reflections and one without:

• Download the Touch Dock background with reflections » (PNG, 9KB)
• Download the Touch Dock background without reflections » (PNG, 2KB)

You can just use these as-is, or edit them using your non-Photoshop image editor of choice.

Your custom background

If you don’t plan to make any customizations, and just want the iPod Touch look, you can just download one of the PNGs above and skip to the next section. Otherwise, read on.

The PSD includes a text layer with reminder instructions, so make sure you hide that before exporting your image.

You can easily change the background color of the dock by double-clicking the bottom layer in the layer group (named “bg color“). Some colors will work better than others, so play around until you get the desired result. Darker colors will work better:

Of course, there’s no limit to what you can do visually, but I’ll leave further explorations to you.

Once you have your background image the way you want it, just save it as a PNG (via Save As… or as a 24-bit PNG using the web export option).

Upload and apply

Now that you have your custom background image(s), it’s time to get them on your iPhone, and the easiest way is via SFTP. If you followed the instructions, you will be able to connect directly to your iPhone via its IP address (your iPhone must be connected to a WiFi network for this to work). To find your iPhone’s IP address, tap Settings→Wi-Fi, then the blue arrow next to the name of the network to which you are connected.

Connect to that IP address using your SFTP client, with “root” as the username and “dottie” as the password (to keep the connection alive, you may need to temporarily change your iPhone’s Auto-Lock setting to “Never”, under Settings→General→Auto-Lock, to prevent the iPhone from entering sleep mode).

Once logged in, navigate into the “Library” directory that appears (the full path to this directory is /private/var/root/Library). Once there, navigate into the “DockSwap” directory (if it doesn’t exist, create it), and then create a new directory named “Custom“.

Upload your background images into the newly created “Custom” directory, then launch DockSwap on the iPhone and select your new background image. Press your “Home” button to return to the SpringBoard (which automatically restarts), slide the unlock switch, and your Dock should now be graced by your custom background image!

Share your customizations

In the grand spirit of sharing, if you create some snazzy new custom Dock background, post it online and link to it in the comments of this entry, and I’ll start creating a collection that can be posted as a package. I may also see about getting such a package added to the Installer.app sources so it can be regularly updated and easily installed on iPhones everywhere.

Even if you prefer to not share your custom images, go ahead and post screenshots of your customizations to Flickr and add them to the iPhone Customization group.

]]> https://superfluousbanter.org/archives/2007/09/customize-your-iphone-dockswap/feed/ 8 479