Extension talk:ImageMap (Alternate)/Archive

From mediawiki.org

Bug Fixes

  1. Minor bug found in initial release - the icon for the image description wasn't getting picked up.
    This is fixed in a refresh of the code April 16, 21:15 UTC.
    If you have a version that shows the text "about this image" (possibly in another language) and no little blue ball with a italic i in it, please pick up the new version. Michael Daly 20:15, 16 April 2007 (UTC)Reply
  2. Corrected problem with local links not allowing links to headers [[page name#header text]]
    This is fixed in a refresh of the code April 18, 11:30 UTC.
    Michael Daly 10:32, 18 April 2007 (UTC)Reply


Problems

I'm running on Ubuntu server, and had a case-problem I think it was:

require_once( dirname( __FILE__ ) . '/ImgMap.i18n.php' );

should have been

require_once( dirname( __FILE__ ) . '/Imgmap.i18n.php' );

Then it stopped complaining about it. But then I got

Fatal error: Call to undefined method Title::getFragmentForURL() in /var/lib/mediawiki1.7/extensions/Imagemap/InlineImageMap.php on line 482

I had this same problem with the other ImageMap extension (ie. the non-alternate one). Documented that on the talk page there too. 130.102.0.178 06:59, 28 June 2007 (UTC)Reply

If you're running Mediawiki 1.7, it's possible that this function isn't in that version. This extension is for MW1.9 or newer.
Sorry about the case problem - I developed this on Windows and file/path case is not critical on Windows. I half expected to have someone find a case problem under *nix.

Using imagemap in Templates with variables

This doesnt work within a template:

<imagemap>
Image:my-image.png|50px
rect 0 0 100 100 [[{{{1}}}]]
desc none
</imagemap>

Its a bug that has been filed as 2257, but from these 2 or 3 extensions, is there any which will work in this way? I guess not since the bug applies to all? --Kenny5 04:39, 10 September 2007 (UTC)Reply

The bug is not in the extension, it's in MW, so no there's nothing that can be done at this time.Michael Daly 22:49, 17 September 2007 (UTC)Reply

wiki 1.6.10

Will not work ?? is there a version that does ?

Sorry, it's been tested with 1.9 and 1.10 only. As noted above, it doesn't run on 1.7. --Michael Daly 06:12, 13 January 2008 (UTC)Reply

Big blue (i) covers the image

Hi. I am trying to use this to make clickable icon-based buttons. On both Meta and en.Wiki, a blue circle with an "i" (an "information" icon, I assume) appears over the top of the icon. Depending on the size of my button, the information symbol is larger than the image itself!

I'm guessing that the "i" is an attempt at providing attribution for the image (though that's not at all obvious). Aesthetically, this is very poorly implemented. The "i" should scale in size with the image. For example, maybe it should be no larger than 1/10th of the image size (rounded down) or 18px max. If the image is only 10px, then the "i" would only be 1px. If smaller than 10px, no "i" would appear. A 180px image would have an "i" that is 18px. A 400px image would still only have an 18px "i" (that's the max). While a blue 2x2px dot on the bottom of a 28px icon is annoying, it's not nearly as annoying as having the entire image obscured by the current "i" symbol.

Even better would be an option to turn off the info notice completely. There are many legitimate reasons (such as an icon menu) in which "i"'s are not only unattractive, but also confusing as heck to the people trying to use them. --Willscrlt (Talk) 23:41, 23 December 2008 (UTC)Reply

This is not relevant to my extension. You should direct your comments to the Extension:Imagemap page. --Michael Daly2 04:51, 29 December 2008 (UTC)Reply
From Extension_talk:ImageMap: desc none on the line before the closing imagemap tag removes the big "i".

Parser functions and Variables in links

I read the note above about how variables are not supported within the links. I also discovered that parser functions break it, too.

I am pretty sure that I remember reading somewhere in the documentation that it is possible to process data at different times during page rendering. All that would need to happen is defer the final rendering of the ImageMap until after parser functions and variables have been parsed. Then the ImageMap extension would see a valid link.

I say "All that would need to happen" as if it's super easy, but I'm sure it's not quite so easy. But it sure would be helpful for a LOT of different cases in template development. Please, please consider adding that functionality into the extension. Thanks! --Willscrlt (Talk) 23:41, 23 December 2008 (UTC)Reply

Since I've withdrawn support for this extension, this isn't going to happen. However, this may have been corrected in Extension:Imagemap. --Michael Daly2 04:54, 29 December 2008 (UTC)Reply