Extension:MultimediaViewer/Roadmap

Not started

 * QUnit testing:Woo

Not started

 * Figure a way to sanely handle thumbnails and full-size images:Would it be more performant to fetch the full-size than to request a bunch of weird sizes? The former would be better cached, I think...ask someone, probably.
 * Full-size image will often be much larger than you need, and will cause problems if the file needs rotation or is in a non-web format. I recommend first using the existing thumbnail already on the page -- so you get something scaled up but really fast -- then do an API imageinfo call to fetch a screen-size image based on the size of the actual lightbox. You can perhaps bracket to some semi-standard sizes (640px, 800px, 1024px, 1536px, 2048px) to avoid creating a bajillion thumbnails for every slightly-different window width. --brion (talk) 17:43, 27 September 2013 (UTC)


 * Invisible span with "File : " and the extension:Mark
 * Add screenshot:Seriously
 * Link to proper-language discussion page?:Not sure how, or if we want to, or what.
 * Put the description into the view:Mark
 * Stick in geolocation data if available:Mark
 * Put in link to remote repo if applicable:Mark
 * Put in creation time if applicable:Mark
 * Add uploader to list if applicable:Mark
 * Add geoloc data if applicable:Mark
 * Explore categories, maybe stick some into the interface:Mark
 * Category and Gallery support:Mark
 * Use MediaWiki:Gadget-libUtil.js instead of relying on resource attribute:Thanks User:Rillke
 * Icons for remote repositories via the API or a config variable:Mark (core patch(es))
 * List item decorative icons:Mark
 * Static positioning:Mark

Ready for code review

 * Fetch information about image from API, and show title:
 * Show byline in the view:

Finished

 * Initial commit:
 * Import library updates from another repository:
 * Pull resize fixes from multilightbox:
 * Shift the colour scheme to be black-on-white:
 * Change links to Multimedia/Media Viewer:
 * Get ForeignAPIRepo information from host API: