You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Polish. Thanks to DriftEngineer, who translated it (pull request #4)! It comes with its own plural rule (1 zdjęcie, 3 zdjęcia, 5 zdjęć, 22 zdjęcia, but 21 zdjęć, not like Russian). The texts added in 1.9.2 were translated here; corrections are welcome.
How the launcher opens, chosen on the TV: Settings → Home screen → How the launcher opens lists four ways, each with how it works, its pros and its cons. OK twice switches; the way that is on is switched off and checked first, and a way that does not take is undone (tools/homemode.sh, packaged in the app's tools/ folder).
Official: webOS's own choice of Home app (appCategory: ["home"] and setDefaultApp, tools/defaulthome.sh; the method of Lumen's docs/native-home.md). Nothing mounted, and it lasts across a full restart. A boot link gives LG Home back if the launcher has been uninstalled.
Swap: tools/takeover.sh, as before. Helper: the Home key helper (version 18 stands down while the official way is on). Off.
Pixel shift (OLED) (Settings → Appearance: Auto, On or Off): the clock, the cards and the apps move a few whole pixels once a minute round a loop of eight places (Hearth's idea). It follows the clock's own once-a-minute redraw, so it costs no timer. Auto (the default) switches it on when the TV's model name starts with OLED (asked once, getSystemInfo modelName).
App names: all, the selected one only, or none (Settings → Appearance → App names). With the selected one only, the others keep their room, so nothing moves.
Sharper on the TV: nothing with text is scaled any more but the focused card (Settings rows, pickers; the selected app's icon still grows, its name stays at its size), and the app row, the dialog and the toast sit on whole pixels (no translate(-50%), rounded offsets). Text drawn at fractional positions or scales is soft through the TV's 2x scale-up of its 1080p picture.
Start-up picture (Settings → Wallpaper): what the TV shows for a moment while the launcher starts after being unloaded: the wallpaper (the default), the logo card or black. The picture (splash-wallpaper.jpg) is written into the installed app's folder (as Luma does); the wallpaper's copy is the one the launcher already keeps for its own fast start. The Swap's copy of LG Home now shows it too (takeover.sh: splashBackground instead of noSplashOnLaunch).
The frosted glass changes with the wallpaper: it starts to fade in the same frame as the picture (the plate sets its layer up while it renders, not after the next paint), and at start it comes from the cache with the picture instead of being worked out from it again a moment later. The plate's colour is drawn in the same two layers, so a light plate turns dark in the same fade instead of at once, and the new glass fades in over the old one (the sharp wallpaper no longer shows through half-way). The rim (the bright top edge) stays above both layers.
Frost (Settings → Appearance, under Frosted glass): how much the glass blurs the picture behind it, 100% (as before) down to 30%. A change remakes the glass of the picture on screen at once; the saved glass for the fast start is kept per setting.
The clock's digits are centred in their card by what the font really draws (measured on the canvas), not by where its line box puts them: the time and the date move together by whole pixels. Fonts with low digits (Cormorant, Roboto Mono, the TV's own) sat low before. Web views too old to measure text (Chrome 53) keep the layout as it was.
More of the screen on whole pixels: the clock's date (the time's width is rounded up), Settings' headings, rows, values, buttons and pickers (whole-pixel line heights; button and value widths rounded up by useSnapWidths) and the toast (an even width).
Updates reach a launcher that stayed loaded: each build writes its id to assets/version.txt; the launcher reads it whenever it goes to the background or is relaunched and loads itself again when another build is on disk (a rebuild of the same version too). Before, the TV kept the old version running (above all the Swap's copy behind the Home button) until it was fully restarted. An update from 1.9.1 or older still needs that one restart, as those versions don't check. npm run install:tv also closes the launcher and the Swap's copy, so the new version loads without restarting the TV; AGENTS.md says how to do the same after installing another way.
The official way works on a TV whose list of default apps names no Home app (as out of the box: LG Home is then Home); it was refused with "could not read the TV's default apps".
A switch of the way that fails turns the way that was on back on (it was left with none), and the Home key helper setting is changed only when a switch worked.
Tests run on macOS too (timeout falls back to perl).