Set JupyterViz as stable

docs/mesa.md

@@ -3,7 +3,7 @@
 ## Subpackages
 
 ```{toctree}
-mesa.visualization
+mesa.visualization_old
 ```
 
 ## Submodules

docs/mesa.visualization_old.md

@@ -0,0 +1,46 @@
+# mesa.visualization_old package
+
+## Subpackages
+
+```{toctree}
+mesa.visualization_old.modules
+```
+
+## Submodules
+
+## mesa.visualization_old.ModularVisualization module
+
+```{eval-rst}
+.. automodule:: mesa.visualization_old.ModularVisualization
+    :members:
+    :undoc-members:
+    :show-inheritance:
+```
+
+## mesa.visualization_old.TextVisualization module
+
+```{eval-rst}
+.. automodule:: mesa.visualization_old.TextVisualization
+    :members:
+    :undoc-members:
+    :show-inheritance:
+```
+
+## mesa.visualization_old.UserParam module
+
+```{eval-rst}
+.. automodule:: mesa.visualization_old.UserParam
+    :members:
+    :undoc-members:
+    :show-inheritance:
+
+```
+
+## Module contents
+
+```{eval-rst}
+.. automodule:: mesa.visualization_old
+    :members:
+    :undoc-members:
+    :show-inheritance:
+```

docs/mesa.visualization_old.modules.md

@@ -0,0 +1,76 @@
+# mesa.visualization_old.modules package
+
+## Submodules
+
+## mesa.visualization_old.modules.BarChartVisualization module
+
+```{eval-rst}
+.. automodule:: mesa.visualization_old.modules.BarChartVisualization
+    :members:
+    :undoc-members:
+    :show-inheritance:
+```
+
+## mesa.visualization_old.modules.CanvasGridVisualization module
+
+```{eval-rst}
+.. automodule:: mesa.visualization_old.modules.CanvasGridVisualization
+    :members:
+    :undoc-members:
+    :show-inheritance:
+```
+
+## mesa.visualization_old.modules.ChartVisualization module
+
+```{eval-rst}
+.. automodule:: mesa.visualization_old.modules.ChartVisualization
+    :members:
+    :undoc-members:
+    :show-inheritance:
+```
+
+## mesa.visualization_old.modules.HexGridVisualization module
+
+```{eval-rst}
+.. automodule:: mesa.visualization_old.modules.HexGridVisualization
+    :members:
+    :undoc-members:
+    :show-inheritance:
+```
+
+## mesa.visualization_old.modules.NetworkVisualization module
+
+```{eval-rst}
+.. automodule:: mesa.visualization_old.modules.NetworkVisualization
+    :members:
+    :undoc-members:
+    :show-inheritance:
+```
+
+## mesa.visualization_old.modules.PieChartVisualization module
+
+```{eval-rst}
+.. automodule:: mesa.visualization_old.modules.PieChartVisualization
+    :members:
+    :undoc-members:
+    :show-inheritance:
+```
+
+## mesa.visualization_old.modules.TextVisualization module
+
+```{eval-rst}
+.. automodule:: mesa.visualization_old.modules.TextVisualization
+    :members:
+    :undoc-members:
+    :show-inheritance:
+
+```
+
+## Module contents
+
+```{eval-rst}
+.. automodule:: mesa.visualization_old.modules
+    :members:
+    :undoc-members:
+    :show-inheritance:
+```

docs/modular-visualization.md

@@ -1,4 +1,4 @@
-# Modular Visualization - An In-Depth Look
+# Modular Visualization - An In-Depth Look (Deprecated)
 
 Modular visualization is one of Mesa's core features. Mesa is designed
 to provide predefined visualization modules, which can be easily
@@ -127,7 +127,7 @@ Suppose we want a module which can get an arbitrary variable out of a
 model, and display its name and value. Let's create a new subclass:
 
 ```python
-from mesa.visualization.ModularTextVisualization import TextElement
+from mesa.visualization_old.ModularTextVisualization import TextElement
 
 class AttributeElement(TextElement):
     def __init__(self, attr_name):
@@ -205,7 +205,7 @@ Now let's take a look at the TextModule's Python counterpart,
 here's the whole thing:
 
 ```python
-from mesa.visualization.ModularVisualization import VisualizationElement
+from mesa.visualization_old.ModularVisualization import VisualizationElement
 
 class TextElement(VisualizationElement):
     js_includes = ["TextModule.js"]
@@ -240,8 +240,8 @@ the list, the code passes that element of the data to the *render*
 function of the corresponding element, in the elements array.
 
 Currently, module JavaScript files live in the
-*mesa/visualization/templates* directory, and the Python files live in
-*mesa/visualization/modules*.
+*mesa/visualization_old/templates* directory, and the Python files live in
+*mesa/visualization_old/modules*.
 
 When creating a new module, the Python and JavaScript code need to be
 written in synch: the module Python-side **render** method needs to

docs/overview.md

@@ -119,8 +119,8 @@ batch_df = batch_run.get_model_vars_dataframe()
 
 Finally, you may want to directly observe your model as it runs. Mesa's main visualization tool uses a small local web server to render the model in a browser, using JavaScript. There are different components for drawing different types of data: for example, grids for drawing agents moving around on a grid, or charts for showing how some data changes as the model runs. A few core modules are:
 
-- mesa.visualization.ModularVisualization
-- mesa.visualization.modules
+- mesa.visualization_old.ModularVisualization
+- mesa.visualization_old.modules
 
 To quickly spin up a model visualization, you might do something like:
 
@@ -135,8 +135,8 @@ def agent_portrayal(agent):
                  "r": 0.5}
     return portrayal
 
-grid = mesa.visualization.CanvasGrid(agent_portrayal, 10, 10, 500, 500)
-server = mesa.visualization.ModularServer(MyModel,
+grid = mesa.visualization_old.CanvasGrid(agent_portrayal, 10, 10, 500, 500)
+server = mesa.visualization_old.ModularServer(MyModel,
                        [grid],
                        "My Model",
                        {'n_agents': 10})