HTTPS clone URL
Subversion checkout URL
- Community FAQ
- Project: Groogy's Development Environment
- Project: sfeMovie
- Project: Thor
- Project: Zoost and Zoom
- Source: 2D Vector Manipulation
- Source: Analog Clock
- Source: AnimatedSprite
- Source: Audio Player
- Source: Basic Game Engine
- Source: Bouncing ball
- Source: Chronometer
- Source: Color Gradient
- Source: cubic bezier curve
- Source: CurvedText
- Source: Draw Rounded Rectangle
- Source: Drawable Line Shape
- Source: Fader
- Source: FPS
- Source: FrameClock
- Source: GTK integeration
- Source: GTK SFMLWidget
- Source: HeatHazeShader
- Source: High Performance Sprite Container
- Source: HSL Color
- Source: Jukebox
- Source: KeyValues
- Source: Letterbox effect using a view
- Source: Line segment with thickness
- Source: line with thickness
- Source: Load Image From Resource
- Source: Loading Images in a Thread
- Source: Looping Music
- Source: Masking Alpha Blending
- Source: MP3 Player
- Source: Mp3 Soundfile Reader
- Source: Network Chat Example
- Source: Particle System
- Source: Particle System for SFML 2
- Source: PhysicsFS Input Stream
- Source: Radial Gradient Shader
- Source: Round Ended Lines
- Source: Ruby Light Manager
- Source: Settings Parser
- Source: SFML PhysFS
- Source: ShaderTileMap
- Source: Simple Collision Detection
- Source: Simple Collision Detection for SFML 2
- Source: Simple File Logger (by mateandmetal)
- Source: Smart ResourceManager
- Source: Sprite Animated
- Source: Sprite Sheets
- Source: Sprite3d
- Source: TileMap
- Source: TileMap Render
- Source: Verlet Physic
- Source: VertexVector
- Source: wxScrolledSFMLWindow
- Source: Zoom View At (specified pixel)
- Style Guide
- Tutorial: Basic Game Design
- Tutorial: Basic Game Engine
- Tutorial: Build SFML's dependencies
- Tutorial: Build your SFML project with CMake
- Tutorial: Building SFML for Android
- Tutorial: CEGUI and SFML
- Tutorial: Change Cursor
- Tutorial: Compile and Link SFML with Qt Creator
- Tutorial: Correctly Display Accents
- Tutorial: Create and Use SetIcon
- Tutorial: Drawable Group
- Tutorial: Dynamic colorful tile based lighting
- Tutorial: Image Manager
- Tutorial: Installing SFML dependencies
- Tutorial: Link SFML with Qt Creator
- Tutorial: Manage different Screens
- Tutorial: Manage dynamic key binding
- Tutorial: Object Properties
- Tutorial: Play Sine Wave
- Tutorial: Play Sine Wave (OCaml)
- Tutorial: SFML.Net on OSX
- Tutorial: Using View
Clone this wiki locally
This wiki is maintained by the SFML community, and as a consequence you are allowed (and encouraged) to edit or add any relevant contribution. However, it is recommended to follow the general organisation and page layout, in order to keep a consistent and pleasant wiki for all. In other words, don't put your source code under the tutorials section.
There's no restriction on the whole wiki for creating or editing pages; you can even create new categories for subjects that don't exist yet, if you think it's worth sharing.
You are also free to edit pages created by other users, if you have relevant additions or corrections to make.
You are encouraged to share anything related to SFML with no restriction: tutorials, source codes, links, tips and tricks, personal projects, … as long as you find it relevant.
English is the main language of this wiki. However, you can provide translations of certain pages if you want. But keep in mind that the english version has to be the default/main one, if other languages are provided they must only appear as translations of the corresponding english page. Never make wiki links directly point to non-english pages.
When you edit content, please leave a comment in the dedicated text field at the bottom of the page (above the Save and Preview buttons) when you edit it, to let others know what you've done.
If you have requests, suggestions or questions about this wiki, feel free to create a new discussion on the Wiki section of the forum. You should also use this forum to report any bug encountered while using the wiki.
With the change from GitHub on how titles of wiki pages are being handled it's no longer possible to keep the address of a page short and handy, but we still want to have a nicely organized wiki, so read the new rules below.
When you create a link to a new page, you must separate the label of the link (for example A class for animated sprites) and the address of the page (for example Tutorial:-Animated-Sprite). This allows to use descriptive link labels while keeping the name of pages simple enough. Keep in mind that the address will get automatically generated and you don't have to add the dashes for the page name, but instead use spaces.
The example above would translate into the following wiki syntax:
[A class for animated sprites](Tutorial:-Animated-Sprite)
Since the page name is now automatically set as the title, you can't avoid adding spaces which then get translated into dashes. Please try to keep the characters count low and try to avoid special characters like slashes, underscores, etc.
This wiki is "flat": you can't create sections/directories, all pages have to be under the "wiki/" root. To keep them organized, please follow this pattern to name them: "wiki/Category:-Page-Name". Categories are the main categories listed on the home page: Tutorial, Source, Project (FAQ should have no child page).
There's no option to upload images or other types of files directly to the wiki, you must instead find an external storage for them. If you do so, please make sure that the file will always be available, and not be automatically deleted from the website where you host it after a certain amount of days.
Well, in fact there's a way to upload files directly to the wiki, but it's kind of unusable: you must clone the wiki's repository, commit your file and push it. That's far from convenient.
If you upload files directly here, please limit yourself to images of acceptable sizes.