website rev 508
en: Update devel page (partial)
| author | Paul Issott <paul@slitaz.org> |
|---|---|
| date | Sat Jun 13 21:39:44 2009 +0000 (2009-06-13) |
| parents | 83d68707e682 |
| children | 26540b3c7fa2 |
| files | en/devel/index.html |
line diff
1.1 --- a/en/devel/index.html Sat Jun 13 15:54:51 2009 +0000 1.2 +++ b/en/devel/index.html Sat Jun 13 21:39:44 2009 +0000 1.3 @@ -9,7 +9,7 @@ 1.4 <meta name="robots" content="index, follow, all" /> 1.5 <meta name="revisit-after" content="7 days" /> 1.6 <meta name="expires" content="never" /> 1.7 - <meta name="modified" content="2008-07-16 21:45:00" /> 1.8 + <meta name="modified" content="2009-06-13 21:15:00" /> 1.9 <meta name="author" content="Christophe Lincoln"/> 1.10 <meta name="publisher" content="www.slitaz.org" /> 1.11 <link rel="shortcut icon" href="../../favicon.ico" /> 1.12 @@ -76,14 +76,19 @@ 1.13 <h2><font color="#df8f06">SliTaz Developers corner</font></h2> 1.14 1.15 <ul> 1.16 + <li><a href="#kiss">KISS and comply to standards.</a></li> 1.17 <li><a href="#tank">Build host & home.</a></li> 1.18 <li><a href="#repos">Mercurial repositories.</a></li> 1.19 + <li><a href="#iconv">Implementation of iconv().</a></li> 1.20 <li><a href="#pkgs">Tazpkg packages.</a></li> 1.21 + <li><a href="#pkgs-naming">Naming of packages.</a></li> 1.22 <li><a href="#website">Website Management.</a></li> 1.23 + <li><a href="#xhtml">xHTML coding style.</a></li> 1.24 <li><a href="../mailing-list.html">Mailing List.</a></li> 1.25 <li><a href="../doc/cookbook/wok-tools.html">Wok & Tools.</a></li> 1.26 <li>Mercurial Repositories: <a href="http://hg.slitaz.org" >hg.slitaz.org</a></li> 1.27 - <li>SliTaz Laboratories: <a href="http://labs.slitaz.org/">labs.slitaz.org</a></li> 1.28 + <li>SliTaz Laboratories: <a href="http://labs.slitaz.org/">labs.slitaz.org</a></li> 1.29 + <li><a href="http://labs.slitaz.org/wiki/distro">Developers Wiki</a></li> 1.30 </ul> 1.31 1.32 <p> 1.33 @@ -102,6 +107,17 @@ 1.34 and the <a href="../mailing-list.html">Mailing List</a>. 1.35 </p> 1.36 1.37 +<a name="kiss"></a> 1.38 +<h3>KISS and comply to standards</h3> 1.39 +<p> 1.40 +Keep it simple: follow the best standards, carefully draft and write 1.41 +high quality documentation, provide a stable and robust system and keep 1.42 +the <em>rootfs</em> on the LiveCD light enough to run on machines with at 1.43 +least 128 MB RAM. It's also possible to use GTK+2, Dialog, SHell scripts, 1.44 +or PHP coding tools on the distribution. The idea is not to duplicate and 1.45 +to think small... 1.46 +</p> 1.47 + 1.48 <a name="tank"></a> 1.49 <h3>Tank - Build host & home</h3> 1.50 <p> 1.51 @@ -186,6 +202,14 @@ 1.52 <li><code>hg head</code> : Display the last log.</li> 1.53 </ul> 1.54 1.55 +<a name="iconv"></a> 1.56 +<h3>Implementation of iconv()</h3> 1.57 +<p> 1.58 +SliTaz uses iconv() provided by GNU glibc - some packages that offer 1.59 +<code>libiconv</code> must use the version of glibc (<code>glibc-locale</code>). 1.60 +There is therefore no longer a libiconv package (1.2 MB) in SliTaz. 1.61 +</p> 1.62 + 1.63 <a name="pkgs"></a> 1.64 <h3>Tazpkg Packages</h3> 1.65 <p> 1.66 @@ -214,6 +238,15 @@ 1.67 exists to help you get started. 1.68 </p> 1.69 1.70 +<a name="pkgs-naming"></a> 1.71 +<h3>Naming of packages</h3> 1.72 +<p> 1.73 +In most cases the package name is the same as the source, except for 1.74 +Python modules, Perl, PHP, Ruby and Lua. For example, the package 1.75 +providing a Kid template system written in Python and XML is named: 1.76 +<code>python-kid</code>. 1.77 +</p> 1.78 + 1.79 <a name="website"></a> 1.80 <h3>Website Management and Books</h3> 1.81 <p> 1.82 @@ -226,7 +259,45 @@ 1.83 $ hg clone http://repos.slitaz.org/website 1.84 </pre> 1.85 1.86 -<h4>Diff and patch</h4> 1.87 +<a name="xhtml"></a> 1.88 +<h3>xHTML coding style</h3> 1.89 +<p> 1.90 +The pages and different <em>books</em> are coded in xHTML 1.0 1.91 +transitional. The colors for the <code>body</code> and the titles 1.92 +are placed directly on the page so the links are easy to follow. 1.93 +The title of level 1 is used only once (at the top), level 2 is 1.94 +the title of the document and levels 3 and 4 are then used for 1.95 +the subtitles. If a list is used instead using smart anchors; 1.96 +then that starts at the top, just after the title of level 2. 1.97 +Paragraphs are contained in the tags <code><p></p></code>. 1.98 +For indentation, we use tabs - the reason being semantics and to take 1.99 +up less space in terms of octets (bytes). To put code, like the name of 1.100 +a command inside a paragraph: <code><code></code> is the preferred 1.101 +method. To view commands or to utilize a terminal, the web pages use 1.102 +<code><pre></code> to display the formatted text. Example: 1.103 +</p> 1.104 +<pre> 1.105 + $ command 1.106 +</pre> 1.107 +<p> 1.108 +To view text that can be copied and pasted, such as scripts, 1.109 +bits of code, sample configuration files, etc - we also use 1.110 +<code><pre></code>, but with a CSS class named "script". Example: 1.111 +</p> 1.112 +<pre class="script"> 1.113 +<pre class="script"> 1.114 + 1.115 +code... 1.116 + 1.117 +</pre> 1.118 +</pre> 1.119 +<p> 1.120 +The <em>emphasized</em> words put themselves in the tag <code><em></code> 1.121 +and internal links are relative. Remember to check the validity 1.122 +of the code via the online <em>validator</em> of the W3C. 1.123 +</p> 1.124 + 1.125 +<h3>Diff and patch</h3> 1.126 <p> 1.127 The utilities <code>diff</code> and <code>patch</code> are command-line tools 1.128 for creating and implementing a file containing differences between two files. 1.129 @@ -254,7 +325,7 @@ 1.130 <!-- Start of footer and copy notice --> 1.131 <div id="copy"> 1.132 <p> 1.133 -Last modification : 2008-07-16 21:45:00 - 1.134 +Last modification : 2009-06-13 21:15:00 - 1.135 <a href="#top">Top of the page</a> 1.136 </p> 1.137 <p>