Mirage Configuration and Customization

Introduction

Mirage is a new XMLUI theme, added in DSpace 1.7 by @mire. The code was mainly developed by Art Lowel. The main benefits of Mirage are:

• Clean new look and feel.
• Increased browser compatibility. The whole theme renders perfectly in today's modern browsers (Internet Explorer 7 and higher, Firefox, Safari, Chrome, ...)
• Easier to customize.
• Enhanced Performance

Configuration Parameters

Technical Features

Look & Feel

• The Simple Item Display underwent a full redesign to provide visitors with a clearer overview of available metadata and associated files.
• Item list views can now be displayed in two distinct different styles. Switching between these styles is possible with the new dspace.cfg parameter 'xmlui.theme.mirage.item-list.emphasis'
  • The 'metadata' list style includes item abstracts in the listing and is suited for scientific articles.
  • The 'file' list style immediately shows you whether files are attached to the items, by displaying a large thumbnail icon for each of the items.

Structural enhancements for easier customization.

• Based on the new restructured dri2xhtml base templates. Templates in the theme, overriding the new base templates, are located in the same folder hierarchy to ensure full transparency.
• Automated browser feature detection for improved browser compatibility.
  • In other themes, user agent detection is used to identify which browser version your user is using. Based on the result of this detection, the theme would use a different cascaded style sheet (CSS) to render a compatible page for the visitor. This approach has 2 major issues:
    • User agent detection isn't very reliable
    • Maintaining these different CSS files is a maintenance nightmare for developers, especially when using features from newer browsers.
  • Mirage applies two novel techniques to resolve these issues
    • For compatibility with older Internet Explorer browsers, conditional comments give the body tag a class corresponding to the version of IE
    • modernizr is used to detect which css features are available in the user's browser. This way you can target all browsers that support a certain feature using css classes, and rules affecting the same element can be put together in the same place for all browsers.
• CSS files are now split up according to function instead of browser. style.css will now fit most needs for customization. Following additional CSS files are included, but will rarely need to be changed:
  • reset.css ensures that browser-specific initializations are being reset.
  • base.css contains a few base styles
  • helper.css contains helper classes to deal with specific functionality.
  • handheld.css and print.css enable you to define styles for handheld devices and printing of pages.
• jQuery and jQueryUI are included by default. To avoid conflicts the authority control javascript has been rewritten to use jQuery instead of Prototype and Script.aculo.us.

Enhanced Performance

• Concatenation and Minification techniques for css and js files.
  • The IncludePageMeta has been extended to generate URL's to the concatenated version of all css files using the same media tag.
  • The ConcatenationReader has been created to return concatenated and minified versions of the css and js files.
  • Once js and css files have been minified and concatenated, they are being properly cached. As a result, the minification and concatenation operations only need to happen once, and do not include performance overhead.
  • Caution: when minification is enabled, all code-comments will be removed. This could be a problem for comments containing copyright notices, so for files with those comments you should disable minification by adding '?nominify' after the url e.g.
    <map:parameter name="javascript" value="lib/js/jquery-ui-1.8.5.custom.min.js?nominify"/>
    
  • Disabled by default, these features need to be enabled in the configuration using the properties 'xmlui.theme.enableConcatenation' and 'xmlui.theme.enableMinification'
  • These features can be enabled for other themes as well, but will require an alteration of the theme's sitemap.
• Javascript references are included at the bottom of the page instead of the top. This optimizes page load times in general.
  

Troubleshooting

Errors using HTTPS

DSpace 1.7.0 ships with a hardcoded http:// link for JQuery, causing problems for users running 1.7.0 Mirage on HTTPS. While awaiting the implementation of this fix in an upcoming release, you can solve in the following file: lib/core/page-structure.xsl, addJavascript template. In this file, you will need to replace

<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js">&#160;</script>

with

       <script type="text/javascript">
            <xsl:text disable-output-escaping="yes">var JsHost = (("https:" == document.location.protocol) ? "https://" : "http://");
            document.write(unescape("%3Cscript src='" + JsHost + "ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js' type='text/javascript'%3E%3C/script%3E"));</xsl:text>
        </script>

Thanks Peter Dietz for providing this fix. Note: This issue is resolved in 1.7.1