Mikaela
/
Limnoria
mirror of https://github.com/Mikaela/Limnoria.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

PLUGIN_TUTORIAL: Remove references to the old website. 

Signed-off-by: James Vega <jamessan@users.sourceforge.net>
This commit is contained in:
James Vega 2009-12-10 08:09:11 -05:00
parent 3689460d0f
commit 0806c0bbc3
1 changed files with 6 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/PLUGIN_TUTORIAL
View File

@ -144,10 +144,7 @@ everything that wasn't contributed by someone else was done by the main author.
For now we have no contributors, so we'll leave it blank. For now we have no contributors, so we'll leave it blank.
Lastly, the __url__ attribute should just reference the download URL for the Lastly, the __url__ attribute should just reference the download URL for the
plugin. We encourage you to use the supybot.com website for distributing plugin. Since this is just an example, we'll leave this blank.
plugins and have gone to great lengths to make distributing them nice and easy
to do so. Since this is just an example, we'll leave this blank, but
supybot-plugin-create shows an example URL of a plugin home here on supybot.com
The rest of __init__.py really shouldn't be touched unless you are using The rest of __init__.py really shouldn't be touched unless you are using
third-party modules in your plugin. If you are, then you need to take special third-party modules in your plugin. If you are, then you need to take special
@ -551,7 +548,7 @@ wisdom with regards to Supybot plugin-writing.
the core developers. We (the Supybot dev team) can't possibly document the core developers. We (the Supybot dev team) can't possibly document
all the awesome things that Supybot plugins can do, but we try. all the awesome things that Supybot plugins can do, but we try.
Nevertheless there are some really cool things that can be done that Nevertheless there are some really cool things that can be done that
aren't very well-documented on this site. aren't very well-documented.
* Hack new functionality into existing plugins first if writing a new * Hack new functionality into existing plugins first if writing a new
plugin is too daunting. plugin is too daunting.
@ -560,14 +557,10 @@ wisdom with regards to Supybot plugin-writing.
first point above, the developers themselves can help you even more than first point above, the developers themselves can help you even more than
the docs can (though we prefer you read the docs first). the docs can (though we prefer you read the docs first).
* Publish your plugins on our website. We made some custom stuff on the * Share your plugins with the world and make Supybot all that more
website just to cater to publishing plugins. Use it, share your plugins attractive for other users so they will want to write their plugins for
with the world and make Supybot all that more attractive for other users Supybot as well.
so they will want to write their plugins for Supybot as well.
* Read, read, read all the documentation on our website. I just spent a * Read, read, read all the documentation.
lot of time getting a bunch of these tutorials out and getting things up
to date, so while Supybot documentation in the past hasn't been stellar,
it certainly is very good now.
* And of course, have fun writing your plugins. * And of course, have fun writing your plugins.