Apparently the Jellyfin server may include different fields in the
resposne depending on which SortOrder you use. This causes the model to
generate new roleNames when changing its sortOrder, but the QML part
does not know of this happening and there's no way of notifying the QML
part as far as I'm aware of (if so, let me know). So whenever new
generateFields() is called, it shouldn't reset its roleNames map and
recreate it anew, rather, just append the new roleNames to the current
map. If a model in QML wants to use information used in fields which are
added by changing SortOrder, please add those fields explicitly in
Fields.
* There is a basic collection page, allowing the user to browse through
collections. It has a sort function, that sort of works
* Item cards now show a bar indicating play time
* Item cards now have a black/white (depending on theme) shim, improving
readability.
* The resume watching section now actually loads items
* Pressing the logout button now brings the setup page up again
* Removing a server and readding one of which the hash of the address
has a higher value than the previous one does no longer cause the
application to request a login each time you open it.
* The method for deciding if the user is in setup has been changed. It
now checks if a page in the pageStack has the property _isSetupPage,
which works better than manually keeping track of state.
Features so far:
- Login is working, both on back-end and GUI-wise
- Saving and reusing login tokens is working
- The home page is mostly functional
- Show details can be received and displayed in a basic manner
Following features are taken into account, but have not been fully
implemented:
- Support for multiple accounts/servers
- Securely saving login tokens