QGIS Developers Corner¶
- Developer Guide
- Build Notes For Developers
- Coding Standards and Bug Hunting
- Coding Design Discussions
- Coding tutorials
- Tickets workflow (draft)
- Help on writing custom apps with QGIS API
- Help on writing plugins
- API Documentation and source profiling
- Miscellaneous
- Python Plugin Repositories
- Bugs
- Google Summer of Code
- QGIS Server tutorial
- QGIS GRASS Integration Disposable Locations on the Fly
- Switching from Old to New Symbology and Labeling
- New Labeling changes and roadmap
- Ideas for enhancement print composer
- API changes for version 2.0
- GUI roadmap for version 2.0
- Ideas for field validation
- Future ideas for expression builder
- Globe Plugin
- Sharing QGIS development costs
- Backward Compatibility
- Data Frames
Developers Manual¶
The Developers Manual is generated using text2tags from CODING.t2t in the QGIS sources. The Developers Manual should always reflect the most current SVN trunk build procedure - for release versions the CODING document in the sources will be generated according to the current build procedure at the time.
Building From Source¶
The Build Guide was generated using text2tags from INSTALL.t2t in the QGIS sources. The installation guide should always reflect the most current SVN trunk build procedure - for release versions the INSTALL document in the sources will be generated according to the current build procedure at the time.
Request For Comment¶
A QGIS Request For Comment (RFC) describes a major change in technology, major additions to functionality, or changes in the direction of the project. It is published on the RFC wiki page and announced on the developer and user mailing lists.
Branches Directory¶
- List of available SVN Branches
Training Guides¶
- Python Plugin Worksheet: Python_workshop_en.pdf
- QGIS API Docs
- Qt Documentation
- PyQGIS Cookbook