rht

Authoring a Jupyter widget with React: https://blog.jupyter.org/build-a-jupyter-widget-with-react-and-typescript-d83e07340fa3.

The new `batch_run()` is simpler, but it hasn't been used by a lot of people yet, and so there is no data point on its UX. There could be unforeseen...

Another alternative: split the examples into essential examples (making sure they cover all the built-in features) and non-essential examples (where they heavily use the functionality of other libraries). In this...

This way, people won't have to stop and read what `model.running` is, what it is used for, etc -- saving time.

Based on reading https://juliadynamics.github.io/Agents.jl/stable/comparison/, it seems that Agents.jl considers it a feature to have a boolean model state to tell whether a model has terminated or not. I can't find...

OK, I'm answering my own question regarding with Agents.jl termination. The `run!` has `n` as an argument, which can be an `Int` or a function. The `until` function handles both...

IMO, the simulation termination condition should be defined separately from the model step. I think, writing it in `run_model` is cleaner.

Regarding with `this.running` (https://github.com/projectmesa/mesa/blob/5a4248d9c6b5bb81271abefc82a6cafa9788c730/mesa/visualization/templates/js/runcontrol.js#L42) in the front-end, it is actually not related to `model.running`. The only interaction with the server is the `get_step` message in https://github.com/projectmesa/mesa/blob/5a4248d9c6b5bb81271abefc82a6cafa9788c730/mesa/visualization/templates/js/runcontrol.js#L54. The models that have...

It looks like the `ModelController` is not leveraging the model's `run_model` when the "start" button is clicked where it should have. This seems incorrect.

I think it is actually safer with `run_model`, because the client is passively waiting for websocket messages from the server anyway. I have seen that currently, the simulation keeps doing...