Home
Welcome to the cgeo wiki!
If you are a c:geo user, maybe you want to meet some of the people from the development team? Most other information in the wiki is targeted at developers.
Do you want to join the team of developers/tester of cgeo? We have a set of coding conventions to reduce confusion and reformatting when submitting pull requests. Please adhere to these conventions.
If you are not used to git, don't fear, we have some guidelines for git beginners. When writing code for the project, you should know which branch to target, therefore please check how to get a bug fix into the release.
Some major ideas that will take some time to implement and therefore fall out of the category 'issue' are recorded here as Things To Do and Future Ideas. Please have a look at the [[Request-For-Co mments]] page and leave your comments there.
From time to time (2018-20: 1-4 month distance), we release a new version on the PlayStore.
Translation of the strings used in the c:geo app and plugins as well as the Playstore descriptions are handled via Crowdin.
The Crowdin integration is described here: Translation-(L18N).
We have a notification system in place to inform the users of new releases and of problems in the current release.
Information
Development
- Join the team
- Development Environment
- GitHub
- Coding conventions
- design conventions
- Working on c:geo for git beginners
- Creating custom Android icons
- Translation
- Release Preparation
- Continuous Integration
- c:geo notifications
- Logging
Usage
- Creating offline maps
- Send a debug log to the developers
- 'New Map' feature description
- Presenting a demo
Technical documentation
- Heading
- Screen densities
- GPS low power mode
- DB Schema
- Map usages
- Disk Usage Structure
- Trackable parsing
- UnifiedMap
Misc
Outdated: