- 14 Apr, 2022 4 commits
-
-
We can already access all the information by other means.
-
Corentin Noël authored
Document the basics of each classes.
-
-
Corentin Noël authored
It is a now widely supported editor configuration. The spec is available at https://editorconfig.org
-
- 13 Apr, 2022 1 commit
-
-
James Westman authored
Use the .osd style class for the zoom in/out buttons in ShumateSimpleMap.
-
- 17 Mar, 2022 1 commit
-
-
- 03 Mar, 2022 1 commit
-
-
James Westman authored
Change the URL template placeholders from #X#, #Y#, and #Z# to {x}, {y}, and {z}. This format is used, for example, in Leaflet and the TileJSON specification. Fixes #33.
-
- 01 Mar, 2022 1 commit
-
-
Add methods to get and set a global user agent for libshumate. Fixes #32.
-
- 30 Jan, 2022 1 commit
-
-
James Westman authored
That way, markers can be built from xml correctly.
-
- 26 Jan, 2022 1 commit
-
-
Corentin Noël authored
It is not really required these days.
-
- 18 Jan, 2022 1 commit
-
-
James Westman authored
-
- 13 Jan, 2022 5 commits
-
-
Corentin Noël authored
Avoid crashing the demo application by simply implementing it.
-
Corentin Noël authored
Use SemVer as our versioning scheme, and release libshumate 1.0.0.alpha.1 as the first alpha version of the libshumate 1 API. The first beta will be 1.0.0.beta.1 and the first stable will be 1.0.0.
-
Corentin Noël authored
-
This widget is designed for simple use cases of libshumate, mainly in apps where maps aren't the main focus. It takes care of license text, source switching, base vs. overlay layers, etc. but offers somewhat less control. The individual child widgets that make up the widget are still accessible. Also removes the custom styling on the compass widget, because it doesn't look right where I put it in the ShumateSimpleMap. Fixes #20.
-
This reverts commit ec655268.
-
- 10 Jan, 2022 1 commit
-
-
TAO ZUHONG authored
-
- 08 Jan, 2022 1 commit
-
-
James Westman authored
-
- 03 Jan, 2022 1 commit
-
-
Corentin Noël authored
This makes sure that implementing this function is possible with bindings. Signed-off-by:
Corentin Noël <corentin.noel@collabora.com>
-
- 22 Dec, 2021 1 commit
-
-
James Westman authored
If ShumateCompass:viewport was set to the same viewport twice in a row, the notify::rotation signal would be disconnected, but not reconnected.
-
- 01 Dec, 2021 1 commit
-
-
Bilal Elmoussaoui authored
-
- 19 Nov, 2021 1 commit
-
-
Corentin Noël authored
-
- 18 Nov, 2021 1 commit
-
-
James Westman authored
Split the network source into separate classes for fetching data, rendering raster tiles, and rendering vector tiles. This makes the code much more modular and organized, especially since vector tiles are about to get even more complicated. ShumateDataSource is a new abstract class that retrieves tile data. It has a built-in implementation, ShumateTileDownloader, which takes over the network part of ShumateNetworkTileSource. ShumateRasterRenderer is a ShumateMapSource that provides tiles by reading image files from a ShumateDataSource. Similarly, ShumateVectorRenderer is a ShumateMapSource that provides tiles by rendering vector tiles. This commit also modifies the network source to use the tile URL as a file cache key, rather than the map source ID. This is because, with vector tiles, two different map sources may use the same set of tiles.
-
- 17 Nov, 2021 1 commit
-
-
Andy Holmes authored
Avoid int * int multiplication warnings by performing the calculation on gsize values.
-
- 12 Nov, 2021 2 commits
-
-
Marcus Lundblad authored
Avoid int * int multiplication warnings by performing the calculation on gsize values.
-
Marcus Lundblad authored
Declare local variable m_per_pixels as double to avoid potential overflow when promoting the result when muliplying with a float value passing the result to "log" (double precision).
-
- 08 Nov, 2021 2 commits
-
-
James Westman authored
Added a build option, -Dvector_renderer, to enable or disable the experimental vector tile renderer. It defaults to false.
-
James Westman authored
Don't build the docs in flatpak because the Python packages needed aren't in the runtime.
-
- 01 Nov, 2021 9 commits
-
-
Removed the {append|prepend|remove}_map_source methods from ShumateLicense and replaced them with a `map` property. The license monitors changes to the map layers through a new `layers-changed` signal and updates the license text automatically. This also required adding `license` and `license-uri` properties to ShumateLayer. Currently only ShumateMapLayer implements them and they are taken from the map source.
-
These expressions are used primarily to show only certain features in a layer (for example, a "landuse" layer might only cover certain landuses).
-
-
-
Added fill layers. This involves parsing a vector tile in protobuf format and converting the features inside into cairo paths. vector_tile.pb-c.{c,h} is the generated protobuf parsing code. Since the spec is not likely to change, I checked these files into git instead of generating them as part of the build. This commit introduces dependencies on libprotobuf-c and libprotobuf.
-
Add layers to ShumateVectorStyle. It reads these layers from a Mapbox Style Specification JSON file. So far, only background layers are supported because there is no protobuf/MVT parsing capability yet.
-
This commit adds a dependency on json-glib.
-
This error domain is used for errors during style parsing.
-
Here begins the epic vector tiles merge request... ShumateVectorStyle is the main entry point of the vector renderer. By setting the `style` property of a ShumateNetworkTileSource, tiles will be interpreted as protobuf/Mapbox Vector Tile formatted files rather than raster images. So far, though, none of that is implemented and ShumateVectorStyle contains a dummy renderer.
-
- 14 Oct, 2021 2 commits
-
-
James Westman authored
-
The viewport was accidentally initialized twice, leaking the first one.
-
- 06 Oct, 2021 1 commit
-
-
Niels De Graef authored
The whole `SECTION` block is a gtk-doc specific annotation. Just immediately document the class/struct/interface with the usual docs syntax and gi-docgen will know what to do with it. There's also no worrying about exposed structs, since there are none in libshumate, and even if there were, you would still have to document them in the GIR. Finally, use proper linking as specified by the gi-docgen tutorial.
-