Project

General

Profile

Feature #1476

Updated by cpg almost 7 years ago

With the information I have right now about the metadata server, here is how I propose to be implemented. Please provide feedback.
Api call:
<pre>
GET /md?f=filename&h=hint
</pre>


Here is my take on the implementation.
1. The shares API will have a content tag that has a list of tags

2. If content of a share contains is "movies"
- When user touches the share, the files and folders list will be retrieved and metadata will be called for EVERY file and folder, with the hint "movie"
- Each file/folder will be displayed with the artwork of the movie with the title on top and the year. Here we can later get creative and show as much information as we deem suitable in a _nice_ UI. it's important that we make this of very high quality. starting with something simple.
- When user taps on a movie, if it is a file it will play the movie.
- this is higher priority and should be implemented first because it's simpler

3. If content of a share is "tv"
- When user touches the share, the files and folders list will be retrieved and metadata will be called for EVERY file and folder with the hint "tv"
- Each file/folder will be displayed on multiple lines with the artwork and description
- When user touches a TV show if it is a file it will just play. If it is a folder that folder will be listed as follows. The header will be the Artwork and description as on the previous screen. The files and folders will be displayed as a list (probably not the best way but I don't see a good way to do it now).
- Browsing deeper within the folder should keep the header.
- This is low priority and should not be implemented until we have done movies

4. In any other case, the folder listing will be shown (this shown(this is the default option for all shares)


Back