d4mation / living-pokedex Goto Github PK

When I first made this I thought it would be cool to include Pokedex Entries or something (And I think my Schema still reflects that...) but I wasn't able to get that via the APIs I was using so I never did it.

Now I realize that Evolution/Breeding data along with Capture Locations for each game is a much better addition, since I remember I was constantly checking Bulbapedia or Serebii while completing my Living Dex.

http://pokedextracker.com/ does this, but it only includes Capture Locations for Gen 6. Ideally I'd like to include Capture Data for Gens 3-6, since you can transfer all the way from Gen 3 to Gen 6 through legitimate means. I know that's how I got some of my Pokemon in my Living Dex 😆

Currently the User can only delete their data by clearing Caught Pokemon one at a time or by deleting it directly from the Database. That's no good.

Two separate builds, perhaps created based on different Gulp Tasks/Flags.

One for a Self Hosted setup, placed on master.

Another that can run without a Database (and run on gh-pages!)

cuint would need to be able to run from the Browser as well as DarkNikGr/PokeEditor for a version to work on gh-pages.

Perhaps for the Public Version data could be kept in LocalStorage?

Regardless, Releases would still have a .zip for each Branch.

.CSVs are cool and everything, but how about uploading a dumped main file? 😎

Utilizing DarkNikGr/PokeEditor on the server for ripping apart the PC Box data. May end up making a PR to include Party Pokemon and Daycare Pokemon if I can figure out the Save Structure.

With Angular+Express providing all kinds of very easy to use Routes, it seems almost pitiful to limit this to only a singular Admin User.

However, given that it is Self Hosted, maybe making it an option? So the ability enable/disable registration? People may not want their DB to get bloated from randos registering if they really just want it for themselves and are hosting it so they can get to it away from home from any device.

The latest Commit for master is based on Bootstrap and the Mobile experience isn't all that great.

Instead of squishing a bunch of Pokemon per row, perhaps just one large Entry per row would work best for Mobile.

http://poketracker.com/ handled it very well on Mobile. Desktop is very similar to what I already did.

The Public Version would fall short of other services like http://pokedextracker.com if it has no way to share the completion progress with other Users.

GET parameters may be a way to get around this, provided it doesn't get too long.

It would be static, but better than nothing. Unfortunately that's the downside to not having a central database ¯_(ツ)_/¯

Building on #3

Mongo is straight forward, but it is prone to crashing.