In the comments to the original linking syntax request, ghoppe said:
Thanks for the card links. As the guy who whipped up the jsfiddle, I admit I lifted the tooltip function (which is open source) to speed the creation of the popup. But there is an API to retrieve just the images from gatherer — any popup script could be used. e.g. The Cheese Stands Alone I completely understand the stance of not wanting to use undocumented APIs, so I'll take what we can get. ;) – ghoppe May 3 at 1:13
Kevin Montrose's answer there says
Do note that the AutoCard feature only seems to document opening new windows, that nifty hover affect is something else. I'll do some digging to see if that is documented anywhere, but if not we can't copy that particular behavior.
Like many of us, I'm a programmer of some experience myself. My question is: why shouldn't we implement this anyway, even if the image service is undocumented?
Reasons to implement:
- It's very easy:
- The original blog post uses the tool-tip hover as the first example, implicitly endorsing it, even though it doesn't provide the code in the article text.
- The original blog post was written in 2002. This API has been around, and been stable, for 10 years! Do we have any reason to think it will change?
- It's very low-impact. This is not critical, site-breaking functionality. Nothing depends on it. If the API changes, we don't see pop-ups anymore. Oh well. That would mean... we wouldn't see pop-ups! Which is what we (don't) have, right now.
- It would be very slick, and would present a much more 'pro' image to the MTG crowd.
What are the counter-arguments? It would be nice to have a chance to discuss the issue as a community, and hear the issues.