Blog Archives
How not to break your Nexus One Car Dock
… and what to do if you do.
My HTC Nexus One Car Dock broke only a few months after I got it. I searched the Internet about this, and found that I was not alone. One man suggested a way to handle it with care and I am now following his advice with my replacement dock. I am providing this video to give you a visual tutorial about how to baby your fragile car dock. Hope it works for you!
In case your car dock breaks, I recommend that you do what I did: call HTC Repair and tell them that your Nexus One Car Dock broke and you want them to send you a replacement under the one-year warranty. If they give you any trouble, tell them that you know of other people whose car docks broke and who received replacements. They should email you an RMA label. You will have to box up your broken car dock and drop it off at a FedEx with the provided shipping label. HTC Repair should receive it within a couple of days, process the replacement in a couple of days, and ship it back to you via FedEx in a couple of days; i.e., you “should” have a new one in your hands within a week.
What happened in my case is Read the rest of this entry
Why I’m not using Typekit Fonts yet
I tried installing Typekit fonts on this blog, and I almost gave up because the complexity of it reminded me of why I moved my blogs from WordPress.org to WordPress.com. I suppose it would have been easier if Typekit had built-in support for the Twenty Ten theme, but when I tried it a couple of weeks ago, they didn’t. So I had to open one of my blog pages in Safari, select Develop from the menu (because I installed the optional developer tools), select Show Web Inspector, and study the CSS to suss out what the “selectors” were for the masthead and other sections of the pages I wanted to set the new fonts to. Even knowing CSS, it took some searching through the code to see what was styling what, since Classes and IDs are arbitrarily created by each CSS author.
Once I found the Classes and IDs, I had to go back to the Typekit editor (which always took a long time to load, as did everything else on the Typekit site) and manually enter the “selectors” I wanted to apply the fonts to. I found that I had to do it with periods in front rather than hashmarks, or maybe it was the other way around— I would have to be writing CSS on a regular basis to get it right, and who does? (If you do, then you wouldn’t find it complicated at all, but then you might as well have a WordPress.org site and not a WordPress.com site, eh?)
ASL Policy and Deaf Interpreters at RID Conference
Abstract
Reflections on my recent experience at the RID Region V conference, the benefits of the policy of using ASL at all times during the conference (except in a few of the workshops that were interpreted), and the great contribution of deaf interpreters to the field. I also discuss my experience as a workshop presenter and my thoughts on how to make my discussions of interpreting less hearing-interpreter-centric, and more inclusive of all interpreters, especially deaf interpreters.
Digital zoom test with Froyo camera app
I finally got the Froyo (Android 2.2) update pushed to my Nexus One today, and I noticed digital zoom as an option in the new Camera app. I ran an experiment by placing this ad down on the counter, and standing in the same place taking photos at 2x, 1.5x, and 1x digital zoom.
2x digital zoom
Why I moved my blogs from WordPress.org to WordPress.com
I finally got tired of the hassle and hours it took me to update my WordPress.org-powered self-hosted versions of two different blogs–danielgreene.com and smithersgreene.net. Trying to upgrade my blogs to WordPress 3.0 was the last straw.
I’m a guy who started writing his own HTML and CSS in 1996; in fact, I was one of the first handful of brave ones on the Internet to style valid HTML with CSS knowing that most browsers couldn’t handle it. After all, what did I have to lose? Little old me with his personal website.
This was a decade before Flickr and YouTube and Facebook and Twitter allowed you to post content with ease and let them take care of the code, and years before every major website was written in structural HTML and styled with CSS. This was back when you had to either have a self-hosted website or something like AOL Hometown Web pages. This was when “Web Designers” would charge you an arm-and-a-leg for a page and a couple of links. I was okay with the idea that, if I wanted a site that used proper HTML (without proprietary structural markup) and CSS, I had to get an ISP to host my own website. And I had to write all my own HTML & CSS.
Things have changed in the past few years. Even with WordPress.org, I had more freedom to blog without worrying about the coding. When I didn’t have to worry about updating WordPress and editing .htaccess pages and PHP files, it worked great. But I hated it when I would break my site when trying unsuccessfully to upload new versions of the blogging platform software. I thought, “Why can’t it be more like posting content to Facebook, Flickr, Twitter, or YouTube? I can’t break those sites. There must be an easier way.”
