UPDATE: Version 2.0 is now available. See article here.
I didn’t want to go the whole week without giving a quick update on the latest builds of sIFR. I’ll be releasing version 2.0b on Sunday and features to look forward to include:
With contributions coming now from Seattle, Baltimore, Sweden, The Netherlands, and other corners of the world, the task of getting all of components distilled down to a single mechanism is not trivial. The 2.0b release this weekend will still be a “developer’s release” per se and might not quite be idiotproof yet, but it will contain the same full feature set as the release version.
UPDATE: Version 2.0 is now available. See article here.
Three days and tens of thousands of hits later, sIFR has so far held its own as a solid, compatible way to replace browser text with custom typography. I’ve released a few new updates in response to minor glitches reported, but more importantly, a solid release is only days away. In the meantime, please feel to download version 1.1.4 which simply refines the replacement function a bit so that it should work on very complicated replacement rules and such. I’ve also updated the example page.
Here are some of the issues which I plan to address in version 1.2 (to be released hopefully in the next few days):
I’m probably missing some stuff, but those are the biggies. I want to again thank everyone who has taken the time to put this thing through its paces over the last few days. sIFR is nice in that it is portable enough to pop into your site fairly quickly, and pop out of your site even quicker. The nice side-effect of this is that when I release updates, they should be fairly easy to apply. The upcoming 1.2 release will have its own dedicated page with release notes, but I’m a designer so don’t expect a full-on SourceForge repository or anything.
Please feel free to comment on any of the items above… especially if you have solutions to suggest or additional features to request.
UPDATE: Version 2.0 is now available. See article here.
It’s been well over ten years now since the debut of the graphical web browser and we still don’t have an easy way to deliver rich typography using HTML/CSS. With CSS we can size, style, color, kern, show, and hide our text but we can’t deliver something classical typesetters have delivered since at least the 15th century: custom typography. Until now. In concert with Shaun Inman and Tomas Jogin, I am releasing into the public domain a scalable, multiline, Flash 6 compatible version of IFR to help you reduce the amount of browser text in your life and free the world from the scourge of Arial.
An updated example of sIFR (now at version 2.0) is available here.
Read more…
I was at a bar this weekend telling a couple of friends how I’ve reflexively stopped using the grammatical device “i.e.” lately because of the industry I’m in. Whenever I have the urge to use it in a sentence, I’ve begun using “e.g.” instead. It’s really quite silly but I just can’t help it.
This sparked a bit of a dorky discussion (see: chick repellant) about what the two abbreviations really mean. “i.e.” seems the most common, but I’ve always assumed they were just two interchangeable ways to say “for example”. Turns out they aren’t, and friend #1 lost twenty bucks to friend #2 because of it.
According to the dictionary, “i.e.” means “that is to say” while “e.g.” means “for example”. So the difference would be as such:
“There are many ways to lose a race (i.e. there are a lot of obstacles to winning).”
“There are many ways to lose a race (e.g. disqualification, injury, sickness).”
So it turns out that by reducing my use of I.E., I am actually a more grammatically correct person now.
E.G. is the new I.E.
Ever wanted to turn a cloudy day into a sunny one? Well now you can, with the magic of PHP. If you use the Live Theme here at Mike Industries, you may have noticed that the weather conditions displayed in the header have improved markedly over the last couple of weeks. We’ve gone from a summer of “partly cloudy” and “fair” days to “sunny”, “beautiful”, and “spectacular” days. Here’s the lowdown on the PHP-induced warming trend:
When I first launched the Live Theme, it was merely a live shot of Puget Sound with no weather conditions readout. But then I saw Michael Simmons’ handy dandy weather readout and got jealous enough to set up a weather readout of my own (full instructions will follow later in this article). Problem was, I didn’t like what I was seeing on the weather report. We are in the middle of our third spectacularly sunny Seattle summer in a row and my weather readout still said things like “Partly Cloudy”.
Then one day a couple of weeks ago, something made me snap. I looked out the window of my office at the 360 degree view, and I saw nothing but blue sky and one tiny speck of a cloud in the distance. I then went to the web and saw that Mike Industries was reporting “Partly Cloudy and 80 degrees”. It was clear at this point that something had to be done.
Read more…
The first weekend of August is a great time to come to Seattle. Not only is it sunny and beautiful, but the city also plays host to Seafair Weekend; an annual outdoor festival featuring two days of airshows by the Blue Angels, unlimited hydroplane races, and a big old floating boat party on Lake Washington. This year’s waterborne festivities resembled New Orleans during Mardi Gras more than any other year I can remember. Think beads. Lots of beads. I didn’t see one indecent exposure ticket getting written though, so perhaps Seattle cops have lightened up a little.
Anyway, I was planning on having a bunch of photos to post, but unfortunately I forgot to charge the Optio S and it ran out of batteries right after the Blue Angels show was over. Below are ten photos from the airshow:
Something happened today which shook the very foundations of what I’ve always believed about computers. See, maybe this was just a crazy notion, but I was always under the impression that if there was ONE thing computers did well, it was math. Simple math, algebra, geometry, calculus… it didn’t matter. Computers have always been equation solving machines. Or so I thought.
As it so happened, I was catching up on three months of procrastinated Quicken transactions and I had a slight discrepancy in my numbers. I typed in Command-Space “cal” to launch the built-in Apple calculator via LaunchBar in order to check my figures. Here is the equation I typed in:
9533.24-215.10
… and here is the garbage Apple babbled back at me: 9318.139999999999
What? How is that possible? I’m subtracting two decimal numbers and the result is a repeating decimal? Thinking something was wrong, I began experimenting by simplifying the equation:
9533.24-.1
Result: 9533.139999999999
Convinced I had the calculator in some whacked-out Reverse Polish mode or something, I began checking the menus. The only relevant menu item was a setting called “Precision” which went from 0 to 16 and was defaulted at 12. How about Precision “Infinity”? I want my damned calculator to be precise enough to subtract simple decimals and apparently 12 isn’t enough to do this. As it turns out, “Precision” is a bit of a misnomer for this setting because it just represents how many decimals you want to see before the number gets rounded. Anyway, that still doesn’t explain why an equation which needs no rounding to begin with is giving me a repeating decimal.
Upon more experimentation, I discovered the following:
And so there you have it… what was once simple is now apparently difficult again, thanks to the otherwise brilliant piece of engineering that is OS X Panther. I’m sure the explanation has something to do with floating-point calculations, whatever the hell those are, but that doesn’t make this bug the least bit more acceptable. My worst nightmare is that the repeating decimal answer actually is the correct answer from a computing standpoint but most computers are smart enough to round it for us, knowing what we really want. That would really alter my perceptions of low-level computing quite a bit.
On the bright side, we finally found something PCs are better than Macs at.
Subtraction.
Beauty comes in many forms. For normal people, maybe it’s Ashley Judd in a bedsheet on a Sunday morning. For web dorks, however, it can be something as mundane as extensionless URLs or intelligent error pages. Sad as that may be, most of us don’t have the Ashley Judd option available anyway, so we shouldn’t feel too bad about deifying code.
Last week’s post on dirified URLs was supposed to bring about some sort of consensus opinion on smart URL-naming conventions. Thanks to everyone who posted their very helpful and enlightening comments, but in the end, we only discovered more options and came to no mutual conclusions. It appears that people just look for different things in their URLs and what you do with yours is up to you.
Having said that, I have completely redone my URL structure and 404 strategy at Mike Industries based on the comments received and some additional research.
Related: Read the resolution to this article here: Beautification Revisited
Although the subject of clean URLs has passed through the blogosphere plenty of times over the last year or two, I don’t feel there has been a definitive answer as to a) how important they are, and b) what the best way to implement them is. I plan on making a naming-convention change at Mike Industries this week and am soliciting user feedback as to the best way to go about it.
Clearly the most compelling use of intelligent page naming is what is known in the industry as “vanity urls”. If we are calling out a special Lance Armstrong section on ESPN.com via the use of a television, radio, or print campaign, it is a huge advantage to point readers to something like “espn.com/lance”. A nice, clean, easy-to-remember URL is the only chance we have of planting information into our audience’s heads which may stick.
But what about the recent trend towards Googlefying URLs? In this case, you have a URL like:
https://mikeindustries.com/ blog/ archives/ 2004/ 04/ 20/ what_is_wrong_with_the_cottage_cheese_industry/
… which is neither memorable nor particularly vain. The idea, as I understand it, is mainly to pack the URL with keywords relevant to the subject of the page, so as to coax Google into awarding a higher page rank.
There appear to be advantages and disadvantages of naming pages in this fashion.
Read more…
One of the longest running rumors in the Apple community is the emergence of an Apple-branded cell phone. Apple has denied the existence of such a product for as long as the world can remember, and up until now, they’ve had legitimate reasons to stay away from the cell phone market. Poor data speeds, poor service, incompatible frequency standards, and lack of profit on handsets have all been cited as reasons to stay away from the cell phone business. With the emergence of several new developments in the cell phone industry, however, it is becoming rapidly clear that Apple is ripe to enter the cell phone market within the extremely near future.
Let’s examine what’s new:
As companies like Virgin, AT&T Wireless, and others enter the new MVNO (Mobile Virtual Network Operator) market, it is becoming clear that the key to success in the MVNO realm is branding. For those unfamiliar with MVNOs, they are a relatively new phenonemon in the wireless industry whereby a company like Virgin resells wireless minutes through a provider like Sprint PCS. A customer buys a Virgin-branded phone at a retail location, signs up with service through Virgin, and goes on to use the phone, receiving bills and notices as though everything was coming from Virgin. Behind the scenes, however, Sprint is doing all the heavy lifting. Their network provides the infrastructure for placing and receiving calls, they meter customers’ usage, and just about everything “technical” related to the customers’ use of the phone is handled by them. The deal is a win-win for both companies because Sprint fills up their network with more customers and Virgin’s brand does all the selling. Many MVNO operators have a special differentiating factor to them, and Virgin’s is pre-paid service… perfect for teens.
It used to be impossible to design a phone which would work on most cellular networks. The U.S. market was so splintered with incompatible standards that service providers had to pay handset manufacturers to develop phones for their platform. Well now it’s 2004 and the world seems to have standardized on two basic standards for now — GSM and CDMA. In the U.S., Sprint PCS and Verizon use CDMA and T-Mobile, Cingular, and AT&T Wireless use GSM. What this means is that handset makers need only develop for two platforms to cover 90% of the market. Handspring currently offers its Treo 600 to customers of all five of the providers mentioned above. It is for the most part, an identical unit, save a minor color variance and a few internals.
Handspring is smiling all the way to the bank with the success of their Treo 600 smartphone. Even with a $600 price (near the top of the cell phone market), Treos are flying off the shelves faster than Handspring can manufacture them. While most people pay under $100 for their phone, or nothing at all, the pent-up demand for a true portable convergence device is so great that Handspring can sell a unit with a fairly low-resolution screen and no bluetooth for crazy prices. There will always be cheap little free phones around to coax customers into signing long-term contracts with service providers, but Handspring has proved with the Treo that the high end of the market is where the profit is.
Apple has enjoyed the same sort of success with the iPod as Handspring has with the Treo. Both are very expensive devices which were eaten up by the public not because they filled niches, but rather because they created niches. There was no clamoring for a $400 portable music player before the iPod and there was no clamoring for a $600 phone before the Treo. Apple has turned the iPod into a cultural phenomenon by giving people all sorts of new freedoms they never had before.
The iPod and the Treo are about the same size, they both play MP3s, and yet the iPod only does a few things better. It has up to 40 gigs of storage, as compared to the 1 gig SD card you can stick in a Treo. That’s about 10,000 songs vs. 250 songs (albeit in removable form). The second thing is does better is provide a dedicated music-centric interface. The Treo’s interface must do 1000 things with the iPod’s does only do a few. And finally, the iPod looks a little better than the Treo, and that is a testament to Apple’s legendary design prowess.
Aside from those three things, however, the Treo dropkicks the iPod right off the playing field. It makes calls, organizes contacts, syncs with PCs and Macs, plays games, runs applications, gets email, surfs the web, checks blogs, has crazy-high battery life, and on and on and on. So if I only have room for one cigarette-pack-sized device in my pants pocket, which one am I going to pick? That’s easy. There is no good reason for portable music players to continue on as standalone units, and Apple, being a smart company, realizes this.
The “wireless web” has long been a joke among those of us involved in web design and development. Who wants to develop for tiny screens and sub 14.4kbps speeds? Cellular service providers placed large bets on their data networks early and when the customers failed to come in, the public lost faith in the business. While the 3G speeds companies have been promising for the last several years still aren’t here yet, the data rates on the big five cell networks in the U.S. could now legitimately be considered viable for lite-duty digital communication. Reading e-mail is a snap, syncing contacts takes seconds, and even browsing the web is an acceptable experience if you don’t mind waiting a few seconds here and there. Were Apple to make waves in the cell phone industry, they would make waves on the data side of things, and the state of the industry suggests the timing may finally be right for such a foray.
Read more…
... or use RSS