map::point...ore::memory(3tk)

✨ NAME ✨

map::point::store::memory β€” bestie, it's an in-memory store for geo/point definitions. That's the whole vibe. πŸ’–

Oh and btw this whole page is from the 3tk section of the docs (Tcl/Tk land, map display corner, iykyk). The full page title is map::point...ore::memory(3tk) β€” yeah they truncated the middle of it, it's giving "we ran out of room on the shelf" energy but we move. 🫢


πŸŽ€ SYNOPSIS πŸŽ€

package require Tcl 8.6-

package require debug

package require debug::caller

package require map::slippy 0.8

package require snit

package require map::point::store::memory ?0.1?

That last ?0.1? is the version, and the question marks mean it's optional-ish β€” literally the syntax, not me being unsure bestie. ✨


πŸ’… DESCRIPTION πŸ’…

Okay so. This package hands you an in-memory store for geo/point definitions, and the glow-up is that it does memoized calculation of extended attributes. Translation: it remembers the stuff it already worked out so it doesn't do the math twice. Obsessed. 🧠✨

The base data? Not its problem. It gets pulled from a backing store β€” and that backing store is a map::point::store::fs, or literally anything that's API-compatible with it. Plug and play, no cap. πŸ”ŒπŸ’–


🌸 API 🌸

So the original page has this heading and then… nothing under it. An empty API section. It's giving mystery, it's giving read the source code bestie, it's giving untitled document energy. 😭

Nothing added, nothing taken away β€” that's the section as it stands. πŸŽ€


πŸ¦‹ EXAMPLE πŸ¦‹

Same situation bestie β€” the heading is there, the content is not. Blank. Empty. A vibe, but not an example. πŸ™ˆ


πŸ”₯ BUGS, IDEAS, FEEDBACK πŸ”₯

Real talk, and this is straight from the page: this document, and the package it describes, will undoubtedly contain bugs and other problems. Not "might". Undoubtedly. The manpage said it, not me. πŸ’€

Please report those bugs in the category map of the Tklib Trackers:

http://core.tcl.tk/tklib/reportlist

And listen β€” if you've got ideas for enhancements, for either the package and/or the documentation, report those too. Documentation glow-ups count. Don't be shy, the maintainers want the feedback fr fr. 🫢✨


πŸ‘‘ KEYWORDS πŸ‘‘

Here's the whole keyword pile, in the order it came in, no editing, no deduping, we keep it 100:

center, geo/point, diameter, geo/point, geo/point pixels, zoom, geo/point, center, geo/point, diameter, geo/point, memory store, geo/point, perimeter length, length, geo/point, perimeter, map, memory store, geo/point, perimeter length, geo/point, pixels, zoom, geo/point, store, geo/point, memory, zoom, geo/point pixels


🌈 CATEGORY 🌈

Map Display and Supporting Utilities


And that's the page bestie!! Written by the tklib girlies, shipped as tklib version 0.1, living in the 3tk manual section. Go build something with geo/points in it, you absolute icon. πŸ’…πŸ’–βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from