Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the Displaying of Tags to the Item Interface #6

Open
wants to merge 3 commits into
base: gh-pages
Choose a base branch
from

Conversation

EnigmaSolved
Copy link

Please note that this code is untested, but there's not much complexity here so as long as my guess about item.Tags is correct everything should run fine. :)

I've aimed for displaying the tags directly after the Overview, which is my recommended (and preferred) location, and is also consistent with their location in the Server web-app single-item display. Personally, I'm open to some other locations, but would definitely prefer to have tags displayed somewhere that general area (so, displaying them before the Overview, and after Genres, would be another logical location, though that may run the risk of being confused with Genres).

It might not be a bad idea to eventually add a user setting in the ET client to show or hide Tags (since perhaps some users won't wish to see them displayed), but I'm not familiar enough with the ET architecture yet to do a PR for that.

Let me know if anything else is needed in order to merge this into the core Emby Theater interface.

I'm just guessing regarding "item.Tags" -- wasn't sure where to look to verify that (so this is untested!). For now I've just gone with using the same approach as how Genres are handled of using bullets to separate them (so I mostly just copied and modified the Genres code), but I also think it would be fine to use the gray rounded-corner button look (like the tags appear in the server web interface, and like the media info details appear in ET). I might lean a little more towards the gray button look personally, but this was easier/quicker to implement. :)
Had originally used a Div because was thinking might try to emulate a different style presentation, but am going with P since currently just using same layout as Genres.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant