I’ve come to a resolution on this whole issue of “plagiarizing” code. (I really shouldn’t even think of it that way, frankly. It’s just a nice, sensationalistic way of referring to it.)
First, a brief update. Brandy, being very generous by giving her limited time to a complete stranger, promptly got back to me on this issue after trying to investigate who actually wrote the dropdown menu code at Sapient. She couldn’t find out who actually wrote the code, but offered this bit of sage advice:
————————————————————————
“I would just use it and if anyone gives you a problem then find another solution. You could even give proprs in your .js file, that’s a really good way to be ehtically correct. You arn’t hiding that you snagged it and your happy to say that you did cause you think it’s a well written peice of code. I can’t see how that could bring any harm.”
————————————————————————
Exactly. This was pretty much where I was sitting (near the fence) on the issue, but my uber-ethical side had to get a second opinion. And this was also the gist of what Rob was saying in the legal speak I quoted in my first post on this.
So, I plan on customizing the code for my purposes on a future project, but the original project for which I was investigating this for wound up continuing on with the old (IMO, hideous looking and dirty code-wise), non-validating code. A few options were explored before making this decision.
Taking the dropdown menus out completely — even though we all agreed that they were not necessary to the usability of the site — was impossible, simply because of the red tape we’d have to go through with the higher ups to make a change like this.
We could have also used a different DOCTYPE, but that would have thrown the X/HTML compliance requirement out the window. No can do.
So, the decision was made with the client and the CMS developers that we would take the DOCTYPE out completely. Again, not my first choice, but it was mostly out of my hands. As long as the code would validate “conditionally” by force-feeding an X/HTML DOCTYPE to the W3C validator, all the CMS-driven requirements would be met - as stipulated in the contract. It just meant that we would have to make sure to test religiously, to make sure that sending certain browsers into quirks mode didn’t screw anything up.
Which brings us to the end of our story for now. The site got delivered a couple weeks ago, and after CMS integration and much content entry (thankfully not performed by me or anyone at my firm) was launched on Monday.
I still can’t wait to get an opportunity to put these menus into a site at some point, though. Everytime I go to the Cingular site I spend 10-15 seconds rolling over the navigation just to see how smooth it is. Heck, the only reason I go to the site at is to marvel at the menus! Nice work Brandy and team.