folium VS sciter

A good thing to try would be to look over the folium documentation on their GitHub Page, Folium. For help with code you could ask ChatGPT to explain what you're interested in using their docs.

I currently utilize Folium for a work project but would like to move it out of Folium into something that supports API requests for real-time data and vector tiles instead of raster.

If you know Python you can use Folium produce Leaflet maps without using Javascript. I'm not sure if the updating functionality you require is possible, but could be worth a look.

Try Folium, here are some examples.

For our visualizations we will be using Folium. This is a description from the authors:

I'm mapping some election results, and trying to create a diagrammatic representation of who voted for whom, and where. I'm using Python, and I can create a perfectly respectable initial map (without Voronoi diagrams) using its folium package, with OpenStreetMap tiles. See https://numbersandshapes.net/posts/post_election_swings/.

Look in the folium package. https://python-visualization.github.io/folium/

Choropleth maps are a quick and easy way to visualize a numeric variable geographically. I love the ease and interactivity of most functions from the folium module, but the choropleth method lacks interactivity and clarity in the legend.

> wondering if css and svg could be used as abstraction over graphics and UI libraries

There's another project called Sciter that uses CSS to target native graphics libraries: https://sciter.com

> I wonder how hard it was to implement css. I've heard it can be pretty complex.

It was hard, but the biggest barrier is the obscurity of the knowledge.

Text layout is the hardest, because working with glyphs and iterating them in reverse for RTL is brain-breaking. And line wrapping gets really complicated. It's also the most obscure because nobody has written down everything you need to know in one place. After I finished block layout early on, I had to stop for a couple of years (only working a few hours a week though) and learn all of the ins, outs, dos, and don'ts around shaping and itemizing text. A lot of that I learned by reading Pango's [1] source code, and a lot I pieced together from Google searches.

But other than that, the W3C specifications cover almost everything. The CSS2 standard [2] is one of the most beautiful things I've ever read. It's internally consistent, concise, and obviously the result of years of deliberation, trial and error. (CSS3 is great, but CSS2 is the bedrock for everything).

[1] https://gitlab.gnome.org/GNOME/pango/

otherwise, if we have only retained mode as in browsers, we will need to modify the DOM heavily and create temporary elements for handles.

[1] https://sciter.com

I've still never used it but I've long been curious about Sciter:

https://sciter.com

These bullet points are exactly what I did in Sciter (https://sciter.com)

- Windowing

-- Tabs

-- Menus

-- Painting

-- Animation

-- Text

-The compositor

-Handling input

-- Pointer input

-- Keyboard input

- Accessibility

- Internationalization and localization

- Cross-platform APIs

- The web view

- Native look and feel

On top of that DOM and CSS implementations to achieve declarative UI. And JS as a languuage behind UI - declarative in some sense way of defining UI behavior.

I'm not sure if it can support all the libraries but yes it can be used to make desktop apps. Theres also Sciter.

https://sciter.com/