Mikaela/Limnoria
1
0
Fork 0
mirror of https://github.com/Mikaela/Limnoria.git synced 2025-01-09 11:42:35 +01:00
Code Issues Projects Releases Wiki Activity

Updated DocBook translation

Browse Source
This commit is contained in:
Daniel DiPaolo 2004-09-05 04:52:58 +00:00
parent 6a4567df32
commit 8b150d33c3
1 changed files with 88 additions and 73 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
docs/DocBook/capabilities.sgml
View File

@ -20,6 +20,11 @@
<date>18 Feb 2004</date>
<revremark>Initial Docbook translation</revremark>
</revision>
<revision>
<revnumber>0.2</revnumber>
<date>04 Sep 2004</date>
<revremark>Update Docbook translation</revremark>
</revision>
</revhistory>
</articleinfo>
<sect1>
@ -86,7 +91,7 @@
But that's not all! The capabilities system also supports
<emphasis>Channel</emphasis> capabilities, which are
capabilities that only apply to a specific channel; they're of
the form <capability>#channel.capability</capability>.
the form <capability>#channel,capability</capability>.
Whenever a user issues a command to the bot in a channel, the
command dispatcher also checks to make sure the user doesn't
have the anticapability for that command <emphasis>in that
@ -107,7 +112,7 @@
anticapability, then the bot checks to see if the user issued
the command over a channel, and if so, checks to see if the
user has the antichannelcapability for that command,
<capability>#baz.-bar</capability>. If so, again, he returns
<capability>#baz,-bar</capability>. If so, again, he returns
right then and there and doesn't even think about responding
to the bot. If neither of these anticapabilities are present,
then the bot just responds to the user like normal.
@ -119,7 +124,7 @@
<sect2>
<title>A programmer's perspective</title>
<para>
From a programmatical perspective, capabilties are easy to use
From a programming perspective, capabilties are easy to use
and flexible. Any command can check if a user has any
capability, even ones not thought of when the bot was
originally written. Commands/Callbacks can add their own
@ -140,6 +145,7 @@
bot to follow for users that haven't yet registered in his
user database.
</para>
</sect2>
<para>
It's really a revolution!
</para>
@ -165,22 +171,22 @@
</para>
<para>
People who are to administer channels with the bot should have the
<capability>#channel.op</capability> capability -- whatever
<capability>#channel,op</capability> capability &ndash; whatever
channel they are to administrate, they should have that channel
capability for <capability>op</capability>. For example, since I
want <nick>inkedmn</nick> to be an administrator in
<channel>#supybot</channel>, I'll give him the
<capability>#supybot.op</capability> capability. This is in
<capability>#supybot,op</capability> capability. This is in
addition to his <capability>admin</capability> capability, since
the <capability>admin</capability> capability doesn't give the
person having it control over channels.
<capability>#channel.op</capability> is used for such things as
giving/receiving ops, kickbanning people, lobotomizing the bot,
ignoring users in the channel, and managing the channel
capabilities. The <capability>#channel.op</capability> capability
capabilities. The <capability>#channel,op</capability> capability
is also basically the equivalent of the owner capability for
capabilities involving <channel>#channel</channel> &ndash;
basically anyone with the <capability>#channel.op</capability>
basically anyone with the <capability>#channel,op</capability>
capability is considered to have all positive capabilities and no
negative capabilities for <channel>#channel</channel>.
</para>
@ -201,6 +207,15 @@
[dict go] /] [dict go]</literal>.
</para>
</sect1>
<sect1>
<title>Other capabilities</title>
<para>
Other plugins may require different capabilities; the
<plugin>Factoids</plugin> plugin requires
<capability>#channel,factoids</capability>, the <plugin>Topic</plugin>
plugin requires <capability>#channel,topic</capability>, etc.
</para>
</sect1>
</article>