You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've received numerous feature requests (FRs) for multiple image support across various objects, including performers, alternate scene covers (scenes), DVD/CD/VHS covers and spines for movies (now groups), and studio favicons (studios). Many of these FRs have been limited in scope or overly simplistic. For instance, some requests specify a single image type (e.g., DVD Spine Cover) hardcoded to a movie objects, while others propose multiple image support without any corresponding metadata/attributes, effectively creating a redundant sub-gallery of images outside existing only within an object.
Proposal: One multiple image support request to rule them all
To address these needs comprehensively, I propose we implement multiple image support for all objects (scenes, performers, studios, tags, groups) using corresponding user-defined custom image types. These user-defined attributes will categorize the images, allowing for diverse applications beyond mere archival purposes.
Example of object image types
Object
(Custom) Description
(Custom, Optional) Aspect Ratio
Hardcoded
Studio
Favicon
1:1
True
Studio
Banner
Studio
Wordmark
Scene
Original
Scene
Alternate
Scene
Poster
2:3
True
Performer
Headshot
2:3
True
Performer
Hero
16:9
True
Performer
Clothed
Performer
Unclothed
Movie
DVD Cover
Movie
DVD Spine
Movie
VHS Cover
Movie
VHS Cover
Some of these, which might deemed to have a general in-app use-case, could come prepopulated with the stock app, such as performer headshot and studio favicons.
Performer select drop down fields. Looks for the performer headshot type first, if it exists, it displays that image, which is more useful in select drop down.
Plugins could expand about grid view types, with some grid view favoring certain image types over others
Yet another multiple image support request
We've received numerous feature requests (FRs) for multiple image support across various objects, including performers, alternate scene covers (scenes), DVD/CD/VHS covers and spines for movies (now groups), and studio favicons (studios). Many of these FRs have been limited in scope or overly simplistic. For instance, some requests specify a single image type (e.g., DVD Spine Cover) hardcoded to a movie objects, while others propose multiple image support without any corresponding metadata/attributes, effectively creating a redundant sub-gallery of images outside existing only within an object.
Proposal: One multiple image support request to rule them all
To address these needs comprehensively, I propose we implement multiple image support for all objects (scenes, performers, studios, tags, groups) using corresponding user-defined custom image types. These user-defined attributes will categorize the images, allowing for diverse applications beyond mere archival purposes.
Example of object image types
Some of these, which might deemed to have a general in-app use-case, could come prepopulated with the stock app, such as performer headshot and studio favicons.
Potential use-cases
Just the tip of the iceberg here.
Related FRs
The text was updated successfully, but these errors were encountered: