mosra / kompas-core Goto Github PK

The home directory is retrieved using some crazy winapi call, but the call doesn't retrieve anything.

TCHAR h[MAX_PATH];
if(!SUCCEEDED(SHGetFolderPath(NULL, CSIDL_PERSONAL, NULL, 0, h)))
    return "";

Qt uses for the same thing (QDesktopServices) function SHGetSpecialFolderPath with totally different syntax, but the function is not in defined in shlobj.h (technically is, but some preprocessor black magic hides it).

Some maps provide time-based data, for example weather maps.These maps should expose that to user, so it's possible to view data from different date/time. The map should somehow provide timestamps for which the data are available:

• All timestamps (bad for lots of timestamps),
• Range and interval of timestamps (bad for irregular steps)

Examples of timeline-enabled data:

• Weather maps (limited 15 minutes steps back, forecast every 6 hours)
• Time-based path (irregular steps...)
• Planet position (infinitely small steps, infinite range)

Implement an interface for hierarchical caching, either as filesystem cache or network cache.

Hierarchy should be defined with sequence of set() and get() functions, for example:

Child get(Node node);
set(Node node, Child child);

Plugin interfaces which need cached data access implement with these functions their own hierarchy and it should be possible for caching plugin to implement all or only some hierarchies.

1. Define an interface - 10%
2. Implement an plugin (in kompas-plugins) - 70%
3. Make use of caching at least in AbstractRasterModel - 20%

Embedded resources such as plugin metadata in static plugins are not visible on N900.

Implement interface for plugins with vector data - unlike raster map plugins vector data are not limited only to maps. Because of that the vector plugin interface should be divided into two parts:

• Interface for data access - "model"
• Interface for viewing and managing the data (e.g. in kompas-qt) - "view"

Vector data can be really anything:

• vector maps
• points of interest
• webcams, geotagged images
• 360° panoramatic view / "street-view"
• 3D objects
• paths
• ...

Data source:

• from URL
• from file
• "direct input" (e.g. URL which has path coordinates encoded in itself)

For one model there can be multiple viewers, for e.g. path there can be direct in-map viewer or widget with elevation, length, time statistics.