Read It Later Fluid has been upgraded to 2.0 and with the upgrade it got a new name: Read It Later Restyled. I have turned it into a userscript so more people can take advantage of it. What it does is allow any userscript supporting browser to change the look of the Read It Later Web interface.
“Read it later Fluid” is a set of userstyles for Fluid, a Site Specific Browser for OSX, that updates the look of the Read It Later Web interface. I was unhappy with the default look, so I created a new design that more closely matches their main site and iPhone app.
I’ve been wanting to customize the templates, for the Publish feature in Delicious Library 2 for a long time. The ones it comes with are nice, but I want to be able to pull the data and display it in my own way, so I reverse engineered one of the default templates to see how it all functioned. This is a work-in-progress, so I’ll update as I figure stuff out.
While designing your own Tumblr theme, you have the option to choose between three different audio player colors for your audio posts: black, grey and white. If you’re pulling data using the Tumblr API, you are limited to just the default white player. With a slight change to the code, you can display it in other colors.
I’m a member of a local comic group called Midmococo. Each year we host an official 24 Hour Comics Day location where comic artists attempt to create a 24-page comic in 24 hours. This year, we’ll be working downtown at the Columbia Art League. Because of the extra space, we were able to expand our event. To get more people involved and fill that space, we needed publicity, so I thought this would be a good time to try and silkscreen a poster. With my wife’s help, it turned into an interesting process, so I thought I’d share. It didn’t quite work out as planned, but it still looked cool.
While reading an article on NYTimes.com, I discovered a handy little feature that I never really noticed before. When I double clicked on a word to highlight it, a pop-up window appeared with a definition. At first I was annoyed to have a pop-up appear, but once I figured out what was going on, I started to like it.
When I launched the new design of my site, I also changed the way URLs were structured causing broken incoming links from search engine traffic. Since I didn’t want Google to think those pages vanished, I needed to create a few 301 redirects to keep my posts showing up in searches. Because of the way Symphony does some RewriteRules in the .htaccess, the default, easy way to add 301 redirects doesn’t quite work as expected. After some asking in the forum and some trial and error I managed to find a different way.
<pre> in Symphony
When I was creating my custom templates for Symphony, I reused a lot of code from the default template. This helped me learn how Symphony functioned and how to write XSLT. Because the default template used wildcard selectors when outputting data in textareas, my template did too. It worked fine until I had a post with code blocks in it and then I had a problem.
While I was building my site in Symphony, I had a bit of a learning curve with XSLT and even simple, little things were a challenge. One of those dumb, little things were getting Internet Explorer conditional comments to output in my XHTML. It took a bit of Googling, but I figured it out.
I finally got around to refinishing the top surface of the lighted drafting table I found at the University surplus Ebay store. It looked pretty rough at first, but after a few coats of stain and polyurethane it looks new again. Now, it’s time to start using it!