chris/harbour-sailfin
chris/harbour-sailfin
1
0
Fork 0
mirror of https://github.com/HenkKalkwater/harbour-sailfin.git synced 2024-11-15 05:55:18 +00:00
Code Issues Releases Wiki Activity
harbour-sailfin/qml/pages/itemdetails/EpisodePage.qml

80 lines
3 KiB
QML
Raw Normal View History

Restructured the way item "details" are loaded Previously, Items were displayed in one page, named DetailPage.qml. This page then would load a qml component, based on the page type. It also contained some components common for each detail page, like displaying the name of the item. This construction had as downside that modifying the page properties, adding a pulley menu or basing the page around a SilicaListview was not possible. So I already had created some other pages. The new construction uses a base page, named BaseDetailPage which does set some common properties and handle the loading of the items, so that that part does not have to be duplicated. Displaying the name of an item was a very trivial thing to do, so duplicating that part across files was not a problem. Anyway, the rest of the pages are now seperate, but all have BaseDetailsPage as the root, so they can use the common functionality by that page. Those subpages now can be based around GridViews, Carrousels, have pully menus and so on. To determine to which page to go to, based on the content type, a function named getPageUrl has been added to Utils.js, which takes a content type as argument and gives the page url back.
2020-09-29 00:15:50 +00:00
/*
Sailfin: a Jellyfin client written using Qt
Copyright (C) 2020 Chris Josten
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
*/
import QtQuick 2.6
import Sailfish.Silica 1.0
import nl.netsoj.chris.Jellyfin 1.0
import "../../components"
import "../../"
BaseDetailPage {
SilicaFlickable {
anchors.fill: parent
contentHeight: content.height
Column {
id: content
width: parent.width
PageHeader {
title: itemData.Name
description: {
if (typeof itemData.IndexNumberEnd !== "undefined") {
qsTr("Episode %1–%2 | %3").arg(itemData.IndexNumber)
.arg(itemData.IndexNumberEnd)
.arg(itemData.SeasonName)
} else {
qsTr("Episode %1 | %2").arg(itemData.IndexNumber).arg(itemData.SeasonName)
}
}
}
PlayToolbar {
imageSource: Utils.itemImageUrl(ApiClient.baseUrl, itemData, "Primary", {"maxWidth": parent.width})
Report playback progress and resume items [Playback]: New: playback progress is reported to the Jellyfin server. [Playback]: New: resume partly played items or start playing from the beginning if desired. I also had to make some changes to the VideoPlayer, because the VideoHUD got locked up when the player changed status from Buffering to Buffered too quickly in succession, which occurs when trying to seek directly after the application is able to.
2020-10-01 19:45:34 +00:00
imageAspectRatio: itemData.PrimaryImageAspectRatio || 1.0
playProgress: itemData.UserData.PlayedPercentage / 100
Restructured the way item "details" are loaded Previously, Items were displayed in one page, named DetailPage.qml. This page then would load a qml component, based on the page type. It also contained some components common for each detail page, like displaying the name of the item. This construction had as downside that modifying the page properties, adding a pulley menu or basing the page around a SilicaListview was not possible. So I already had created some other pages. The new construction uses a base page, named BaseDetailPage which does set some common properties and handle the loading of the items, so that that part does not have to be duplicated. Displaying the name of an item was a very trivial thing to do, so duplicating that part across files was not a problem. Anyway, the rest of the pages are now seperate, but all have BaseDetailsPage as the root, so they can use the common functionality by that page. Those subpages now can be based around GridViews, Carrousels, have pully menus and so on. To determine to which page to go to, based on the content type, a function named getPageUrl has been added to Utils.js, which takes a content type as argument and gives the page url back.
2020-09-29 00:15:50 +00:00
onPlayPressed: pageStack.push(Qt.resolvedUrl("../VideoPage.qml"),
Report playback progress and resume items [Playback]: New: playback progress is reported to the Jellyfin server. [Playback]: New: resume partly played items or start playing from the beginning if desired. I also had to make some changes to the VideoPlayer, because the VideoHUD got locked up when the player changed status from Buffering to Buffered too quickly in succession, which occurs when trying to seek directly after the application is able to.
2020-10-01 19:45:34 +00:00
{"itemId": itemId, "itemData": itemData,
"audioTrack": trackSelector.audioTrack,
"subtitleTrack": trackSelector.subtitleTrack,
"startTicks": startFromBeginning ? 0.0
: itemData.UserData.PlaybackPositionTicks })
Restructured the way item "details" are loaded Previously, Items were displayed in one page, named DetailPage.qml. This page then would load a qml component, based on the page type. It also contained some components common for each detail page, like displaying the name of the item. This construction had as downside that modifying the page properties, adding a pulley menu or basing the page around a SilicaListview was not possible. So I already had created some other pages. The new construction uses a base page, named BaseDetailPage which does set some common properties and handle the loading of the items, so that that part does not have to be duplicated. Displaying the name of an item was a very trivial thing to do, so duplicating that part across files was not a problem. Anyway, the rest of the pages are now seperate, but all have BaseDetailsPage as the root, so they can use the common functionality by that page. Those subpages now can be based around GridViews, Carrousels, have pully menus and so on. To determine to which page to go to, based on the content type, a function named getPageUrl has been added to Utils.js, which takes a content type as argument and gives the page url back.
2020-09-29 00:15:50 +00:00
width: parent.width
}
VideoTrackSelector {
id: trackSelector
width: parent.width
tracks: itemData.MediaStreams
}
SectionHeader {
text: qsTr("Overview")
}
PlainLabel {
id: overviewText
Report playback progress and resume items [Playback]: New: playback progress is reported to the Jellyfin server. [Playback]: New: resume partly played items or start playing from the beginning if desired. I also had to make some changes to the VideoPlayer, because the VideoHUD got locked up when the player changed status from Buffering to Buffered too quickly in succession, which occurs when trying to seek directly after the application is able to.
2020-10-01 19:45:34 +00:00
text: itemData.Overview || qsTr("No overview available")
Restructured the way item "details" are loaded Previously, Items were displayed in one page, named DetailPage.qml. This page then would load a qml component, based on the page type. It also contained some components common for each detail page, like displaying the name of the item. This construction had as downside that modifying the page properties, adding a pulley menu or basing the page around a SilicaListview was not possible. So I already had created some other pages. The new construction uses a base page, named BaseDetailPage which does set some common properties and handle the loading of the items, so that that part does not have to be duplicated. Displaying the name of an item was a very trivial thing to do, so duplicating that part across files was not a problem. Anyway, the rest of the pages are now seperate, but all have BaseDetailsPage as the root, so they can use the common functionality by that page. Those subpages now can be based around GridViews, Carrousels, have pully menus and so on. To determine to which page to go to, based on the content type, a function named getPageUrl has been added to Utils.js, which takes a content type as argument and gives the page url back.
2020-09-29 00:15:50 +00:00
font.pixelSize: Theme.fontSizeSmall
color: Theme.secondaryHighlightColor
}
}
}
}
Copy permalink