Simplification: merge run.py into server.py

[rht]

run.py always contains a few lines of code. Should we merge it into server.py to simplify the coding convention? If people need to call server.launch from a different files (e.g. running Mesa simulation as a part of a larger web application), they can define their separate run.py. I'm citing the 80-20 UX rule (see https://lawsofux.com/pareto-principle/) that we should optimize for the 80% of the use case, and hide the remaining 20% until when it is actually needed.

[jackiekazil]

I think the run.py was originally created for 2 reasons...

1. It was easy to identify which file to run.
2. The run.py was to explicitly hold more run-type settings but it never did.

I am not against your suggestion especially now that the runserver command exists.

[rht]

I simplified the Boltzmann wealth model layout in projectmesa/mesa-examples#44 into
examples/boltzmann_wealth_model/:

• model.py
• app.py
• __init__.py (so that the model is importable)

To run the GUI, simply do solara run app.py.

[jackiekazil]

How does this work with mesa runserver?

[rht]

mesa runserver could later be a proxy to solara run, but probably later on in 3.0.

[quaquel]

this is all deprecated with MESA 3.