Development

Process

Here the team collects everything about navit development.

Planning

• Brainstorming

• Usability

• Changelog

Coding

• Programming guidelines

• Commit guidelines

• Eclipse

• Submitting patches

internals:

• Plugin

• Graphic driver development

• GUI development

• Map driver

• Search Development

• Routing

external control:

• Embedding

• Dbus

• Bookmarks Development

• Command interface

Building

• CMake

• Dependencies

• Build server

• Build logs

Ressources

• Translations

• Internal GUI/Menu configurations

• OSD Layouts

• Vehicle profile flags

• Configuration

Testing

This is detailed in the Testing and CI strategy page.

Packaging

We currently have an build server, but the package generation is quiet scattered. We might change this to a continuous integration server later.

Platforms

• Linux development

• Android development

  • Augmented Reality

• Ångström development

• OpenEmbedded development

• Openmoko development

• Scratchbox development

• TomTom development

• Windows development

• WinCE development

• MacOS development

Maps

• OpenStreetMap

• Maps

• Item def.h

Architecture

Navigation systems offer a lot of functionality. To be flexible and allow a whole community to work on the code, Navit is split into several components and plugins.

Maps storage

• Binfile

• CSV

• Textfile

Visual

• Map Graphics drivers

• Map style

• Custom POIs

• • OSD - for internal UI

Routing

Search

• address

• POIs

Speech

• driving instructions

• TTS

GPS

Internals

• Configs

• Bookmarks

• Command interface