MobileRead Forums
Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Kobo Reader > Kobo Developer's Corner
Reload this Page Screensaver Patching Question

Notices

Reply
Page 2 of 2 1 2
 
Thread Tools Search this Thread
Old 01-26-2022, 12:51 AM   #16
Semwize
Guru
Semwize ought to be getting tired of karma fortunes by now.Semwize ought to be getting tired of karma fortunes by now.Semwize ought to be getting tired of karma fortunes by now.Semwize ought to be getting tired of karma fortunes by now.Semwize ought to be getting tired of karma fortunes by now.Semwize ought to be getting tired of karma fortunes by now.Semwize ought to be getting tired of karma fortunes by now.Semwize ought to be getting tired of karma fortunes by now.Semwize ought to be getting tired of karma fortunes by now.Semwize ought to be getting tired of karma fortunes by now.Semwize ought to be getting tired of karma fortunes by now.
 
Posts: 914
Karma: 275656
Join Date: Jun 2016
Device: Kobo
Quote:
Originally Posted by Deobulakenyo View Post
aren't those figures/numbers for the width size?
It seemed to me that it was better for Libra to increase the size a little. But if you like it, then that's fine.

Try to increase the size and return the code to the place that you deleted. I don't have Libra on hand - so I won't say the exact figure, but it needs to be increased.
Last edited by Semwize; 01-26-2022 at 12:56 AM.
Semwize is offline   Reply With Quote
Old 01-26-2022, 01:09 AM   #17
Deobulakenyo
Guru
Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.
 
Posts: 706
Karma: 2153490
Join Date: Aug 2021
Location: Stupid Philippines
Device: Kobo Libra 2, Boyue Likebook P78
Quote:
Originally Posted by Semwize View Post
It seemed to me that it was better for Libra to increase the size a little. But if you like it, then that's fine.

Try to increase the size and return the code to the place that you deleted. I don't have Libra on hand - so I won't say the exact figure, but it needs to be increased.

Thank you.

I like it like this.

What i want to do now is transfer the transparency of the Powered OFF panel to the SLEEPING Panel so they have the same transparency. and now i am also thinking of reducing the size of the words "Sleeping" and "Powered-Off" for the heck of it.


Is there a setting/line of code from kobo css (i do not know what i am talking about here) so we can look at the powered off settings (transparency) so we can copy that in the patch code?
Last edited by Deobulakenyo; 01-26-2022 at 01:33 AM.
Deobulakenyo is offline   Reply With Quote
Old 01-29-2022, 11:55 AM   #18
jackie_w
Grand Sorcerer
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 6,251
Karma: 16539642
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by Deobulakenyo View Post
What i want to do now is transfer the transparency of the Powered OFF panel to the SLEEPING Panel so they have the same transparency.
As far as I know, the only code available for patching the "look" of the fullscreen screensaver is contained in a nickel resource (FullScreenDragonPowerView.qss), which I have attached in the spoiler below. As you can see there is no reference to opacity in there. The only reference to transparency is at the top
Code:
* {
  background: transparent;
  color: black;
}
which suggests the whole widget is already as transparent as it can be. I'm guessing that the semi-transparency seen in the default Info Panel (both Sleeping and Powered Off) is handled deeper inside the firmware. If so, it would need a deeper dive into the firmware than a nickel.yaml kobopatch can reach. We'd need one of the more technical gurus to have a look at that if they ever have time.

Quote:
Originally Posted by Deobulakenyo View Post
and now i am also thinking of reducing the size of the words "Sleeping" and "Powered-Off" for the heck of it.
Similarly, you can also see that the only current reference to font-size in resource FullScreenDragonPowerView.qss is for #batteryStatus, which I'd guess is the middle line (Charged: x%) shown in the Info Panel when Sleeping. Therefore I'd guess that the font-size of the top line ('Sleeping' or 'Powered Off' headings) is probably handled by one of the more generic basic widget settings contained in nickel resource default.qss.

Unfortunately there are 90+ possibilities in default.qss. Admittedly, based on their names, some are much more likely candidates than others, but there is still an element of "looking for a needle in a haystack" by patching font-size, one item at a time, followed by checking whether the words 'Sleeping'/'Powered Off' changed size - until you find the right one. This is more effort than I'm personally prepared to spend at the moment.

Another consideration is that changing these basic generic widgits may affect the appearance of multiple parts of the GUI, not just the bit you wanted. This is unlikely to be disastrous but people are picky (they probably wouldn't be using kobopatch if they weren't picky ) and is the reason why I haven't included more patches to default.qss in the standard kobopatch pack.

Code for nickel resource FullScreenDragonPowerView.qss in both fw 4.30.xxxxx and 4.31.xxxxx
Spoiler:
Code:
* {
  background: transparent;
  color: black;
}
*[powerOffView=true] {
  color: white;
}
#infoWidget[qApp_deviceIsTrilogy=true] {
  max-width: 300px;
  min-width: 300px;
}
#infoWidget[qApp_deviceIsPhoenix=true] {
  max-width: 380px;
  min-width: 380px;
}
#infoWidget[qApp_deviceIsDragon=true] {
  max-width: 470px;
  min-width: 470px;
}
#infoWidget[qApp_deviceIsDaylight=true] {
  max-width: 611px;
  min-width: 611px;
}
#infoWidget[qApp_deviceIsTrilogy=true],
#infoFrame[qApp_deviceIsTrilogy=true] {
  qproperty-topMargin: 12px;
  qproperty-bottomMargin: 12px;
}
#infoWidget[qApp_deviceIsPhoenix=true],
#infoFrame[qApp_deviceIsPhoenix=true] {
  qproperty-topMargin: 16px;
  qproperty-bottomMargin: 16px;
}
#infoWidget[qApp_deviceIsDragon=true],
#infoFrame[qApp_deviceIsDragon=true] {
  qproperty-topMargin: 22px;
  qproperty-bottomMargin: 22px;
}
#infoWidget[qApp_deviceIsDaylight=true],
#infoFrame[qApp_deviceIsDaylight=true] {
  qproperty-topMargin: 28px;
  qproperty-bottomMargin: 28px;
}
#infoWidget[qApp_deviceIsStorm=true],
#infoFrame[qApp_deviceIsStorm=true] {
  qproperty-topMargin: 25px;
  qproperty-bottomMargin: 25px;
}
#infoWidget[qApp_deviceIsTrilogy=true],
#infoFrame[qApp_deviceIsTrilogy=true] {
  qproperty-rightMargin: 12px;
}
#infoWidget[qApp_deviceIsPhoenix=true],
#infoFrame[qApp_deviceIsPhoenix=true] {
  qproperty-rightMargin: 16px;
}
#infoWidget[qApp_deviceIsDragon=true],
#infoFrame[qApp_deviceIsDragon=true] {
  qproperty-rightMargin: 22px;
}
#infoWidget[qApp_deviceIsDaylight=true],
#infoFrame[qApp_deviceIsDaylight=true] {
  qproperty-rightMargin: 28px;
}
#infoWidget[qApp_deviceIsStorm=true],
#infoFrame[qApp_deviceIsStorm=true] {
  qproperty-rightMargin: 25px;
}
#infoFrame {
  border-top: 1px solid black;
  border-bottom: 1px solid black;
  border-right: 1px solid black;
}
#infoFrame[qApp_deviceIsTrilogy=true] {
  qproperty-leftMargin: 24px;
}
#infoFrame[qApp_deviceIsPhoenix=true] {
  qproperty-leftMargin: 32px;
}
#infoFrame[qApp_deviceIsDragon=true] {
  qproperty-leftMargin: 44px;
}
#infoFrame[qApp_deviceIsDaylight=true] {
  qproperty-leftMargin: 56px;
}
#infoFrame[qApp_deviceIsStorm=true] {
  qproperty-leftMargin: 50px;
}
#infoFrame[powerOffView=true] {
  border-top: 1px solid white;
  border-bottom: 1px solid white;
  border-right: 1px solid white;
}
#batteryStatus {
  font-family: Georgia;
}
#batteryStatus[localeName="ja"] {
  font-family: Sans-SerifJP, sans-serif;
  font-style: normal;
}
#batteryStatus[localeName="zh"] {
  font-family: Sans-SerifZH-Simplified, sans-serif;
  font-style: normal;
}
#batteryStatus[localeName="zh-HK"] {
  font-family: Sans-SerifZH-Traditional, sans-serif;
  font-style: normal;
}
#batteryStatus[localeName="zh-TW"] {
  font-family: Sans-SerifZH-Traditional, sans-serif;
  font-style: normal;
}
#batteryStatus[qApp_deviceIsTrilogy=true] {
  font-size: 17px;
}
#batteryStatus[qApp_deviceIsPhoenix=true] {
  font-size: 22px;
}
#batteryStatus[qApp_deviceIsDragon=true] {
  font-size: 26px;
}
#batteryStatus[qApp_deviceIsAlyssum=true] {
  font-size: 30px;
}
#batteryStatus[qApp_deviceIsNova=true] {
  font-size: 30px;
}
#batteryStatus[qApp_deviceIsStorm=true] {
  font-size: 30px;
}
#batteryStatus[qApp_deviceIsDaylight=true] {
  font-size: 34px;
}
#batteryStatus[qApp_deviceIsTrilogy=true] {
  margin-left: 12px;
}
#batteryStatus[qApp_deviceIsPhoenix=true] {
  margin-left: 16px;
}
#batteryStatus[qApp_deviceIsDragon=true] {
  margin-left: 22px;
}
#batteryStatus[qApp_deviceIsDaylight=true] {
  margin-left: 28px;
}
#batteryStatus[qApp_deviceIsStorm=true] {
  margin-left: 25px;
}
#progressLabel[qApp_deviceIsTrilogy=true] {
  margin-top: 6px;
}
#progressLabel[qApp_deviceIsPhoenix=true] {
  margin-top: 8px;
}
#progressLabel[qApp_deviceIsDragon=true] {
  margin-top: 10px;
}
#progressLabel[qApp_deviceIsDaylight=true] {
  margin-top: 13px;
}
#progressLabel[qApp_deviceIsStorm=true] {
  margin-top: 11px;
}
#batteryStatus[iconView=true][qApp_deviceIsTrilogy=true] {
  margin-left: 6px;
}
#batteryStatus[iconView=true][qApp_deviceIsPhoenix=true] {
  margin-left: 8px;
}
#batteryStatus[iconView=true][qApp_deviceIsDragon=true] {
  margin-left: 10px;
}
#batteryStatus[iconView=true][qApp_deviceIsDaylight=true] {
  margin-left: 13px;
}
#batteryStatus[iconView=true][qApp_deviceIsStorm=true] {
  margin-left: 11px;
}
jackie_w is offline   Reply With Quote
Old 01-29-2022, 08:20 PM   #19
Deobulakenyo
Guru
Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.Deobulakenyo ought to be getting tired of karma fortunes by now.
 
Posts: 706
Karma: 2153490
Join Date: Aug 2021
Location: Stupid Philippines
Device: Kobo Libra 2, Boyue Likebook P78
Quote:
Originally Posted by jackie_w View Post
As far as I know, the only code available for patching the "look" of the fullscreen screensaver is contained in a nickel resource (FullScreenDragonPowerView.qss), which I have attached in the spoiler below. As you can see there is no reference to opacity in there. The only reference to transparency is at the top
Code:
* {
  background: transparent;
  color: black;
}
which suggests the whole widget is already as transparent as it can be. I'm guessing that the semi-transparency seen in the default Info Panel (both Sleeping and Powered Off) is handled deeper inside the firmware. If so, it would need a deeper dive into the firmware than a nickel.yaml kobopatch can reach. We'd need one of the more technical gurus to have a look at that if they ever have time.



Similarly, you can also see that the only current reference to font-size in resource FullScreenDragonPowerView.qss is for #batteryStatus, which I'd guess is the middle line (Charged: x%) shown in the Info Panel when Sleeping. Therefore I'd guess that the font-size of the top line ('Sleeping' or 'Powered Off' headings) is probably handled by one of the more generic basic widget settings contained in nickel resource default.qss.

Unfortunately there are 90+ possibilities in default.qss. Admittedly, based on their names, some are much more likely candidates than others, but there is still an element of "looking for a needle in a haystack" by patching font-size, one item at a time, followed by checking whether the words 'Sleeping'/'Powered Off' changed size - until you find the right one. This is more effort than I'm personally prepared to spend at the moment.

Another consideration is that changing these basic generic widgits may affect the appearance of multiple parts of the GUI, not just the bit you wanted. This is unlikely to be disastrous but people are picky (they probably wouldn't be using kobopatch if they weren't picky ) and is the reason why I haven't included more patches to default.qss in the standard kobopatch pack.

Code for nickel resource FullScreenDragonPowerView.qss in both fw 4.30.xxxxx and 4.31.xxxxx
Spoiler:
Code:
* {
  background: transparent;
  color: black;
}
*[powerOffView=true] {
  color: white;
}
#infoWidget[qApp_deviceIsTrilogy=true] {
  max-width: 300px;
  min-width: 300px;
}
#infoWidget[qApp_deviceIsPhoenix=true] {
  max-width: 380px;
  min-width: 380px;
}
#infoWidget[qApp_deviceIsDragon=true] {
  max-width: 470px;
  min-width: 470px;
}
#infoWidget[qApp_deviceIsDaylight=true] {
  max-width: 611px;
  min-width: 611px;
}
#infoWidget[qApp_deviceIsTrilogy=true],
#infoFrame[qApp_deviceIsTrilogy=true] {
  qproperty-topMargin: 12px;
  qproperty-bottomMargin: 12px;
}
#infoWidget[qApp_deviceIsPhoenix=true],
#infoFrame[qApp_deviceIsPhoenix=true] {
  qproperty-topMargin: 16px;
  qproperty-bottomMargin: 16px;
}
#infoWidget[qApp_deviceIsDragon=true],
#infoFrame[qApp_deviceIsDragon=true] {
  qproperty-topMargin: 22px;
  qproperty-bottomMargin: 22px;
}
#infoWidget[qApp_deviceIsDaylight=true],
#infoFrame[qApp_deviceIsDaylight=true] {
  qproperty-topMargin: 28px;
  qproperty-bottomMargin: 28px;
}
#infoWidget[qApp_deviceIsStorm=true],
#infoFrame[qApp_deviceIsStorm=true] {
  qproperty-topMargin: 25px;
  qproperty-bottomMargin: 25px;
}
#infoWidget[qApp_deviceIsTrilogy=true],
#infoFrame[qApp_deviceIsTrilogy=true] {
  qproperty-rightMargin: 12px;
}
#infoWidget[qApp_deviceIsPhoenix=true],
#infoFrame[qApp_deviceIsPhoenix=true] {
  qproperty-rightMargin: 16px;
}
#infoWidget[qApp_deviceIsDragon=true],
#infoFrame[qApp_deviceIsDragon=true] {
  qproperty-rightMargin: 22px;
}
#infoWidget[qApp_deviceIsDaylight=true],
#infoFrame[qApp_deviceIsDaylight=true] {
  qproperty-rightMargin: 28px;
}
#infoWidget[qApp_deviceIsStorm=true],
#infoFrame[qApp_deviceIsStorm=true] {
  qproperty-rightMargin: 25px;
}
#infoFrame {
  border-top: 1px solid black;
  border-bottom: 1px solid black;
  border-right: 1px solid black;
}
#infoFrame[qApp_deviceIsTrilogy=true] {
  qproperty-leftMargin: 24px;
}
#infoFrame[qApp_deviceIsPhoenix=true] {
  qproperty-leftMargin: 32px;
}
#infoFrame[qApp_deviceIsDragon=true] {
  qproperty-leftMargin: 44px;
}
#infoFrame[qApp_deviceIsDaylight=true] {
  qproperty-leftMargin: 56px;
}
#infoFrame[qApp_deviceIsStorm=true] {
  qproperty-leftMargin: 50px;
}
#infoFrame[powerOffView=true] {
  border-top: 1px solid white;
  border-bottom: 1px solid white;
  border-right: 1px solid white;
}
#batteryStatus {
  font-family: Georgia;
}
#batteryStatus[localeName="ja"] {
  font-family: Sans-SerifJP, sans-serif;
  font-style: normal;
}
#batteryStatus[localeName="zh"] {
  font-family: Sans-SerifZH-Simplified, sans-serif;
  font-style: normal;
}
#batteryStatus[localeName="zh-HK"] {
  font-family: Sans-SerifZH-Traditional, sans-serif;
  font-style: normal;
}
#batteryStatus[localeName="zh-TW"] {
  font-family: Sans-SerifZH-Traditional, sans-serif;
  font-style: normal;
}
#batteryStatus[qApp_deviceIsTrilogy=true] {
  font-size: 17px;
}
#batteryStatus[qApp_deviceIsPhoenix=true] {
  font-size: 22px;
}
#batteryStatus[qApp_deviceIsDragon=true] {
  font-size: 26px;
}
#batteryStatus[qApp_deviceIsAlyssum=true] {
  font-size: 30px;
}
#batteryStatus[qApp_deviceIsNova=true] {
  font-size: 30px;
}
#batteryStatus[qApp_deviceIsStorm=true] {
  font-size: 30px;
}
#batteryStatus[qApp_deviceIsDaylight=true] {
  font-size: 34px;
}
#batteryStatus[qApp_deviceIsTrilogy=true] {
  margin-left: 12px;
}
#batteryStatus[qApp_deviceIsPhoenix=true] {
  margin-left: 16px;
}
#batteryStatus[qApp_deviceIsDragon=true] {
  margin-left: 22px;
}
#batteryStatus[qApp_deviceIsDaylight=true] {
  margin-left: 28px;
}
#batteryStatus[qApp_deviceIsStorm=true] {
  margin-left: 25px;
}
#progressLabel[qApp_deviceIsTrilogy=true] {
  margin-top: 6px;
}
#progressLabel[qApp_deviceIsPhoenix=true] {
  margin-top: 8px;
}
#progressLabel[qApp_deviceIsDragon=true] {
  margin-top: 10px;
}
#progressLabel[qApp_deviceIsDaylight=true] {
  margin-top: 13px;
}
#progressLabel[qApp_deviceIsStorm=true] {
  margin-top: 11px;
}
#batteryStatus[iconView=true][qApp_deviceIsTrilogy=true] {
  margin-left: 6px;
}
#batteryStatus[iconView=true][qApp_deviceIsPhoenix=true] {
  margin-left: 8px;
}
#batteryStatus[iconView=true][qApp_deviceIsDragon=true] {
  margin-left: 10px;
}
#batteryStatus[iconView=true][qApp_deviceIsDaylight=true] {
  margin-left: 13px;
}
#batteryStatus[iconView=true][qApp_deviceIsStorm=true] {
  margin-left: 11px;
}

Thank you very much. Now i understand. I am now happy enough with the size reduction thanks to you and Semwise who took the time to explain thiss to me.

Deobulakenyo is offline   Reply With Quote
Reply
Page 2 of 2 1 2

« Previous Thread | Next Thread »

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Patching H2O Maillemom Kobo Developer's Corner 8 10-19-2016 09:58 AM
Instructions for patching firmware 3.13.1 GeoffR Kobo Developer's Corner 56 07-01-2016 09:59 AM
Instructions for patching firmware 3.17.0 GeoffR Kobo Developer's Corner 49 08-16-2015 05:20 AM
Hacks Screensaver question yankgirl Amazon Kindle 1 08-07-2009 12:09 PM


All times are GMT -4. The time now is 04:37 PM.

Contact Us - FAQ - Guidelines - Privacy - Top

MobileRead.com is a privately owned, operated and funded community.