XBMC v13.1 "Gotham" has been released! See Gotham FAQ for details.

Developing XBMC for Mac

From XBMC
Jump to: navigation, search
Home icon grey.png   ▶ Development ▶ Developing XBMC for Mac


Cleanup.png This page or section may require cleanup, updating, spellchecking, reformatting and/or updated images. Please improve this page if you can. The discussion page may contain suggestions.

Development:

Team-XBMC have ported the XBMC Media Center software to Mac OS X some time ago.

XBMC is a huge open source project and it takes loads of people working together to maintain it for all platforms, that is why Team-XBMC is always on the lookout for C/C++ programmers to volunteer in assisting us with the development of XBMC. Whether you have contributed to The XBMC Project in the past or not, please consider doing so now.


Those of you who are completely unfamiliar with XBMC can get a good overview of it on XBMC and XBMC FAQ.


Contents

1 End-users (non-programmers)

You can help too by downloading XBMC for Mac, testing it, and reporting bugs and issues. Also, spread the word about XBMC for Mac to your friends and family, we are sure they will enjoy it too.

2 Developers (programmers)

You should be proficient in C/C++ programming language, and allthough not really required knowledge of OpenGL or multimedia programming is a plus, as well as prior cross-platform or porting development experience.

The Mac OS X development platform is Mac OS X 10.6 32-bit x86-Intel. There are Xcode project files available in our git repo

3 Hardware requirements

4 Detailed technical information

For more details please visit the Development Notes section of this manual.

5 Source code

The XBMC source code is in our git repository on github.com. Full instructions for compiling/builing XBMC under Mac is available here:

6 General guidelines

6.1 User-friendliness is next to godlyness

One major ongoing goal of Team-XBMC has always been to make XBMC and its user interface feel even more intuitive and user-friendly for its end-users, based on the KISS (Keep It Simple Stupid) principle of simplicity. It is our belief that usability is the most important aspect of a media center like XBMC. Many other media center projects make user interface decisions by developers, who often have little experience in user interface design. In contrast, Team-XBMC does its best to listen to XBMC's end-users to learn how XBMC is actually being used and how we can improve the user experience. We also aim to do regular overhauls, improving existing features/functions, and scrapping outdated code and features/functions (as "too much stuff" adds unnecessary complexity and can thus also be a bad thing). Everything should be made as simple as possible, but no simpler.

6.2 XBMC as a whole must...

  • First and foremost be aimed at a large-screen (28" or more) 10-foot user interface for the living-room experience.
    • Large menus, text/fonts and buttons that is designed to be navigated by a hand-held remote-control.
  • Be focused around the main features of playing music, watching movies, recorded television broadcasts, and viewing pictures.
    • XBMC may be capable of converging other things but those things should never take over the main focus in the interface.
  • Be easy to install, set up and maintain (so that our valuable end-users do not get fed up with it and quit).
  • Have an user interface that is simple and intuitive enough so that less tech-savvy people are not intimidated by it.
  • Be able to play audio and video files that have been encoded using DivX, XviD, etc. directly out-of-the-box.
  • Be able to organize audio and video files in an easy and user-friendly way.
  • Use standards and be consistent, (the Music section can for example not use completely different controls from the Video section).
  • Perform actions in the GUI with as few 'clicks' as possible.
  • Be aimed at an international audience, internationalization and localization by supporting different languages, timezones and other regional differences
  • Require little to no non-GUI configuration (and all such non-GUI configuration should be done in just one file: advancedsettings.xml).
  • Be beautiful to look at, after all we hope you will be using it a lot!

6.3 Team-XBMC members should always strive to

  • Promote open source - XBMC is based on the ideas of FOSS (free open source software), licensed under the GPL and builds partly on other open source projects which we do our best to support. The GPL should be respected at all times. All code should be committed to the XBMC project’s git repo before any public binaries are released.
  • Promote the sharing of knowledge and collaboration - Through the use of information sharing tools and practices XBMC is a collaborative environment.
  • Understand that development is a team effort - Treating our users as co-developers has proven to be the most effective option for rapid development. Always strive to work as a team at all times. Actively promote discussion on new features and bug fixes, and respect others comments and criticisms with replies in a timely fashion.
  • Apply the Law of Diminishing Return - The majority of the effort should be invested in implementing features which have the most benefit and widest general usage by the community.
  • Try to make all code, feature, and functions to be platform agnostic - XBMC is a multi-platform software, thus any single platform specific features should be discussed with other team members before implemented. Major features should be developed in a separate branch or committed in small increments so that other members have the opportunity to review the code and comment on it during development.
Personal tools
Namespaces

Variants
Actions
Navigation
Wiki help
Toolbox