Skip to content
This repository was archived by the owner on Dec 14, 2022. It is now read-only.
This repository was archived by the owner on Dec 14, 2022. It is now read-only.

Make mapview HABP-community friendly #3

@relrod

Description

@relrod

The initial (NodeJS) version of mapview first came to life on July 29, 2013 -- a year and some months ago. This Haskell rewrite happened in January of this year.

Though it hasn't been tested in practice yet (due to balloon launch failures), I believe it is at the stage where we should begin looking at what we can do to turn it into a system that other clubs can take advantage of for their own launches. Among other things, this means getting it into a state where we can ship it to Hackage and perhaps a Fedora Copr/Ubuntu PPA.

Here is what I see needing to happen for this to pan out:

  • We need a landing site that explains:
    • An overview of the pieces of the system. The readme does this right now but is somewhat technical.
    • Information on installing the system
    • Information on setting up the mapview-psc frontend
    • Screenshots of mapview-psc
  • Misc. code cleanup
    • Perhaps split some pieces into separate modules.
    • Making use of lens-aeson
    • Making it easy for clubs to edit the parser (even though it requires a recompile)
    • Un-hardcode anything specific to our launches, if possible. Some stuff (e.g. parser) won't be possible.
  • Really clear install instructions
    • This is crucial, I think. We have a ton of dependencies. I don't see us giving up many of them, but at minimum we need to at least explain in detail how to install them all and set things up.
    • Explain how to deploy mapview-psc
    • Firewall gotchas between mapview-psc clients and mapview-send
  • Make sure mapview-psc works well on mobile.
  • Maybe develop a mobile app in addition, but this is way down the road.
    • It could do like the Google Sky Map and Satellite AR apps do and let you hold up your phone and have it show you, based on coordinates and look-angle, exactly where you should be looking. I suspect @kg4sgp would like that.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions