Q) Can you deep link inside a PDF?
A) Yes, but only by specifying PDF page numbers. Can’t link to Bookmarks. Link would look like this:

http://www.domain.com/test/test.pdf#page=3

Q) Can you specify a link in a PDF to open it’s target in a new window?
A) No, not for URL links. They will open in the same window the PDF was in, thereby replacing the PDF.

Q) Can links in PDFs be specified as relative?
A) Yes, for URL links.

Here’s a couple of links worth reading that pertainto Facebook and SEO/SEM…

• How to Make a Fan Page in Facebook
• Why You Need to Make a Facebook Fan Page for Your Website NOW!

Warner Music correctly identified their unlicensed music in a couple of YouTube videos I posted for our Heath High School reunion in 2008. Videos are still there, but muted. Grumble. Will have to get some new music for those sometime soon.

• Here…
• Here…
• Here…
• And here…

Preface: You have to understand that Apple really, really, REALLY doesn’t expect (want?) folks to be upgrading the drive of their MacBook Pros. This was nothing like the nightmare involved in an old clamshell iBook drive upgrade, but boy howdy I’ve never seen so many screws.

Whew. Just a follow-up from a previous post where I mentioned I was considering upgrading the hard drive in my MacBook Pro. Found a walk-through online with photos, so I was somewhat prepared, though I found out too late the Torx driver heads I had were one size too large (doh!). A lunch-break trip to Home Depot took care of that little problem. Everything went pretty much according to plan, with three notable exceptions that I’ll post here for anyone else who may be interested in a similar upgrade:

1. During the initial “cracking” of the case, I got to the step where you remove the top panel (with the keyboard) but couldn’t get the bloody thing detached at the front middle. The article cautioned about this area and said to rock the panel side to side in order to get it to release. I went on for some time (rocking, shaking, inserting plastic objects in the gaps, etc.) before realizing that I had missed a screw that was holding this part together. Heh. One more screw and voila. =)
2. On the way out I was in a hurry and made a really unfortunate but laughable mistake. On each side panel there are four tiny screws that need to be replaced. On the first side: Screw 1… done. Screw 2… done. Screw 3… done. Screw 4… whoa. The screw went too far into the hole. Huh? Yeah. Was it the wrong screw? Nope. Weird. Couldn’t get it out, so would have to come back to it. Next! Screw 5… whoa, same problem. What on earth? Couldn’t get it out, and this was going to be a problem. Screw 6… wait a minute. There are only supposed to be four screw holes on each side. That’s when it dawned on me… I had put the screws into the screw holes for the monitor plug. Heh. Yikes. Had to leave, so I finished up the rest of the job and left two screw holes empty in the battery compartment. I banged as hard as I dared, shook, used my tiny magnetic tools… nothing. Maybe it would come out on the trip home. Nope. At home I tried sticky-tack (sidenote: my sticky tack has been in my desk since college, and it pretty gooey at this point), but no luck. In the end, I put Super Glue on the end of my screwdriver, held it to the screw long enough to get a bond, and then unscrewed it out (even though the screws were too small, the threading still prevented them from just coming by pulling). Same trick on the second one, and voila.
3. One last snafu to mention. In the battery compartment there are three tiny screws that to the casual observer will appear identical to the other tiny screws on the unit. Being a casual observer, natch, I made this error, and put them in the pile with the other small screws. But there is a big difference… these three screws have no counter-sinking bevel, and so if used on the outside of the unit not screw down flush with the case. I found this out the hard way, but noticed and put things right.

Yay! 320GB of goodness. The night before I had used SuperDuper to migrate my main drive’s date onto the new drive by way of OWC’s Mercury On-the-Go FireWire 800/USB 2 portable eSATA drive case. Sheri and I watched a movie on NetFlix while the transfer happened, and I was suprised that it was done by the time the move ended. Man, I love FireWire 800! =)

Found this link at CNN interesting today. From the article…

“It is not just coffee that can lead to caffeine withdrawal. While a 6-ounce cup of brewed coffee contains about 100 milligrams of caffeine, tea and cola have about 40 milligrams each, a bar of milk chocolate has about 10 milligrams and hot chocolate has about 7 milligrams.”

Not sure if I’m brave enough for this, but my MacBook Pro is full, and I’m out of things I’m willing to offload to external drives. Not sure I’m brave enough for this, though. Might give it a shot.

The next time someone tells you that you can’t track downloads in Google Analytics (like links to PDFs, movies, or other assets that don’t reside on an actual page) tell them they’re full of crap. =) Provided you’re using the newer ga.js method you are golden. Check it out here.

The one gotcha is that the ga.js code can’t be at the bottom of the page, which is non-typical, and could increase page rendering times. The reason Google’s ga.js code goes at the very bottom is to prevent the latency of connecting to Google from adding to the page’s render time. Since the code is now at the top of the page, there’s no way to avoid the (admittedly only potential) latency problem.

But hey, you can track your document downloads! =)

Update: Also works for offsite links.

Well, the day finally came to upgrade the memory on my father-in-law’s Mac Mini. He was running with 512MB and it just wasn’t cutting it any longer, plus I wanted to upgrade him to Leopard so more memory seemed like a good idea. Getting the extra RAM was the easy (cheap!) part, but once confronted with the Mac Mini itself I couldn’t figure out a way to “crack” it open. Thankfully, I wasn’t the first person to run into this problem, and there are many how-to’s online. Two word: putty knife. =)

To resolve ASP.NET CS0433 compile errors resulting from a changed code-behind, simply do the following:

1. rename the Bin directory (may need to wait for the processes inside to finish talking to it)
2. visit page in question (will result in an error, just ignore)
3. rename Bin directory back to Bin
4. visit page in question again

Ta da!. =)

Thanks go out to David Woods for this solution.

I’ve recently gone through the painful task of using Adobe’s GL2DW extension to convert a very large heavily component-ized, heavily templated GL CS2 site to Dreamweaver CS3. This would have been a much more grizzly experience without the help of Rob Keniger of MenuMachine fame and his revisions to the GL2DW tool found here:

http://www.menumachine.com/kb/162

Also Thuy Copeland’s efforts to catalog the issues and solutions with the extension found at her site here:

http://www.mindgraffiti.net/gl2dw-faq-for-common-problems/

I’ll summarize her findings. Prior to running the export make sure to:

1. Rename /Extras/Library to /Extras/Library/Snippets.
2. Remove all non-component GoLive object tags from components/templates (the GoLive datetime object, older smart rollover objects etc.).

A couple things Thuy doesn’t mention:

1. gl2dw will not handle editable header items correctly. Beware that after conversion you templates may not have editable headers, and thus any change to the templates would overwrite the head elements of your pages. Make sure and check this and add the editable regions back in if necessary.
2. Make sure all components and templates are loose in their respective folders, and not nested in subfolders. If you have nested folders, move the components/templates out of their subfolders (renaming if necessary). Example: /Components/interior/header.html could become/Components/interior_header.html

GoLive’s templates, components, and other Extras can be stored in hierarchal folders. Components are in the Components folder, and they can be in subfolder after subfolder after subfolder within. Example:

/Components/header/
/Components/interior/callouts/
/Components/interior/menus/

There doesn’t appear to be a way in Dreamweaver to organize templates and components like this. All components (called library items in DW) apparently live in one big bin (/Library for library items, /Templates for templates) with only alphabetization available to help organize them. Groan.

Behavior appears to be identical in the new DW CS4.