Projet

Général

Profil

Révision 00c2605a

Ajouté par Assos Assos il y a environ 9 ans

Weekly update of contrib modules

Voir les différences:

drupal7/sites/all/modules/advanced_help/help/ini-file.html
1
The advanced help configuration file is in simple .ini file format, divided into sections for each help file, plus an optional section for global settings that might be inherited for each help file.
1
<p>The advanced help configuration file is in simple .ini file format.
2
It has an optional section for global settings that might be inherited
3
for each help file, followed by sections for each help file.</p>
2 4

  
3
The first line of an advanced help ini file should be ;&#x24;Id &#x24; which will be a comment providing the CVS identifier for the file. The ; indicates a comment character. Anything after the ; will be ignored.
5
<p>Global settings may be put into a section named <code>[advanced help
6
settings]</code>.  This means that this name is reserved and it cannot
7
be a help file in any module or theme. The following settings may be
8
set in this section, with the default value (if any) in brackets.</p>
4 9

  
5
Global settings may be put into a section named <strong>[advanced help settings]</strong> -- this means that this name is reserved and it cannot be a help file in any module. The following settings may be set in this section:
6 10
<dl>
7
<dt><strong>line break</strong></dt>
8
<dd>If set to any value, the line break filter will be applied to all help files defined by this module, unless that help file specifically is set otherwise. By default, the line break filter is not applied; however, help files can be much easier to write with the line break filter on.</dd>
9
<dt><strong>navigation</strong></dt>
10
<dd>If set to true, the navigation will be displayed at the end of the help topic: previous topic, next topic, and child topics.</dd>
11
<dt><strong>css</strong></dt>
12
<dd>Specify a css file that will be used for all help files (unless overridden), including the .css extension. This .css file must reside in the help directory along with the .html files, and will not be affected by translation.</dd>
13
<dt><strong>name</strong></dt>
14
<dd>May be set to override the module name as displayed in both the module index as well as the navigation and breadcrumb trail. In general this does not need to be set, but a few modules may want to use a more friendly name than appears in the .info file.</dd>
15
<dt><strong>index name</strong></dt>
16
<dd>This may be set to change the name of the module in the module index. It overrides the 'name' setting above, as well as the module name in its .info file.</dd>
17
<dt><strong>hide</strong></dt>
18
<dd>This may be used to hide a module in the module index. This is particularly useful for modules who insert their help files into the hierarchy of another module, as might be done by modules that extend Views or CCK. By setting "hide = TRUE" the module will not appear as its own entry.</dd>
11
<dt><code>line break</code> (FALSE)</dt>
12
<dd>If set, the line break filter will be applied to all help files
13
defined by this module or theme, unless that help file specifically is
14
set otherwise.  The line break converts line breaks
15
into <code>br</code> and <code>p</code> tags automatically.</dd>
16

  
17
<dt><code>navigation</code> (TRUE)</dt>
18
<dd>If set, this navigation will be displayed at the end of the topic:
19
<em>previous topic</em>, Up (parent), <em>next topic</em>.</dd>
20

  
21
<dt><code>css</code></dt>
22
<dd>Specify a css file that will be used for all help files (unless
23
overridden), including the .css extension. This .css file must reside
24
in the help directory along with the .html files, and will not be
25
affected by translation.</dd>
26

  
27
<dt><code>name</code></dt>
28
<dd>May be set to override the module or theme name as displayed in
29
both the module/theme index as well as the navigation and breadcrumb
30
trail. Usually, this is not set, but for some projects you may want to
31
use a more friendly name than appears in the project's .info file.</dd>
32

  
33
<dt><code>index name</code></dt>
34
<dd>This may be set to change the name of the module or theme in the
35
module/theme index. It overrides the <code>name</code> setting above,
36
as well as the project's name in its .info file.</dd>
37

  
38
<dt><code>hide</code> (FALSE)</dt>
39
<dd>This may be used to hide a module or theme in the module/theme
40
index. This is particularly useful for modules who insert their help
41
files into the hierarchy of another module or theme, as might be done
42
by modules that extend <strong>Views</strong> or derived themes that
43
extend base themes like <strong>Zen</strong>. By setting this to TRUE
44
the project will not appear as its own entry.</dd>
19 45
</dl>
20 46

  
21
Each section after that will correspond to a single help file, and each one may have the following settings:
47
<p>Each section after that will correspond to a single help file for a
48
single topic.  It starts with the topic name in square brackets
49
(e.g. <code>[ini-file]</code>).  The following settings may be set for
50
each file/topic, with the default value (if any) in brackets.</p>
51

  
22 52
<dl>
23
<dt><strong>title</strong></dt>
24
<dd>The title of the topic, presented to the user and used in links. If you have special characters in your title, be sure to enclose it in quotes.</dd>
25
<dt><strong>file</strong></dt>
26
<dd>The filename, without the .html extension, used for the topic. This is optional; if not specified, the topic name wil be the file name.</dd>
27
<dt><strong>weight</strong></dt>
28
<dd>The weight, used for sorting topics on the administration page. Defaults to 0 of unspecified. Items with the same weight are sorted alphabetically.</dd>
29
<dt><strong>parent</strong></dt>
30
<dd>The topic ID to use in a hierarchy; children will be listed beneath parents in the topic list, and will have the parent in their breadcrumb trail. You may parent this topic to another module's topic by using module%topic as the identifier. For example, 'views%display' will make this a child of the 'display' topic in the 'views' module.</dd>
31
<dt><strong>line break</strong></dt>
32
<dd>If set to true, linebreaks will be converted into br and p tags automatically. If unspecified, will default to off. Set to 0 to disable the filter if this has been turned on in the global settings.</dd>
33
<dt><strong>css</strong></dt>
34
<dd>Specify a css file that will be used for this file. This .css file must reside in the help directory along with the .html files. This will override any .css file added by the global system.</dd>
35
<dt><strong>popup width</strong></dt>
36
<dd>The width in pixels of the popup window.  Defaults to 500 if unspecified.</dd>
37
<dt><strong>popup height</strong></dt>
38
<dd>The height in pixels of the popup window.  Defaults to 500 if unspecified.</dd>
53
<dt><code>title</code></dt>
54
<dd>The title of the topic, presented to the user and used in
55
links. If you have special characters in your title, be sure to
56
enclose it in quotes.  (This setting is currently not optional.)</dd>
57

  
58
<dt><code>file</code> (topic name)</dt>
59
<dd>The filename, without the .html extension, used for the file with
60
the help text for the topic. This is optional; if not specified, the
61
topic name wil be the file name.</dd>
62

  
63
<dt><code>weight</code> (0)</dt>
64
<dd>The weight, used for sorting topics on the administration
65
page. The default is 0 (zero) if unspecified. Items with the same weight
66
are sorted alphabetically.</dd>
67

  
68
<dt><code>parent</code></dt>
69
<dd>The topic ID to use in a hierarchy; children will be listed
70
beneath parents in the topic list, and will have the parent in their
71
breadcrumb trail. You may parent this topic to a topic in another
72
module or theme by using <code>module%topic</code>
73
or <code>theme%topic</code> as the identifier,
74
where <code>module</code> or <code>theme</code> is the project's short
75
name. For example if parent is set to, '<code>views%display</code>',
76
the topic will be regarded as a child of the
77
<code>display</code> topic in the <strong>Views</strong> module.</dd>
78

  
79
<dt><code>line break</code> (FALSE)</dt>
80
<dd>Set the line break filter for this topic. Set to FALSE to disable
81
the line break filter if this has been turned on in the global
82
settings.</dd>
83

  
84
<dt><code>css</code></dt>
85
<dd>Specify a css file that will be used for this file. This .css file
86
must reside in the help directory along with the .html files. This
87
will override any .css file added by the global settings.</dd>
88

  
89
<dt><code>popup width</code> (500)</dt>
90
<dd>The width in pixels of the popup window.</dd>
91

  
92
<dt><code>popup height</code> (500)</dt>
93
<dd>The height in pixels of the popup window.</dd>
39 94
</dl>
40 95

  
41
For example, here is a version of the <strong>advanced_help.help.ini</strong> file:
96
<p>For example, here is a version of the <code>advanced_help.help.ini</code> file:</p>
97

  
42 98
<pre>
99
[readme]
100
title = README
101
weight = -11
102

  
43 103
[using-advanced-help]
44
title = "Using advanced help"
104
title = Using advanced help
45 105
weight = -10
46 106

  
47 107
[translation]
......
49 109

  
50 110
[ini-file]
51 111
title = Help .ini file format
112
line break = FALSE
113

  
114
[why-advanced-help]
115
title = Why advanced help?
52 116
line break = TRUE
53
</pre>
117
</pre>

Formats disponibles : Unified diff