Archive talk:HOW-TO:Write plugins for XBMC: Difference between revisions
Jump to navigation
Jump to search
>Atrent (redesign required) |
>Atrent No edit summary |
||
| Line 1: | Line 1: | ||
This page is very badly designed, it mixes many layers of knowledge: | This page is very badly designed, it mixes many layers of knowledge: | ||
- python | - python | ||
- python editor | - python editor | ||
- traffic sniffing | - traffic sniffing | ||
- plugin writing | - plugin writing | ||
Instead it should only delve into details about "how to write a plugin", taking for granted knowledge about the rest | Instead it should only delve into details about "how to write a plugin", taking for granted knowledge about the rest | ||
An "object oriented" approach would be better, explaining the meaning an expected behavior of the methods that must be implemented in the plugin to make xbmc accept it | |||
Revision as of 16:17, 8 February 2011
This page is very badly designed, it mixes many layers of knowledge:
- python
- python editor
- traffic sniffing
- plugin writing
Instead it should only delve into details about "how to write a plugin", taking for granted knowledge about the rest
An "object oriented" approach would be better, explaining the meaning an expected behavior of the methods that must be implemented in the plugin to make xbmc accept it