This theme is not owned by me, and is made available as a convenience under the licenses of the various authors.
It's been tested with Roundcube Webmail 1.4.9
It consists of a compiled copy of the elastic theme from roundcube/roundcubemail@06eb080e82d3b546343e44475a412274d018eadb including its various dependencies.
To the extent anything additional I've done is separately licensable from the component parts, I release it under the terms of the UNLICENSE.
To install in a mail-in-a-box, (to be safe) first set the theme to something
other than elastic. Then log into the box via SSH and:
# backup the included theme
sudo tar ZacfP elastic.backup.tar.gz /usr/local/lib/roundcubemail/skins/elastic/
# remove included theme
sudo rm -r /usr/local/lib/roundcubemail/skins/elastic
# install this theme
sudo git clone https://github.com/pckilgore/roundcube-elasticdark.git \
/usr/local/lib/roundcubemail/skins/elasticDepending on the amount of caching in front of your box, you may need to refresh/logout/wait a bit, then login and select the theme for use in roundcube.
This skin package contains a theme for the Roundcube Webmail software. It can be used, modified and redistributed according to the terms described in the LICENSE section.
For information about building or modifying Roundcube skins please visit https://github.com/roundcube/roundcubemail/wiki/Skins
The contents of this folder are subject to the Creative Commons Attribution-ShareAlike License. It is allowed to copy, distribute, transmit and to adapt the work by keeping credits to the original authors in the README.md file. See http://creativecommons.org/licenses/by-sa/3.0/ for details.
This folder also contains code licensed separately:
- Bootstrap Framework 4 from https://github.com/twbs/bootstrap
- FontAwesome 5 fonts from https://fontawesome.com/
- Roboto font from https://google-webfonts-helper.herokuapp.com/fonts/roboto?subsets=cyrillic,latin-ext,cyrillic-ext,latin,greek,greek-ext
-
Supported browsers: IE11+, Edge, Last 2 versions for Chrome/Firefox/Safari, Android Browser 5+, iOS Safari 9+.
-
Skin color palette changes and other css modifications can be done via _styles.less and _variables.less files. Where you can overwrite all variables and add custom styles.
-
Minimum supported screen width is 240px (note that even if the device screen resolution is e.g.320x372 changing the text size in device settings will reduce the resolution)
-
Every page (which is not a frame) has following required structure:
<body>
<div id="layout">
<div id="layout-menu"></div>
<div id="layout-sidebar"></div>
<div id="layout-list"></div>
<div id="layout-content"></div>
</div>
</body>
where #layout-sidebar and #layout-list are optional. Which element of the #layout will be displayed
as a main view on mobile devices can be defined by adding selected class to it.
-
The
<html>element will receive special classes that will be updated on resize or orientation change:touch: A touch device, screen width <= 1024px,layout-large: Screen width > 1200px,layout-normal: Screen width <= 1200px and >= 768px,layout-small: Screen width < 768px and > 480px,layout-phone: Screen width <= 480px.
Frames will have the same classes applied as their parent windows.
-
Every button, that is not nor should have inner element for the button label.
-
Every iframe need to be wrapped by an element with
iframe-wrapperclass. It is required to have proper scrolling on mobile devices. -
Special attributes:
-
data-hidden: Makes a menu entry/button hidden on specified screen sizes. Can be used for example for functionality not implemented or that has no sense on phones or touch devices. Contains a comma-separated list following values:large(width > 1200px),big(width > 768px),small(width =< 768px),phone(width =< 480px),lbs(width > 480px). -
data-content-button: Makes the action button with this attribute to be copied to the content frame header on small/phone screens.
-
-
Special URLs: In phone mode we display Prev/Next navigation buttons below the content preview frame. We do this e.g. for mail preview or contact preview. Plugins should use _action=add* or _action=create* or _nav=hide in the frame URL if the navigation should be hidden, which is the case when you create a content object.
-
Dark mode: In dark mode html element will have
dark-modeclass assigned. It is possible to disable dark mode using less variable@dark-mode-enabled. Optiondark_mode_supportin meta.json controls addition of the mode switch in the menu.