Source code

The source code for Flint is released under the MIT open-source license. The MIT license is a permissive license, allowing you to use Flint within your work provided you retain the license and copyright notice with the source code.

The source code for Flint is available through three sources.

Downloads

The latest version of Flint is available from the downloads section on the GitHub repository as four separate downloads.

• Flint version 4.0.1 source code for Flash or Flex
• Flint version 4.0.1 swc for Flash or Flex
• Flint version 4.0.1 documentation
• Flint version 4.0.1 examples

Downloads of earlier versions are available in the Github downloads.

GitHub

All active development of Flint takes place on GitHub. If you want the latest, cutting edge version of Flint then you need to check-out the GitHub repository. This is available through Git (git://github.com/richardlord/flint) or Subversion (http://svn.github.com/richardlord/flint).

Subversion access via GitHub is read-only and not browsable. If you try to browse the repository (and many Subversion tools will try to do so without you asking) then you will get an error. A simple checkout (svn checkout http://svn.github.com/richardlord/flint) will work.

The various examples in the examples section of this site are also available on GitHub.

Google code

The Google code repository used to be the master repository for Flint prior to moving Flint to GitHub. Now, the Google code repository is maintained as a way for users to download the latest release of Flint. Every release of Flint is copied to the Google code repository so it can be checked out by any users who prefer this method for accessing the source code.

Contributing

If you wish to contribute to the Flint project your best option is to fork the project on GitHub and let me know when you have features for me to pull back into the master repository. Please note that any items added to the master repository will be made available to all under the MIT licence to provide consistent licensing across the project. Your name will appear in the source code as the developer of the feature you contribute.

I am also happy to receive contributions as code posted to the forum but this is only practical for small contributions.