<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-forward-container">FYI<br>
<br>
-------- Weitergeleitete Nachricht --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Betreff:
</th>
<td>Calamares branding components</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Datum: </th>
<td>Thu, 16 Oct 2014 18:40:06 +0200</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Von: </th>
<td>Teo Mrnjavac <a class="moz-txt-link-rfc2396E" href="mailto:teo@kde.org"><teo@kde.org></a></td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">An: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:calamares-dev@googlegroups.com">calamares-dev@googlegroups.com</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>Hello everyone,
this is to let you know that as of today the branding mechanism has been
merged.
A prominent element of the whole rationale behind Calamares has always been to
discourage the proliferation of branches and forks and enable everyone to
share and work on common general-purpose solutions which can then be
customized to suit individual needs and tastes.
The branding system now allows distributors to customize strings and graphics
in their Calamares deployment without forking and without writing C++ or
Python code. Right now Calamares comes with a "default" branding component, it
lives in src/branding/default and is chosen at the end of settings.conf. A lot
of strings and images are not customizable yet, they can become so over time
as we notice unbranded strings and images which someone might want to make
brandable.
A branding component is a directory, which contains a YAML file branding.desc
and other files as needed.
To roll out your own branding component "mybranding", you only need to provide
a directory called "mybranding" with a branding.desc file inside. This file is
the branding descriptor. It must specify "mybranding" as componentName, plus
your strings and paths to other resources. All paths in branding.desc must be
relative to the branding component directory. A badly formatted branding.desc,
or invalid paths in branding.desc, will result in Calamares quitting on
startup with an error message in the terminal.
If you choose to maintain your branding component in Calamares master, you
only need to put it in src/branding, together with the default one (feel free
to submit a pull request). The Calamares build system will then pick it up and
install it in /usr/share/calamares/branding.
If you choose to maintain it outside the Calamares repo and ship it yourself,
you can deploy it in /etc/calamares/branding as well.
Cheers,
--
Teo Mrnjavac
<a class="moz-txt-link-freetext" href="http://teom.org">http://teom.org</a> | <a class="moz-txt-link-abbreviated" href="mailto:teo@kde.org">teo@kde.org</a>
--
You received this message because you are subscribed to the Google Groups "Calamares development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a class="moz-txt-link-abbreviated" href="mailto:calamares-dev+unsubscribe@googlegroups.com">calamares-dev+unsubscribe@googlegroups.com</a>.
To post to this group, send email to <a class="moz-txt-link-abbreviated" href="mailto:calamares-dev@googlegroups.com">calamares-dev@googlegroups.com</a>.
To view this discussion on the web visit <a class="moz-txt-link-freetext" href="https://groups.google.com/d/msgid/calamares-dev/1463180.ln8DUW99Mm%40haven">https://groups.google.com/d/msgid/calamares-dev/1463180.ln8DUW99Mm%40haven</a>.
For more options, visit <a class="moz-txt-link-freetext" href="https://groups.google.com/d/optout">https://groups.google.com/d/optout</a>.
</pre>
<br>
</div>
<br>
</body>
</html>