Gilles Dubuc 30563de71d Add file usage data to MMV metadata panel ... Interface code is its own class which does not depend on the main interface class it can be unit tested (and eventually moved into its own file to make browsing the code easier). IMO we should aim to eventually break up the interface into similar classes (with a simple init/empty/set interface + custom events where it makes sense). Also, sneak-introducing LESS! API usage could be more effective (globalusage is a separate API call; it needn't be), but we will have to rewrite that part soon anyway, so it should pass for now. Bug: 60087 Mingle: https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/44 Change-Id: Ibe5c323cdeab4a378316925f0c3efb3dc7ef5997		2014-01-30 13:03:28 +01:00
..
lightboximage.test.js	Fix bug that would cause the image to stay small	2014-01-27 10:21:38 +01:00
lightboxinterface.test.js	Test metadata visibility in fullscreen mode	2014-01-30 08:39:55 +01:00
mmv.lightboxinterface.test.js	Test metadata visibility in fullscreen mode	2014-01-30 08:39:55 +01:00
mmv.model.test.js	Moving things around for module renames	2014-01-24 09:21:16 -08:00
mmv.provider.test.js	Add file usage data to MMV metadata panel	2014-01-30 13:03:28 +01:00
mmv.test.js	Refactor image load code, add unit tests.	2014-01-30 08:51:15 +01:00
mmv.testhelpers.js	Test metadata visibility in fullscreen mode	2014-01-30 08:39:55 +01:00
mmv.ui.description.test.js	Moving things around for module renames	2014-01-24 09:21:16 -08:00
mmv.ui.fileUsage.test.js	Add file usage data to MMV metadata panel	2014-01-30 13:03:28 +01:00
multilightbox.test.js	Moving things around for module renames	2014-01-24 09:21:16 -08:00