micahg/ntt

Network Table Top

Network Table Top

Present tabletop assets on a remote screen.

Mission

1. Eliminate paper maps
2. Run on any screen
3. Stay simple
4. Stay open source
5. Stay cheap

For cost -- try to keep it free for everyone even on hosted unless they want asset storage.

Ideally give people the option to host their own install too.

ntt's Issues

debounce resize

no need to rerender while resizing.

websocket keep alive

Add a keep alive ping so we don't constantly close out the socket and reopen it.

Redo Toolbars

When you come back to this, think back -- you tried to change the toolbar to dynamically respond to the scene component state and it did not go well.

Because the canvasses are basically their own state and have a separate state machine, you can away with the janky implenetation of how those toolbars work. But the implementation is probably "wrong" or at least isn't the right way to do it with react.

Reminder: right now you have an object in the ContentEditor module (not the functional component state) that represents the state of the buttons. It'll have properties you'll use to enable or disable the button. This is janky but you need it because the functions in the GameMasterAction don't pull up-to-date values from the component state (eg: something you set with useState).

When you come back around to this, i think its important to revisit how you can signal between components or how effects from one can influence another.

Handle failed asset uploads

If you upload a really big asset (right now > 32mb) the system fails without error.

Specifically a 413, which we know is "too big" is just ignored.

Environment config not considering hostname

All assets are fetched from localhost even on the docker image.

Opacity for overlay (editor only)

Convert to Monorepo

Oh if Sasha could see me now ... he'd give me shit!

• rename repo to tbltp (optional but its in the settings so why not)
• https://gfscott.com/blog/merge-git-repos-and-keep-commit-history/
• fix actions https://stackoverflow.com/a/58136732/3427440
• remove npm package build in actions (we only need docker now that we have compose.yml)

remove "@typescript-eslint/no-explicit-any": ["off"] from .eslintrc.json

fix your typing.

Color Chooser for Obscuring

clear remote overlay on scene flip to scene without overlay

To reproduce, flip between two scenes:

Scene A) player content and overlay
Scene B) payer content only

When you go from A to B and update the remote display, we leave scene A's overlay up on the remote. The easy workaround is to just clear the overlay and sync the remote display again...

docker compose for local install

Now that docker images are created we can:

• stop making npm packages, and only make docker images
• use docker compose for local runs to make life (and testing) easier
• its probably possible to have docker build in nttinfra FROM ntt and nttsrv. Maybe a monorepo makes more sense?

Default scene is ambiguous

How is anyone supposed to know what to do?

Websocket Defaulting to localhost:3000

frontend can appear laggy while assets are downloading

it'd be nice to have some UI feedback about uploads and downloads

scenes with no overlay adopt the previous scenes overlay

min and max zoom not updated when editor's scene changed

Fix zoom toggle

Problem

Zoom in/out works initially but after some play (maybe opacity related) you can't toggle the zoom state anymore.

Root Cause

Didn't really figure out how/when it happens but moving around and zooming in and our and playing with the opacity seem to do it.

After deleting a scene, its loaded in the content editor

This should not be...

I guess it would make sense to flow to the content editor when the scene is updated

Database for multiple scenes

use offscreen canvas for overlay

Right now the overlay image is sized to whatever fits in the window for the editor. It should use an off-screen canvas sized to the full background. I think it should:

• capture the dimensions on the onscreen canvas using mouse or whatever
• upsize
• render offscreen
• then paint onscreen

After a scene is created we should flow to the content editor for that scene

The SceneComponent, when creating a new scene, just sits there after the scene is created.