Skip to main content
GameTeX Django
==============

A Django app for GameTeX integration. Writing a ten-day webapp? You'll want this.

Getting started
---------------

You'll need a version of GameTeX that supports JSON export (talk to Ken).

To install:

* `pip install gametex-django`
* Add `gametex` to your INSTALLED_APPS in settings.py.
* Run `./manage.py syncdb` to create the new models.

To import your game data:

* Generate `json_PRINT.json` by LaTeXing `json_PRINT.tex` in your game's Production directory.
* Run `./manage.py load_gametex /path/to/json-PRINT.json`

You then have access to everything exported in your JSON file, all within Django.

If you pass the `--clear` argument to `./manage.py load_gametex`,
all existing GameTeX objects will be deleted from your database.

If you pass the `--create-users` argument, *and* all your PCs have
'username' and 'password' fields, the loader will automatically create
users for each of your PCs and create GameTeXUser entries to map between
them.

Django model mapping
--------------------

Each GameTeX entity (sheet, ability, PC, etc.) becomes a GameTeXObject
(GTO for short). Each GTO belongs to a number of classes, such as
'KeyCard', 'Item', or 'PC'; a 'PC' might also be a 'Char'. (There's
no hierarchical representation in the GameTeX Django models; that's up
to GameTeX.)

There's a shortcut method, 'bc', that allows you to filter
GameTeXObjects by class.

Each GTO has a 'name', a 'number', and a 'macro'; 'name' and 'number'
may be blank. You can query using any of these, and you can access
them in the usual way:

>>> g = GTO.bc('PC')[0]
>>> g.name
u'Captain GameTeX'
>>> g.macro
u'cTest'
>>> g.number
u'22234'

Note that all fields are Unicode text, even ostensibly numerical ones
such as 'number'. It's up to you to convert those to int (or whatever)
if necessary.

GTOs may also have custom fields defined, depending on how your game
looks. For example, an item might have a 'price' field. You can
access these like normal:

>>> g2 = GTO.bc('KeyCard')[0]
>>> g2.name
u'CompSci Data'
>>> g2.hintreq
u'Cryptography 2'
>>> g2.name = 'CS Data'
>>> g2.name
u'CS Data'

In case your field has spaces in it, you can reference it with the
'field' and 'set_field' methods of GameTeXObject:

>>> g.has_field('Combat Rating')
True
>>> g.field('Combat Rating')
u'2'
>>> g.set_field('Combat Rating', '4')
>>> g.field('Combat Rating')
u'4'

Updating in place
-----------------

Running `./manage.py load_gametex ...` again will update your objects in-place.
If a macro exists, any field changes you've made in the database will be overridden, but
new objects will be created and new fields populated as normal. For example, if you had
a character (pseudo-JSON):

{"macro": "cTest",
"name": "Captain GameTeX",
"number": "1",
"Combat Rating": "2"
}

and you updated from a JSON file that looked like this:

{"macro": "cTest",
"name": "Captain Achmed von GameTeX",
"number": "100",
"income": "5"
}

you'd get:

{"macro": "cTest",
"name": "Captain Achmed von GameTeX",
"number": "100",
"income": "5",
"Combat Rating": "2"
}

You may override this behavior by passing `--preserve` to `./manage.py load_gametex`. This
would result in:

{"macro": "cTest",
"name": "Captain GameTeX",
"number": "1",
"Combat Rating": "2"
"income": "5",
}

Metadata

Release files for gametex-django 0.3.6

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for gametex-django 0.3.6
File Size Uploaded Provenance
gametex-django-0.3.6.tar.gz 13.2 kB Without provenance Details

Release files / gametex-django-0.3.6.tar.gz

Download URL gametex-django-0.3.6.tar.gz
Size 13.2 kB
Tags Source
SHA-256 checksum
How to use checksums
45f6cce71ebd3e505caa81f7ab26d4d331158511b7f77caeb0afc8c37a161c15
BLAKE2b-256 checksum
How to use checksums
21cc11022e44db5f5209586102d909e71cd5905f1c18273ce93e92b8fb9b9248
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for gametex-django 0.3.6

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page