PokemonGoers / Catch-em-all

Now that we have tons of data about Pokemon (what they are, where they are, what’s their relationship, what they can transform into, which attacks they can perform, aso) we want to integrate it all into a comprehensive website. This website should contain sections about each Pokemon and its details. Additionally, the website should register the user’s location and tell the user how close is that the predicted pokemon to him/her. Additionally you will be incorporating the apps that were created by project B,C and D into the website. Your group will need to create automated builds and testing for this apps and use continuous integration to pull in new changes in the code repositories. Apps from projects B-D should be packaged and made available on NPM. Ideally when you completed these tasks the webapp component would integrate the apps by “requiring’ them. Here is a possible user story: when a user opens the website or the app the current location of the user will be shown. Additionally, the website/app will show automatically where the pokemons that are currently active are and where the pokemons that we predict to active in the nearest future (i.e. within half a day) will be located (all of this will be available from the app developed in project D). Hopefully, the website will be somewhat crowded by that data. Then, there needs to be a menu bar or something available (e.g. above the map or on the right side to it) that will list currently active or predicted pokemons. Clicking on one of them will make other pokemons on the map disappear, except of this clicked one. Separate web pages would allow the search and presentation of individual Pokemons and the information we gathered about them, including third party data (project A) and twitter analysis (project C)
9 stars 7 forks source link

Mob card #80

Closed johartl closed 8 years ago

johartl commented 8 years ago

Similar to the POI card where we display a Pokemon which was clicked on we need the same for a mob. Once the user clicks on a mob a bottom sheet should slide up which shows the following information.

AlexanderLill commented 8 years ago

@johartl this can be closed after #87 is merged, right?

WoH commented 8 years ago

@AlexanderLill No, this is the Mob card, not the POI card.

AlexanderLill commented 8 years ago

@WoH but i saw some code in his PR that seemd to be handling the mobs :)

johartl commented 8 years ago

That's a different concept because for the mobs we want to display the tweets causing that mob. But I'm sure we can reuse the swipe card and just fill it with different content.

AlexanderLill commented 8 years ago

Okay :) I was just trying to clean up the issues a little bit :)

gyachdav commented 8 years ago

is this demoable?

MajorBreakfast commented 8 years ago

@sacdallago Why did you assign me to this? I just saw that you assigned me a few days ago and I didn't know anything about it! If I had known I wouldn't have redesigned the PokeDex! What to do now? I can build the card. But proper mob integration is a lot more work. I thought @johartl was on it

sacdallago commented 8 years ago

I assigned you and @Georrgi because one week ago @johartl was overloaded and I thought it'd be fair to redistribute a bit of the work :)

I thought this was only about the design, not the full integration. I seriously hope that is taken care of.

MajorBreakfast commented 8 years ago

I'll take care of it.

BTW I haven't heard from @Georrgi for quite a while now. He hasn't contributed to the project so far. I unassign him for now.

I will work on this this evening.

sacdallago commented 8 years ago

Good to know

MajorBreakfast commented 8 years ago

131 implements the PokeMob card