chris/harbour-sailfin
chris/harbour-sailfin
1
0
Fork 0
mirror of https://github.com/HenkKalkwater/harbour-sailfin.git synced 2024-11-16 22:45:18 +00:00
Code Issues Releases Wiki Activity
harbour-sailfin/sailfish/qml/pages/itemdetails/FilmPage.qml

44 lines
1.4 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
sailfish: display backdrop instead of poster on film page This simply looks better, since the backdrop has a more suitable aspect ratio.
2024-01-02 21:42:35 +00:00
Copyright (C) 2020-2024 Chris Josten
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
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
WIP: Add playlists/queues and add support for Sailfish back
2021-07-31 13:06:17 +00:00
import nl.netsoj.chris.Jellyfin 1.0 as J
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
import "../../components"
import "../.."
Minor UI improvements * EpisodePage and FilmPage are now based off VideoPage, since they share a lot of components in common. * The overlay over the thumbnail in PlayToolbar is less obtrusive * Cover shows now the title of the item, and total play time, if applicable * The resume playing section forces all delegates to be square. * The Season page now uses a ListView instead of a ColumnView.
2020-10-01 22:13:05 +00:00
VideoPage {
Initial step towards the QObject rewrite
2020-10-04 21:03:58 +00:00
subtitle: qsTr("Released: %1 — Run time: %2").arg(itemData.productionYear).arg(Utils.ticksToText(itemData.runTimeTicks))
sailfish: display backdrop instead of poster on film page This simply looks better, since the backdrop has a more suitable aspect ratio.
2024-01-02 21:42:35 +00:00
imageSource: Utils.itemBackdropUrl(apiClient.baseUrl, itemData, 0, {"maxWidth": parent.width})
imageBlurhash: itemData.imageBlurHashes["Backdrop"][itemData.backdropImageTags[0]]
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
Minor UI improvements * EpisodePage and FilmPage are now based off VideoPage, since they share a lot of components in common. * The overlay over the thumbnail in PlayToolbar is less obtrusive * Cover shows now the title of the item, and total play time, if applicable * The resume playing section forces all delegates to be square. * The Season page now uses a ListView instead of a ColumnView.
2020-10-01 22:13:05 +00:00
SectionHeader {
text: qsTr("Overview")
}
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
Minor UI improvements * EpisodePage and FilmPage are now based off VideoPage, since they share a lot of components in common. * The overlay over the thumbnail in PlayToolbar is less obtrusive * Cover shows now the title of the item, and total play time, if applicable * The resume playing section forces all delegates to be square. * The Season page now uses a ListView instead of a ColumnView.
2020-10-01 22:13:05 +00:00
PlainLabel {
id: overviewText
Initial step towards the QObject rewrite
2020-10-04 21:03:58 +00:00
text: itemData.overview
Minor UI improvements * EpisodePage and FilmPage are now based off VideoPage, since they share a lot of components in common. * The overlay over the thumbnail in PlayToolbar is less obtrusive * Cover shows now the title of the item, and total play time, if applicable * The resume playing section forces all delegates to be square. * The Season page now uses a ListView instead of a ColumnView.
2020-10-01 22:13:05 +00:00
font.pixelSize: Theme.fontSizeSmall
color: Theme.secondaryHighlightColor
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
}
}
Copy permalink