Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ship Map - Create Backend fixtures and API for storing deck SVGs #163

Closed
Tracked by #162
alexanderson1993 opened this issue Jan 8, 2022 · 0 comments · Fixed by #220
Closed
Tracked by #162

Ship Map - Create Backend fixtures and API for storing deck SVGs #163

alexanderson1993 opened this issue Jan 8, 2022 · 0 comments · Fixed by #220
Assignees
Labels
approved Issues that are approved and ready to be implemented.

Comments

@alexanderson1993
Copy link
Member

alexanderson1993 commented Jan 8, 2022

Discussed in #161

Originally posted by alexanderson1993 January 3, 2022

SVG layers

Each deck will first be defined with an SVG file that shows a graphical layout of that deck, with one SVG for each deck. Any images, lines, or diagrams can be used in these SVGs, but there will be guidelines for making sure the deck diagrams have a consistent appearance. SVGs are preferred since you can infinitely scale them without losing resolution, but it could be configured to work with transparent PNGs too.

As far as scale is concerned, we'll treat one SVG point as one meter. The expectation is that the deck SVGs will be able to layer on top of each other so they have everything lined up properly between decks.

In the future, there can be an in-app SVG editor, but for 1.0, we'll expect ship map SVGs to be created by hand or using an image editor like Adobe Illustrator.
So, decks will consist of:

  • A name
  • An order
  • An SVG image

...

Editing the Ship Map

Creating and editing the ship map is a simple process:

  • First, create and name a deck and upload an image for it. The image is stored in the file system with the plugin, not in the .yml file for the ship template.

...

@alexanderson1993 alexanderson1993 mentioned this issue Jan 8, 2022
9 tasks
@alexanderson1993 alexanderson1993 moved this to ⏳Pending Approval in Thorium Nova Roadmap Jan 8, 2022
@alexanderson1993 alexanderson1993 added the approved Issues that are approved and ready to be implemented. label Jan 8, 2022
@alexanderson1993 alexanderson1993 moved this from ⏳Pending Approval to 📌 Todo in Thorium Nova Roadmap Jan 8, 2022
@alexanderson1993 alexanderson1993 self-assigned this Feb 10, 2022
@alexanderson1993 alexanderson1993 moved this from 📌 Todo to 🛠 In Progress in Thorium Nova Roadmap Feb 10, 2022
@alexanderson1993 alexanderson1993 mentioned this issue Feb 10, 2022
11 tasks
@alexanderson1993 alexanderson1993 moved this from 🛠 In Progress to ✅ Done in Thorium Nova Roadmap Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Issues that are approved and ready to be implemented.
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant