Reorganisation of plugins/trunk

[Technology]

https://openkore.svn.sourceforge.net/sv ... ins/trunk/
Its currently a mess.
Some plugins became obsolete like: doCommand.pl
I suggest we move each plugin to a specifical folder inside plugins/trunk.
This way, we will not only be able to add a readme and examples for usage/configuration of the plugin.
But we will actually be able to download the specifical plugin we want to trough SVN.

I'll do it, if you guys agree.


For forum moderators:
when the change is made please search forum for "plugins/trunk/" and change that to the plugins new paths.
thanks

[kali]

I agree

[h4rry84]

Agreed, better with making new link Wiki Page for plugins/trunk list

[Technology]

With openkore 3.0 coming up, we needed to reorganize the plugins so we can make tags for 2.x and 3.x.
This is because the design of 3.0 will differ allot from 2.x

A big part of the plugins is moved to this location:
https://openkore.svn.sourceforge.net/sv ... re/plugins

As you might notice, the documention is far from complete.
The readme.txt doc's are only basic, the wiki should have a plugin section in the future,
where every plugin will be explained. (like the macro plugin)
Feel free to complete wherever you can and test the plugins.

In the manual, these plugins should be documented and further devided into different sections:
- anti anti bot (there should be a module (.pm) that contains re-usable functions for the different plugins here)
- notification
- encryption
- datamining
- AI manipulating
- other...

Plugin developers should be given svn access too imo.


TODO: remove the plugins from: https://openkore.svn.sourceforge.net/svnroot/openkore

[EDIT]
copying the whole openkore svnroot to my harddrive atm

[kali]

Most of the plugin authors offer one-time submission of plugins and don't come back again ever to maintain them.

On the other hand, I've seen a few that actually maintain their plugins and then given SVN write access.

[Technology]

moved all plugins from svnroot/openkore/ to svnroot/openkore/plugins
edited wiki page: http://www.openkore.com/wiki/index.php/ ... VN_modules

forum mods & doc writers:
please change for every pluginName on the forum/wiki

from path: openkore/pluginName
to path: openkore/plugins/pluginName

hint: search for: https OR viewvc

Devs:
are there any other plugins worth moving to SVN?

In my opinion its not usefull to have a different version system for plugins.
ex. pluginName v1.0.2

Here's an idea to resolve possible incompabilities quickly and to be able to link version control on plugins<->openkore:

* openkore/plugins/pluginName/trunk: should contain the plugin that is supported by the latest openkore SVN (openkore/openkore/trunk)
users will be able to report incompabilities

* openkore/plugins/pluginName/tags: should contain the stable versions of the plugin that is supported by specific older milestone openkore versions (openkore/openkore/tags)
ex. openkore/plugins/pluginName/tags/2.0.6.1_v1 should contain the first compatible version of the plugin with OK 2.0.6.1

* openkore/plugins/pluginName/branch: should contain:
- branches of the plugin for branches of openkore (ex. experimental-ai2008, untill it will become stable enough to become SVN trunk version)
- experimental features in a plugin (for testing purposes, ex. macro plugin mods)

early support for still unstable OK branches:
ex. openkore/plugins/pluginName/branch/experimental-ai2008

deviates from 2.0.6.1_v1 in just 1 experimental feature:
ex. openkore/plugins/pluginName/branch/2.0.6.1_v1_featureName

Note:
Also, with OK 3.0 there will come a different generation of plugins, wich should not be called plugins any longer.
They will be more like pluggable modules that will have more control than the regular plugins.