Was thinking the same thing. We're using both Salesforce and ZenDesk, and our strategy is trying to co-locate as many of our 'services' as possible, reducing the number of systems, logins etc. Still don't think we're ditching ZenDesk...
"PETA is extremely disingenuous," said Jennifer Pozner, executive director of the New York-based advocacy group Women In Media & News. "They have consistently used active sexism as their marketing strategy to garner attention. Their use of sexism has gotten more extreme and more degrading."
Playing on sex have proved ingenious for PETA. They've attracted loads of attention. The message they are trying to communicate have, however, to some degree drowned in meta discussions on how they try to do it. But there's no doubt they've gotten a lot of attention, so I don't think disingenuous is the right word here.
Doesn't necessarily make it less controversial or 'wrong' for some people, though.
I don't know much about molecular structures, but it's a really interesting subject. The crowdsourcing aspect of this is also something that makes me believe a little more in human kind.
Of course, if some idealistic crowd were to find the cure for AIDS or a HIV vaccine, some big corporation would surely claim the patents on it or something; it is of course highly ethical to earn big bucks on others' misery, instead of just getting the cure out there to the masses.
This story reminds me of the pilot of Stargate Universe, by the way. The gamers will get to go to space now, right..?
So, just to get this right; to use this script, you'd have to know your content, right down to how many words each text element contains and so forth? The exception being the pairings and repeats. If you already know your content that well (ie. it's static and not any form of user input), you could just add some extra inline elements to your markup, I mean, you're already heavily customizing the text elements.
This is perhaps more elegant, but it makes your CSS too tightly bound to your content. Add a word in the markup, and you'll have to update your CSS as well, with a none or whatnot.
By all means, nice work, I just rarely work with pages where I know how the content will turn out.
Are you using an image element to support printing? There's no other reasons to not use CSS3 to create the dot (or the somewhat more pragmatic approach of setting it as a background image on the target element, reducing your markup), as I see it?
I think you should also expect that people could want more than one target on their maps. There's no downside to switching from IDs to classes here.