Data management UI

[amis92]

Adding UI for managing data sets (game systems, catalogues etc).

Browsing Gallery/Appspot content and selecting which items to download,
and showing which are currently installed locally.

The backing code is supposed to be done in #25

Features:

• Show a list of repositories from a Catpkg Gallery (see Implement data acquisition #25)
• Elements (repositories) can be selected to be locally loaded (downloaded into the browser memory)
• Elements should show some details like name, date, version
• Elements should show a message/icon that an updated version is available (compared to locally downloaded)

A repository can have different states:

• listed as "available to load"
• listed as "loaded locally" and then:
  • it can have an "update available"
  • or it can be "up to date"

[gregscode2]

Really rough wireframe of what I had in mind for this page. Each game system has 3 buttons, save, update and remove, different buttons are disabled based on the state of the game system. The 3 states are:

• not saved locally (update and remove are disabled, can be saved aka loaded into memory)
• saved locally and is up to date (save and update are disabled. Can be removed from memory)
• saved locally and not up to date (save is disabled, can be updated or removed)

Please note that this is a wireframe and only really shows the position of elements in the UI. They will not look exactly like this when I code it. Just trying to get feedback early :)

[amis92]

@arlo47 Looks great! Starting with three buttons is just fine, very simple and clean.

Some thoughts:

• We'll definitely want a Show Archived (default=false) filter (can be a checkbox like Show Saved is) from the start.
• I think the Add Data Source button can be dropped for now. We'll probably want to have a bit more advanced "Manage Data Sources" component later.
• I wouldn't call these "Game systems", because there might be more than one system in a single repository (e.g. HH v1, v2). Maybe call it "packages" or "Data sets"?
• Let's call the Save action either Acquire or Pull (your choice). I've come up with a Pull when thinking of similarities to git.
• Let's give an arrow up for Update :D

[gregscode2]

Sounds good!

What is the difference between a saved package and an archived package?

[amis92]

@arlo47 Archived is a flag on a repository. GitHub has a feature called "Archived Repository" which renders the repository completely readonly (no issues, no comments, no nothing - full freeze). We're using that feature to mark super-old, unmaintained data repositories as such (e.g., Warhammer 40k 7th edition), and we do that to prevent people being confused with too many choices.