kittyfisto / metrolib Goto Github PK

Not all points are equal and sometimes it's important to have some points always be on top of other points (because they represent more important things, etc...).

A user shall be able to assign an importance to points (probably an integer), the higher the importance the more to the front it will be rendered.

Todo: Decide how (and if at all) this shall interact with features of other layers.

Add documentation for every public class.
Add examples for every public control including images.

Add overview image top level read me.

The visibility of a line series should be toggleable without having to remove it from the list of line series.

Currently, each LineChart instance is triggered by the same timer, causing them to update at slightly different times (is noticeable when charts show a sliding window).

Instead, all charts should update at the very same time.

It shall be possible to assign labels to point features. If possible, labels should be of any type and be displayed with a ContentPresenter. Labels shall not overlap each other and not overlap other features.

An appropriate algorithm shall be designed which ensures that labels are laid out without violating these two constraints. If no solution can be found, then some labels shall not be drawn.

The map view currently doesn't do anything but wasting space: It shall now be able to display tiles from a web mapping service (such as various OSM servers).

Whereas the search control features a magnifying glass, the search control should feature a funnel icon. It should be placed where the delete button is and be hidden when the control is focused.

A new layer shall be added which allows simple points to be displayed using a custom WPF DataTemplate. In this first step, the map view shall display all points, regardless of whether or not they overlap. This will be addressed in a separate issue.

It should be possible to inspect the actual value(s) when the mouse hovers over a specific point.
It should be possible to configure if a simple intersection with all series at that X is performed (so that multiple values can be inspected at the same time).

Unless I'm missing something the controls don't react to mouse events.

Currently tiles are always downloaded from their source server. They shall also be cached locally (if desired) both in-memory and on disk. This should be achieved using IsabelDb (which can do both over the same interface).

This is also a good point to move all map related controls into a different project and nuget package (e.g. Metrolib.Map) due to having more dependencies.

The icon should be moved to the right side of the control and be hidden when text is entered or the control is focused.

It's inconvenient that Metrolib doesn't work without log4net.

In order to increase visibility, the displayed angular length of a slice should be bigger than its calculated length, in case the calculated length would result in a slice that is too small to be visible.

(This is obviously dependent on the radius of the pie).

All assemblies in this nuget package should be strong signed.