ornato-t / dia-dynmap

A dynamic map of hell for the D&D module "Baldur's Gate - Descent into Avernus".

About me

• 👋 Hi! I'm Tommaso Ornato
• 📚 I study Computer Engineering at @polito
• 🖥 I mainly work on Frontend Development
• 🔭 I'm currently interested in The Fediverse
• 📸 I am a hobbyist photographer

Some projects I've worked on

• GTTTools - a mobile first, web application for smart mobility in the city of Turin, Italy.
  [TypeScript, SvelteKit, Tailwind CSS, MongoDB]
• Based Count - a data aggregation website for a subreddit of over 500k users.
  [Go, TypeScript, Svelte, Tailwind CSS, MongoDB]
• flairchange_bot - a data collecting Reddit bot with over 300 positive votes.
  [TypeScript, NodeJS]
• ChadGPT - a GPT-2 language model trained on conflicting and controversial political opinions.
  [Python, MongoDB]
• Defederation Investigator - a website tracking federation activity on Lemmy and the Fediverse.
  [TypeScript, SvelteKit, Tailwind CSS]

Skills and technologies

Programming languages

Frontend

Databases and DBMS

Language Proficiency

• Italian - native
• English - C1 (IELTS Academic 8.0/9.0)
• French - A1

dia-dynmap's Issues

Fix buttons CSS on DM's view

The DM's view works fine but the dropdown buttons on the top right corner are a bit broken. The following bugs need to be fixed:

• The dropdown "Show options" button (id: parentButton) sometimes doesn't trigger when clicked and needs to be clicked multiple times.
• On mobile devices and smaller screen the buttons are extremely broken. They fall under the hex grid making them non-interactable and stick in the middle of the page instead of flowing to the side.
• Both buttons' shadows sometimes lose tiny rectangles of texture when interacted with. Fixing this is not a priority but should be worked on.

Running player view on a local web server

Users using the app for in person play should be able to run the player view on their local network on a local server (see README.md#using-this-app, second bullet point).

The easiest way to do this would probably be opening a local web server using express.js in /player/index.js, hosting it on any machine capable of running node. This would allow in person users to not deal with the complexity of setting up a remote host for the player view on glitch or on any other service.