Nope, i am not going to teach you how to create an add-on for XBMC,
But i'm going try to provide as much useful information as possible to get you going.
Since there's so much great and helpful posts on writing addons scattered across the forum,
the aim of this thread is to collect all of them in a single post.
Before you start
Think well through what addon you want to write. Start simple, learn how XBMC reacts and how to get things working and done.
Python is an easy to learn language and there is a lot of information available on the web on how to write scripts.
Dig yourself in some short python tutorials and start exploring the possibilities. Also know the difference between scripts and plugins.
XBMC wiki pages
The XBMC wiki pages is a valuable source of information to find specific examples on creating add-ons and how to use the XBMC python modules.
Be sure to start reading the Add-on development wiki to get you going.
There is also a more specific section about python development.
Some of these pages are a bit out of date and require updating but they should still provide the needed basics. Over time we will get these pages better organised.
The best start to get going is just taking a small script that is already working and start figuring out how things are done. Change the name and add-on id that you can find in the addon.xml file and start tweaking it bit by bit until you created your own version. Just open the files included in the add-ons with a standard text editor (Notepad++ is recommended if your are using Windows.).
After you made the changes try running the add-on like you would with any other of that type.
Make sure you enable debugging so you can see in the debug log if any errors occur.
Here is a list of some simple script to get you started:
- To be added
If you are planning to create an add-on with a custom UI (not for the faint-hearted) you can find some more information about skinning here.
Make sure you read this post to avoid the most common mistake made in xbmc addons:
Presenting your add-on
Once you're well on your way, you may want to present your add-on to the outside world for testing to make sure it runs well for others to on different platforms (some scripts can be limited to a single platform of course).
Like every piece of code, your add-on will contain bugs. to assist you in squashing as much bugs as possible, you can let others test your add-on.
Don't hesitate to start a thread in our Python development area and marking your add-ons as WIP.
Do however follow our no Piracy Policy.
To get others to test your add-on there are several ways.
- Providing the URL where the source code can be found and let users manually install this. For example your github repo (or other development repo).
- Providing your add-on as a .zip file so users can use the "install from .zip" option in the XBMC add-on section. This greatly simplifies it for users that are not that familiar with how things work. You can provide the .zip file by uploading it to some hosting site (or Dropbox i.e.) where users can download it from.
- Creating your own repository which users can install and can install your add-on from there. This however requires some more knowledge of the add-on dev to get this going.
XBMC has a large and active user-base who is willing to test drive your 'work in progress' add-on
and can help you identify those bugs.
Once things are running smoothly you can request your thread to moved to the appropriate add-on section or start a fresh one and get a MOD to close the old WIP one.
Once you are confident your add-ons works like it should you can request it to be added to the "XBMC.org official repo". Be sure to read the set guidelines on the wiki before submitting it. If you have any questions about these feel free to contact the repo maintainers. Also read this thread: HOW-TO get your addon into the official repository
Our users can also help you to translate your add-on in every language XBMC supports.
All you have to do is to submit your English language file to our Transifex project. You can read more about this in the linked thread.
Submitting your add-on to the official XBMC.org repo
To make it easy for all XBMC users (not just the forum-goers) to install your add-on, we would appreciate it if you would submit your add-on to the official XBMC repository.
That way, it will be installable right from within XBMC for everyone.
To make the submission process as easy as possible we're providing a detailed list of guidelines for you to follow.
Keeping it up-to-date
Some add-on require more maintenance than others depending on what type. If you rely on internet pages you might find it that they regularly change their website which breaks the function of your add-on.
Try to find the most reliable way to keep maintenance and breakage down as much as possible. This makes it easier for you and for the users
In case of changes on the website or you find bugs or simply want to add new features, make sure you test them as good as you can. Once that's done you can submit your updated add-on to XBMC.org official repo to distribute it amongst the users. Try to keep your updates to a minimum (once or twice a month for example) but of course don't hesitate to submit an update of your add-on to prevent breakage for users
There's also a python module named Buggalo.
Quote:The buggalo script can collect various information about an
exception in a Python script as well as information about the
users system, such as XBMC and Python versions.
The collected information is then posted to the internet at a
predefined URL where the add-on author can investigate the exception.
The script is somewhat similar to posting the xbmc.log to pastebin,
but is more specialised and doesn't contain superfluous information.
It is also better integrated into the user experience, the user only
has to decide if they want to submit the bug report or not.
Read more about it here here.
Last but not least
should you ever, at any time, get stuck (we all hit the brick wall before)
feel free to ask for help in the Python Add-on Development forum.