Gecko [ www.smkibnusinagenteng.sch.id ]

Name	Size	Permission
Auth.php	2.51 KB	-rw-r--r--
Auth.xml	1.2 KB	-rw-r--r--
Build.php	2.58 KB	-rw-r--r--
Build.xml	388 B	-rw-r--r--
Channels.php	32.66 KB	-rw-r--r--
Channels.xml	4.12 KB	-rw-r--r--
Common.php	8.02 KB	-rw-r--r--
Config.php	15.1 KB	-rw-r--r--
Config.xml	3.3 KB	-rw-r--r--
Install.php	49.81 KB	-rw-r--r--
Install.xml	8.49 KB	-rw-r--r--
Mirror.php	4.4 KB	-rw-r--r--
Mirror.xml	617 B	-rw-r--r--
Package.php	39.21 KB	-rw-r--r--
Package.xml	7.05 KB	-rw-r--r--
Pickle.php	15.52 KB	-rw-r--r--
Pickle.xml	1.15 KB	-rw-r--r--
Registry.php	45.2 KB	-rw-r--r--
Registry.xml	1.75 KB	-rw-r--r--
Remote.php	29.28 KB	-rw-r--r--
Remote.xml	3.23 KB	-rw-r--r--
Test.php	11.85 KB	-rw-r--r--
Test.xml	1.6 KB	-rw-r--r--

Code Editor : Config.xml

<commands version="1.0">
 <config-show>
  <summary>Show All Settings</summary>
  <function>doConfigShow</function>
  <shortcut>csh</shortcut>
  <options>
   <channel>
    <shortopt>c</shortopt>
    <doc>show configuration variables for another channel</doc>
    <arg>CHAN</arg>
   </channel>
  </options>
  <doc>[layer]
Displays all configuration values.  An optional argument
may be used to tell which configuration layer to display.  Valid
configuration layers are &quot;user&quot;, &quot;system&quot; and &quot;default&quot;. To display
configurations for different channels, set the default_channel
configuration variable and run config-show again.
</doc>
 </config-show>
 <config-get>
  <summary>Show One Setting</summary>
  <function>doConfigGet</function>
  <shortcut>cg</shortcut>
  <options>
   <channel>
    <shortopt>c</shortopt>
    <doc>show configuration variables for another channel</doc>
    <arg>CHAN</arg>
   </channel>
  </options>
  <doc>&lt;parameter&gt; [layer]
Displays the value of one configuration parameter.  The
first argument is the name of the parameter, an optional second argument
may be used to tell which configuration layer to look in.  Valid configuration
layers are &quot;user&quot;, &quot;system&quot; and &quot;default&quot;.  If no layer is specified, a value
will be picked from the first layer that defines the parameter, in the order
just specified.  The configuration value will be retrieved for the channel
specified by the default_channel configuration variable.
</doc>
 </config-get>
 <config-set>
  <summary>Change Setting</summary>
  <function>doConfigSet</function>
  <shortcut>cs</shortcut>
  <options>
   <channel>
    <shortopt>c</shortopt>
    <doc>show configuration variables for another channel</doc>
    <arg>CHAN</arg>
   </channel>
  </options>
  <doc>&lt;parameter&gt; &lt;value&gt; [layer]
Sets the value of one configuration parameter.  The first argument is
the name of the parameter, the second argument is the new value.  Some
parameters are subject to validation, and the command will fail with
an error message if the new value does not make sense.  An optional
third argument may be used to specify in which layer to set the
configuration parameter.  The default layer is &quot;user&quot;.  The
configuration value will be set for the current channel, which
is controlled by the default_channel configuration variable.
</doc>
 </config-set>
 <config-help>
  <summary>Show Information About Setting</summary>
  <function>doConfigHelp</function>
  <shortcut>ch</shortcut>
  <options />
  <doc>[parameter]
Displays help for a configuration parameter.  Without arguments it
displays help for all configuration parameters.
</doc>
 </config-help>
 <config-create>
  <summary>Create a Default configuration file</summary>
  <function>doConfigCreate</function>
  <shortcut>coc</shortcut>
  <options>
   <windows>
    <shortopt>w</shortopt>
    <doc>create a config file for a windows install</doc>
   </windows>
  </options>
  <doc>&lt;root path&gt; &lt;filename&gt;
Create a default configuration file with all directory configuration
variables set to subdirectories of &lt;root path&gt;, and save it as &lt;filename&gt;.
This is useful especially for creating a configuration file for a remote
PEAR installation (using the --remoteconfig option of install, upgrade,
and uninstall).
</doc>
 </config-create>
</commands>

${this.title}

Code Editor : Config.xml