ipywardley
Bringing Wardley Map magic to Jupyter notebooks
Introduction
This plugin makes it easy to generate Wardley Maps using Jupyter Notebooks.
It supports a subset of the syntax defined by the Online Wardley Maps service. This simple language can be use to specify the map via the %%wardley cell magic.
Try it out!
Installation
First, install Jupyter. Then before running it, install ipywardley. e.g. if you are using pip:
pip install ipywardley
Then, run Jupyter:
jupyter-lab
Usage
Open up a new Python 3 notebook, and use this command to enable the module:
%load_ext ipywardley
Now you can use the %%wardley directive and create maps. See this example notebook for a detailed example of how to do this.
Screenshot
To Do
- Support more of the OWM syntax and features (?=maybe?):
-
evolution Novel->Emerging->Good->Bestandevolution Xoffering the different sets of x-axis labels. -
y-axis Value Chain->Invisible->Visibleory-axis noneto make 'Visibility' axis optional. -
evolve -
annotation&annotations? -
note? -
marketnodes? -
pipelinenodes? - node
inertia? -
+<>links to indicate flow. -
+>links to indicate flow. -
+<links to indicate flow. -
Hot Water+'$0.10'>Kettleflow labels? -
build,buy,outsourcenode augmentation? -
submapand related syntax? -
pioneer,settler,townplannerareas/boxes?
-
- Add 'Uncharted' and 'Industrialised' labels
- Support rendering from a file, via e.g.
%wardley file=example.owm style=plain - Make it easier to download the SVG/rendered version?
Development
- Clone this directory.
- Set up a
virtualenvand activate it. - Modify the code.
- Run
flit install - Run
jupyter-laband test your changes. - Repeat 3-5 ad infinitum.
- Turn your changes into a pull request.
Making a Release
As per https://flit.pypa.io/en/stable/
- Update version in
\_\_init\_\_.py - Commit, tag, push.
flit publish
Change Log
- 0.0.7:
- Switch from
plt.grid(visibility=True, ...)toplt.grid(visible=True, ...).
- Switch from
- 0.0.6:
- 0.0.5:
Metadata
Release files for ipywardley 0.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ipywardley-0.0.7.tar.gz | 449.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ipywardley-0.0.7-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 467.9 kB
Release files / ipywardley-0.0.7.tar.gz
| Download URL | ipywardley-0.0.7.tar.gz |
|---|---|
| Size | 449.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
44ab4d933c5b8990cb4c2836882b1b5cc3e9cfcb793ed64396caa1c3e9eddfd4
|
|
BLAKE2b-256 checksum How to use checksums |
a55dd99d088f3a3838aa77e9bc7d2fc78cfc7f300b1481afe0642110c8f8f0ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.28.2
|
Release files / ipywardley-0.0.7-py2.py3-none-any.whl
| Download URL | ipywardley-0.0.7-py2.py3-none-any.whl |
|---|---|
| Size | 18.5 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
a11c70b57568b93e2480fa2608f14d8a35e948b4a8ef6e35ba5abbdcbe2284f8
|
|
BLAKE2b-256 checksum How to use checksums |
646adbb6d7722fa4d05b9d68f4c1cb29d1ffbd08736a88eeab3e9bb0e7e3c803
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-requests/2.28.2
|
Security for ipywardley 0.0.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.