Comments for Funroe

Comment on The Last Loose Caboose T-Shirt That Never Was by Lonnie

Lonnie — Thu, 28 Jan 2010 05:23:48 +0000

Yep, those were some good times.
I still have those tapes in the same box that I packed them into so many years ago when I shoved everything I could into a sixteen foot uhaul trailer and made my way to Maine with my trusty assistant, the infamous Young Brad, who is not so young anymore. The tapes await. I hope that someday they get digitally mastered and then compiled.
I’m pleasantly surprised to see this web listing, but knew it would probably be from Jess. Thanks Jess for all your work. That Tee shirt looks familiar.
Lonnie

Comment on Who Dat Gear by Houston Whodat!

Houston Whodat! — Wed, 20 Jan 2010 07:48:11 +0000

I can think of a hoodie that would go nice in this pic

Comment on Ta Ta Tioga! by GooB

GooB — Tue, 29 Dec 2009 07:34:50 +0000

It always makes me sad thinking of Boss. Good times looking at the trailer. Haha you can almost make out Joe the loser on the cement.

Comment on Not A Glenn Kennedy by Jess Planck

Jess Planck — Thu, 19 Nov 2009 22:17:21 +0000

Yea he would have loved it. The iPhone pocket art reminds me of Glenn’s pocket watercolor kit. He would love the bizarre idea of creating art anywhere and instantly publishing it to worldwide audience. Not that I have an audience, but you get the point!

Comment on Not A Glenn Kennedy by Michael Riggins

Michael Riggins — Sat, 14 Nov 2009 19:07:01 +0000

Glenn’s always wanted people to respond to his work this way. Wants everyone to be an artist.
That looks real fine to me!

Comment on Really boring HTML & XML tag class function for PHP by Revisiting My Really boring HTML & XML tag function for PHP » Funroe

Revisiting My Really boring HTML & XML tag function for PHP » Funroe — Fri, 06 Nov 2009 17:34:38 +0000

[...] exclusively as a function. If you want to see the earlier similar function used in a PHP class see Really boring HTML & XML tag class function for PHP. You would have to edit the original example to match these changes, but if you want to use a PHP [...]

Comment on Thoughts on Typekit with Typekit by Jess Planck

Jess Planck — Fri, 21 Aug 2009 20:10:28 +0000

The Wikipedia article is really good on this one. I remember being excited and disappointed at the same time with Netscape 4 and TrueDoc support (ugly is a kind word): http://en.wikipedia.org/wiki/Web_typography The seed conference example is perfect for showing how CSS hacks are bad for accessibility and seo. When they cut up a word like "Crown" with spans to make a drop cap it actually becomes "C rown". Search engines and screen readers might not put the word back together. The proper thing would be use a drop cap font with proper glyphs so you wouldn't cut up the word with span tags. There are many ways to make that example accessible (jQuery, php, CSS :first-letter), but nothing would be simpler than having the right typeface for the job in the beginning. I doubt it will be tough sell for my clients (another story for my day job at nicholls.edu, it's hard to buy pencils right now). For freelance I do mostly sub-contract work for designers and design studios. The designers are always asking for custom fonts on websites and I pull out SIFr or SIFr2 most of the time with huge performance issues. Those designers have clients used to paying thousands of dollars a year for billboards in bad locations. They generally pay less than $150 a year for a website. Another $25 or even $50 to make the website more attractive won't be a hard sell. It will beat the price (sometimes the effectiveness) of the billboard hands down. My clients are given HTML roughs on-line not jpegs most of the time. It will be easy for me to design with something like Typekit and give the client a choice. I know in most cases the better design is going to win. @font-face has been around since CSS2. (see https://developer.mozilla.org/index.php?title=En/CSS/%40font-face) but typographers fear the internet more than Lars Ulrich ever did. Now Typekit has a few competitors; http://fontdeck.com/ and another I can't find. The point is that foundries have a method to protect those font files they have been reluctant to let us use on the web. Now it can only get better or worse.. in a David Carson "Raygun" sort of way.