One of the original goals was to have a modules/plugins system to have 'optional features' that a user could install, and not have the client be bloated with features that a user does not want or use. It also opened up the possibility of non-gtorrent developers easily extending the client. It's pretty much the same thing that rutorrent does with their plugins.
Using Lua for the plugins was talked about, because it's very lightweight to ship the interpreter, but other languages like Python would work too.
Ideas for modules that could be implemented is:
RSS automation
Traffic monitoring
Torrent swarm statistics
GeoIP
Automated tools (moving, renaming etc.)
Or just copy most of the stuff here
I think we need to decide how (or if) a modules system is going to be implemented into the clients, hopefully in a toolkit-independent way. The earlier this is done, the better, as it allows for a lot more work to start happening once it is finished.
One of the original goals was to have a modules/plugins system to have 'optional features' that a user could install, and not have the client be bloated with features that a user does not want or use. It also opened up the possibility of non-gtorrent developers easily extending the client. It's pretty much the same thing that rutorrent does with their plugins.
Using Lua for the plugins was talked about, because it's very lightweight to ship the interpreter, but other languages like Python would work too.
Ideas for modules that could be implemented is:
I think we need to decide how (or if) a modules system is going to be implemented into the clients, hopefully in a toolkit-independent way. The earlier this is done, the better, as it allows for a lot more work to start happening once it is finished.