Replies: 1 comment
-
|
@AdMub, I struggle with providing early feedback, because of the number of requests we get. So, I defer to only providing feedback to things that are completely public out of fairness to provide discoverability. I did look at your PR, and appreciated it. I am going to close this discussion. @wang-boyu, feel free to reopen if you see fit. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi @wang-boyu and @jackiekazil!
Following up on my recently merged PR (#309) implementing
get_random_xy, I have spent the last week deeply analyzing the architectural needs for the "Modernizing Mesa-Geo" project.Following the community discussions around
PropertyLayervolatility and the object-identity issues seen in recent community PR attempts, my GSoC proposal centers on a Flyweight architecture. The goal is to unlock the C-speed of vectorizedPropertyLayerarrays while creating a strict abstraction layer that completely insulates Mesa-Geo's public API from any future internal changes in Mesa-Core. This ensures backward compatibility and preservesmesa.Agentlifecycle hooks.I have finished my full draft covering the Raster Refactor, the Pandas-style Aggregation API, and the SolaraViz
GeoSpaceoverhaul. To keep this thread clean (and to keep my draft private before applications officially open next week), I am sending you both a direct message on Matrix with the link for any early feedback.Looking forward to the community dev meeting on March 17th!
Beta Was this translation helpful? Give feedback.
All reactions