Extension talk:Mirador

Mirador configuration options

Thanks, this is an excellent extension that widens the capabilities of our wiki.

Still cannot put together how to configure Mirador when it is called like Mediawiki extension. Configuration settings are supposed to be in src/config/settings.js, shall I add this file to the extension files and then configure? Default works fine but I would like to change interface available to the users of wiki as Mirador serves as viewer of digital resources, not the editor. Pspviwki (talk) 19:58, 4 October 2023 (UTC)

Thanks, I'm glad you find it useful! With the parser function I have tried to cover many features of the viewer in a way which might be too technical for others, although it is obviously not comprehensive. I'm not sure what you would like to see differently, but I understand you have ideas of their own in how to set up Mirador for your users. Are there any particular features you're missing but would like to see? You are free, of course, to create your own fork of the extension and edit ext.mirador.js. Rand(1,2022) (talk) 14:25, 5 October 2023 (UTC)

Thanks for reply. No forking, that would require the knowledge of writing extensions that I do not have. Example of usage on wiki page.

Example like {{#mirador:manifest=manifest.json

|theme=dark

|windowsmaximized=true

}} works fine.

What I am trying is to achieve is to customize the Mirador window for the wiki users. Some parameters respond, some do not. The aim is (if it is possible)

• Remove options Activate selection of an image region, Window options, Minimize window, Close window from the menu. Only Window views & thumbnail display would stay. (If the user by mistake closes the window, they will have empty wiki page and need to reload the page.)
• That way the sidebar with Add resource, Jump to window, Workspace settings, Workspace options would be disabled too.
• Then I would like to increase height of black background (canvas?) and make the default width of the source wider, ideally fit width. Then with increased height the toolbar for next item would be below document.
• Then update the title of the document in the menu bar as the one provided by the source is not sufficient. Once I got it working it would be made a wiki template (there is no special page for Mirador, an individual page is devoted to each resource)

I tried the following parameters

|theme=dark

|windowsmaximized=true

|allowclose=false

|allowfullscreen=false

|allowtopmenubutton=false

|hidewindowtitle=true

|singlecanvasonly=true

but not all of them work, the way I intend, I do not know if it is my usage (correct parameters?) or the way it is allowed in the extension. Pspviwki (talk) 09:18, 9 October 2023 (UTC)

Okay, you want to strip things down a bit and disallow some features, which is understandable. I didn't think it worthwhile to cover every possible parameter that Mirador has to offer, which would not have been possible anyway given the flat structure of a parser function as opposed to the nested JSON structure. That said, I could still add in a couple of those paramaters you mentioned (allowclose, allowfullscreen) and I have been considering alternative ways of supporting fuller, more complex configurations. I'll let you know! Rand(1,2022) (talk) 14:45, 9 October 2023 (UTC)

Hi @Pspviwki, I just released a new version. While it does not offer everything you asked about, the parser function does come with several new configuration options that should let you trim things down (menu components and features). Documentation is available on the Github. Rand(1,2022) (talk) 15:06, 16 November 2023 (UTC)

Thanks, it works like clockwork. Pspviwki (talk) 15:21, 18 November 2023 (UTC)