Friday, March 07, 2014

flickr hack for a (somewhat) classic view (with bookmarklets)

flickr hack (but not really a hack) for classic view of a photo stream, Add ?details=1 to the end of a url. Oddly enough there is an "edit" button above your photostream that will do the same thing. Who knew and why would they hide it there?

Example:

http://www.flickr.com/photos/sakraft1/?details=1

vs

http://www.flickr.com/photos/sakraft1/

For a classic view of a set, just add "detail" to the end (this one will not work of the url contains "with/" and then the number for one of your photos, you need to delete that from the url first):

http://www.flickr.com/photos/sakraft1/sets/1698787/detail

Now, instead of having to manually paste that in, lets make a bookmarklet. This one will add "?details=1" to the end of your url.

javascript:window.location.href=window.location.href + '?details=1';

Install it by making a new bookmark and making that the address or drag this to your bookmark bar:

?details=1

And here is one for "detail" (for sets):

javascript:window.location.href=window.location.href + 'detail';

or drag this to your bookmark bar

detail

You can rename the bookmark to anything you like for your convenience as long as you keep the address the same.

Still not exactly the way flickr used to be, but its as close as we'll get until Yahoo listens to the angry masses.

Labels: , , , ,

Wednesday, March 05, 2014

My Canon SD1000 has a weekend at Bernie's

My Canon SD1000 has served me well. I got it after my beloved Kodak DX6440 had an unfortunate meeting with some pavement. The Kodak still works, its just not the same, and the battery compartment door is not to be trusted.

So it sort-of was after the SD1000 had its own "accident." I was on vacation last June at the pool and went to the concession stand. The camera happened to be in my hand. Needing both hands to carry the tray of food and drink, I put the camera in the cargo pocket of my swimming trunks and quite forgot about it.

We ate and then were about to leave the pool area when I decided that it was very hot and I might step into the pool for a second to cool off. I went in and out just that fast. As soon as I stepped out, you might as well have queued the dolly zoom. Like a flash of lightning I remembered the camera in my pocket.

The silly thing is, as this was a beach vacation, I had the underwater housing for the camera with me. Just not at the pool. It was up in the room. High and dry.

Enter the bucket of rice. I removed the battery and memory card and put them in with the rice and the camera for a few days of our stay. Luckily by this time the SD1000 was a backup camera to my DSLR. More luckily, I later found that all the photos on the memory card were intact.

After a few days, the SD1000 could be coaxed to life. But like the Kodak before it was not the same and not to be relied upon. Sometimes the lens would get stuck out. The exposures often came out all wrong. A few months later while snapping a photo of a jeep made up in the livery of those from Jurassic Park, the screen stopped working. It would still take photos but I would have to use the viewfinder as if it were 1998 all over again.

And from there it seemed to spiral downward until the SD1000 just sat there. Only taking photos in macro mode.

Until I remembered CHDK. This is a firmware that boots off of a memory card and lets you do all sorts of neat things with Canon cameras. Since some of the hardware seemed to work some of the time it seemed to me perhaps this new firmware could work.

Huzzah! It took a while (and a few terminal commands) to figure out how to make my memory cards bootable but it seems fully functional now. For a backup camera. I still don't entirely trust it. And the caveat is that I have to use one of the two memory cards on which I have installed the firmware. Hence the Weekend at Bernie's analogy. Actually I think it is a Weekend at Bernie's II analogy.

For all the trouble and the low price of a new point and shoot camera, why bother? That underwater housing. The very thing that could have prevented all this in the first place. It cost a pretty penny and was made only for my camera model. I should hate for that to go to waste.

Labels: , ,

Monday, March 03, 2014

A quick dojo cheatsheet



I made a quick and simple cheatsheet for the dojo javascript library. Mind you, this is far from comprehensive, it only contains a few things that I use most frequently. And its for an older version: 1.7, because that's the version being used in a project I am on. This isn't some fancy infographic, just info I need handy. Click here for my dojo 1.7 cheatsheet.

Labels: , ,

Wednesday, February 26, 2014

Eric Carle meets J.R.R. Tolkien


I am an eye and I can covet one ring. Can you do it? I can do it!

Labels:

Friday, February 21, 2014

Yahoo Store Tags Not Working - The Fix

In my spare time I am building an e-commerce website for a friend. As it is my first e-commerce site (I've built many a static site before) I steered him towards a Yahoo! Merchant Starter account. I am already familiar with their small business webhosting tools and I figured the store and cart tools would be similarly easy to use.

Not quite. At first I was looking at their store editor tool. This is barbaric to say the least. Luckily I am a web designer so I decided to build the site myself. I had planned to do so from the outset but I wanted to see if the store builder could give me a starting point. Not really. The merchant started account is acutally two accounts in one, one side is if you are using the store editor. You don't have access to things like HTML files, you are forced to use the aforementioned barbaric store editor tool that was probably written in 1996 and never updated. The other side is the web hosting side, which I am familiar with and where you can make your own pages from scratch.

Going with the later you then have to get information from the catalog manager into your own page. This is done with Yahoo's own Store Tags. The look like an HTML comment or a server side include if you're familiar with those. Something like <!--#iamatag--> or some such magic.

At first I designed a static page without the store tags just to make sure everything would look correct once the data populated. Then I replaced things like product images and descriptions with the store tags, uploaded to the server and... ...nothing. I made sure the catalog was published. Yup. Searching the help area tells me nothing I don't already know. Time to email customer support.

Customer support is good but not great. They respond quickly but not accurately. For each question I have it takes 3 or 4 emails back and forth, usually escalating to different people, before I get information that is useful and should have been in something known in most circles as documentation.

At any rate, it turns out that either my OS or Dreamweaver were setting my file permissions to be too strict! It doesn't matter which because this was easily fixed by telling my FTP application to change the permissions on upload. The owner, at least needs to be able to execute the file, not just read and write. Even if I couldn't do this automatically, I could change files one by one on the server after upload (not ideal). I had to post this because it drove be crazy. For a while I thought it was the file encoding and I tried every encoding combo under the sun. Permissions! Got it? Good.

Labels: