Mipui Developer Guide
Mipui is a free web app for creating and editing maps for tabletop and role-playing games.
This is the developer's guide; see the main site or just jump right into the editor.
Mipui is a hobby project implemented by just one developer with no background in web development; please don't judge the code quality :-) in particular while some areas underwent extensive planning (like operation_center) others were completely hacked together in an hurry (like the menu).
The server-side component is done using [Firebase](firebase.google.com).
Some Implementation Pointers
- Gestures are used for drawing content on the map; but content can also come from non-gesture sources (e.g. loaded from the server), so every cell must know how to correctly draw its content even when no gestures are involved.
This is why cells contain the "setImage", "setText" etc. methods, instead of those being a part of the image or text gestures.
- Map synchronization is guaranteed by serializing the operations, so all clients agree on the order of all operations. Never break that invariant.
- Two important global variables are content (from content.js) and state (from state.js). Go over these if you plan on doing any changes to content saved on the map.
- Methods and fields which are intended to only be used inside the declaring class are marked with trailing underscore_.
- theme.css is intended to be tweaked for styling, while the other style sheets are more functional and care is needed when changing them.
There are three live firebase database repositories: mipui-prod, mipui-dev and mipui-test.
- mipui-prod is the repository serving the live version at mipui.net. Never use that repository.
- mipui-dev is the repository used for development. Feel free to use that repository when testing any changes. This is the default repository used in the code. Information in this repository might get wiped from time to time, though, so don't rely on it for long-term storage.
- mipui-test is used for running unit tests. Please immediately clean any information you create there.
This software is published under an MIT license.
Testing is mostly manual, though a couple of tricky-to-test components have their own sets of unit tests.
As a personal challenge I tried to write them without any test framework;
I know it's a terrible practice but I just wanted to try.
I do recommend using existing frameworks!