I did consider this, but as there is not much additional information to be gotten from the query; I didn't think it was much use. What do you think would be good to display on the view? I think the tab is primarily meant to find people that you know the name of or scroll through to see who's popular at this moment. In both cases it makes sense to show the name and a picture. In the second case it might be nice to show a bit more information, but the only additional information that is available (without requesting full details of a person) is the movies that the person is known for. This is probably not the kind of information that someone is looking for (in the second use case) as the user would probably just go to a specific movie and see who's part of the cast to find that out and even if it is, the user is just one click away from that information by clicking on the person (and thus going to a full overview).
Still, I might be off, so if you think otherwise, please let me know. :)
I did consider this, but as there is not much additional information to be gotten from the query; I didn't think it was much use. What do you think would be good to display on the view? I think the tab is primarily meant to find people that you know the name of or scroll through to see who's popular at this moment. In both cases it makes sense to show the name and a picture. In the second case it might be nice to show a bit more information, but the only additional information that is available (without requesting full details of a person) is the movies that the person is known for. This is probably not the kind of information that someone is looking for (in the second use case) as the user would probably just go to a specific movie and see who's part of the cast to find that out and even if it is, the user is just one click away from that information by clicking on the person (and thus going to a full overview).
Still, I might be off, so if you think otherwise, please let me know. :)
What do you think would be good to display on the view?
Jobs: actor/actress, director, producer, screenwriter, etc.
Known for; Total number of known credits.
Birthday; Day of death; Place of birth.
Anything from this list, probably, is better than nothing.
Also a possibility to change grid size for the People tab is needed, in addition to: #24.
>What do you think would be good to display on the view?
* Jobs: actor/actress, director, producer, screenwriter, etc.
* Known for; Total number of known credits.
* Birthday; Day of death; Place of birth.
Anything from this list, probably, is better than nothing.
Also a possibility to change grid size for the People tab is needed, in addition to: #24.
As far as I know that data (with the exception of known for) is not available without calling extra queries. This normally wouldn't be a problem, but there is a restriction on the amount of queries that can be requested through the API (which is about 40 requests every ten seconds; see https://www.themoviedb.org/faq/api). When sending an extra query for every person that you see on the grid, you'll quickly hit that maximum of 40 requests when scrolling.
As for changing the grid size for the people tab, that won't be a problem to implement. I'll include that in issue #24.
As far as I know that data (with the exception of known for) is not available without calling extra queries. This normally wouldn't be a problem, but there is a restriction on the amount of queries that can be requested through the API (which is about 40 requests every ten seconds; see https://www.themoviedb.org/faq/api). When sending an extra query for every person that you see on the grid, you'll quickly hit that maximum of 40 requests when scrolling.
As for changing the grid size for the people tab, that won't be a problem to implement. I'll include that in issue #24.
OK, then (if I understand you correctly) we have only two options:
Add the movies that the person is known for (to addition to the name and a picture);
Wait until TMDb's API will be extended with additional info.
OK, then (if I understand you correctly) we have only two options:
* Add the movies that the person is known for (to addition to the name and a picture);
* Wait until TMDb's API will be extended with additional info.
Would be nice to have an option to disable a grid for persons too.
I did consider this, but as there is not much additional information to be gotten from the query; I didn't think it was much use. What do you think would be good to display on the view? I think the tab is primarily meant to find people that you know the name of or scroll through to see who's popular at this moment. In both cases it makes sense to show the name and a picture. In the second case it might be nice to show a bit more information, but the only additional information that is available (without requesting full details of a person) is the movies that the person is known for. This is probably not the kind of information that someone is looking for (in the second use case) as the user would probably just go to a specific movie and see who's part of the cast to find that out and even if it is, the user is just one click away from that information by clicking on the person (and thus going to a full overview).
Still, I might be off, so if you think otherwise, please let me know. :)
Anything from this list, probably, is better than nothing.
Also a possibility to change grid size for the People tab is needed, in addition to: #24.
As far as I know that data (with the exception of known for) is not available without calling extra queries. This normally wouldn't be a problem, but there is a restriction on the amount of queries that can be requested through the API (which is about 40 requests every ten seconds; see https://www.themoviedb.org/faq/api). When sending an extra query for every person that you see on the grid, you'll quickly hit that maximum of 40 requests when scrolling.
As for changing the grid size for the people tab, that won't be a problem to implement. I'll include that in issue #24.
OK, then (if I understand you correctly) we have only two options: