Jaime_Pomales, here are some points that will get you started with adding support for the plugins you mentioned (I assume you have good knowledge of css and js):
Plugins use their own html code, css rules, javascript and images located in the plugin directories to render their output. We shouldn't modify any of the plugin files directly, so all our modifications need to be done in the skin's css and js files: outlook/skin/skin_desktop.css (or _mobile.css for mobile devices) and outlook/skin/skin.js.
(If you need unminified versions of the files, we can send them to you, just open a ticket in our helpdesk at
http://roundcubeskins.net.)
IconsThe Outlook skin uses Font Awesome for the icons (
http://fortawesome.github.io/Font-Awesome.) To replace a png icon loaded by a plugin with a flat icon, you'll need to remove the background image specified by the plugin and load the icon character into the element, for example:
#some-element {
background-image: none;
}
#some-element:before {
font-family: FontAwesome;
content: "\f073";
}
(You may need to add some additional styling, but these are the basics. To find the codes for the icons, look in the file outlook/skin/icons/css/font-awesome.css)
If the plugin uses html img tags, replacing the icons won't be as straightforward, but it's still doable.
ColorsThe skin has 18 color schemes to chose from and each scheme has 4 colors that can be applied to html elements. You'll find the list of the schemes, their colors and the applied styles in the file skins.js. The first color in the scheme is used to create a body element class that can be later used in the css rules (for example color-8d2297.)
If you want to apply a color to an element, simply add it to the styles in skins.js. There are ready-made rules for applying the active scheme's colors to the elements' background, borders and text. You can of course create your own rules if you wish.
Incompatible pluginsSome plugins don't support any other skins than larry and classic. They will check if the current skin name is "larry" and if not, they will assume it's "classic." And since the layout positioning of classic is different than larry (and our skins are based on larry,) they will render their output in the wrong places.
If any of your plugins use hard-coded checks for "larry" and render things incorrectly, our plugin rcs_skins can fix this for you. Simply add the name of the incompatible plugin to the $plugins array in plugins/rcs_skins/rcs_skins.php. This will make the incompatible plugin believe it's running under "larry" and so it will render its output in the proper places.
This will also fix the problem with the missing skin template files in the plugin directions that you mentioned in your previous post (you won't need to symlink the larry directories to outlook.)
Hope this will be enough to get you started. Thanks for using our skins! If you need any more help, let us know.