Browse Source

Guild Wars design

main
Julio Biason 2 years ago
parent
commit
1edcb386e9
  1. 5
      README.md
  2. 19
      design/guildwars2.md
  3. 2
      design/mastodon.md
  4. 6
      design/rss.md

5
README.md

@ -17,15 +17,12 @@ Currently, I'm considering the following Capturers (based on my own life):
- [ ] [Mastodon](design/mastodon.md)
- [ ] [RSS](design/rss.md)
- [ ] Guild Wars 2
- [ ] [Guild Wars 2](design/guildwars2.md)
- [ ] Steam Capturer (?)
- [ ] Netflix
- [ ] Deezer
- [ ] Calendar/CalDav
### Guild Wars 2 Capturer
### Steam Capturer
### Netflix Capturer

19
design/guildwars2.md

@ -0,0 +1,19 @@
# Guild Wars 2 Capturer
The Guild Wars 2 will capture the daily play stats, like WvW Rank, PvP Rank,
completed achievements and play time.
## Configuration
The only required configuration is the access token.
## Internals
We need to keep, locally:
- Current played time, to be compared with the new one and point how long the
player played the game on the day.
- Achievements: This needs a two store: A list of current completed achievments
and a list of all achievements (there are different calls for each).
- Current WvW rank, to be compared with the new one.
- Current PvP rank, to be compared with the new one.

2
design/mastodon.md

@ -6,7 +6,7 @@ private and such, which seem better.
## Configuration
The only configuration necessary would be the access token.
The only required configuration is the access token.
## Internals

6
design/rss.md

@ -4,6 +4,12 @@ Simple capturer for RSS. The hard part would be converting the HTML result into
Markdown (although I've done this before, using
[Markup5Ever](https://docs.rs/markup5ever/0.11.0/markup5ever/).
## Configuration
The only required configuration is the feed URL.
## Internals
Needs to store, locally:
- `url`: to avoid mixing information of two different RSS readers;

Loading…
Cancel
Save