From owner-freebsd-x11@freebsd.org Mon Jan 28 23:33:46 2019 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7E0714C29B5 for ; Mon, 28 Jan 2019 23:33:46 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [88.98.225.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 9F4E284B60 for ; Mon, 28 Jan 2019 23:33:45 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from crayon2.yoonka.com (crayon2.yoonka.com [10.70.7.20]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id x0SNXbB6091563 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 28 Jan 2019 23:33:37 GMT (envelope-from list1@gjunka.com) Subject: Re: Lumina and env variables To: Ken Moore Cc: freebsd-x11@freebsd.org References: <4c339ec6-b03b-dfe4-f694-af403dc5d89a@gjunka.com> <54013c32-3b8e-4911-bc53-faca7d255c7a@ixsystems.com> <138c2530-22bd-85ec-da4d-0d033fba926c@gjunka.com> <99cd58ec-ba66-4076-883f-9f8a0d1101d7@ixsystems.com> From: Grzegorz Junka Message-ID: <626cbca8-c249-ad26-f53b-b88e489261ce@gjunka.com> Date: Mon, 28 Jan 2019 23:33:37 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.3.2 MIME-Version: 1.0 In-Reply-To: <99cd58ec-ba66-4076-883f-9f8a0d1101d7@ixsystems.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB-large X-Rspamd-Queue-Id: 9F4E284B60 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of list1@gjunka.com designates 88.98.225.149 as permitted sender) smtp.mailfrom=list1@gjunka.com X-Spamd-Result: default: False [-6.80 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:88.98.225.149]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[gjunka.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[gjunka.com]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.85)[-0.849,0]; IP_SCORE(-3.64)[ip: (-9.53), ipnet: 88.98.192.0/18(-4.77), asn: 56478(-3.81), country: GB(-0.09)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:56478, ipnet:88.98.192.0/18, country:GB]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2019 23:33:46 -0000 > Now for the lumina side of things. > 1. Lumina is completely Qt5-based, so the Lumina theme engine is > *only* used for theming Qt5-base applications. This means that KDE4 > applications will not use it (Qt4), Firefox/Chromium will not use it > (GTK2/3), but the Falkon browser *will* use it (Qt5), and many of the > KDE/Plasma5 applications will also use it (Qt5). > > 2. Instead of going for the one-size-fits-all approach to themes that > most engines use, the Lumina theme engine is a fork/update of qt5ct > which is designed around the concept of a single theme engine being > itself configurable. For example, I mentioned the QtCurve engine > previously and it follows the "engine=look" model where if you don't > like it you have to find another engine. qt5ct and lthemeengine take > the approach that we stick to a single toolkit, but expose all of the > configuration options via the engine itself - so a single engine can > have an infinite number of appearance outputs. The only thing the > engine needs to stay in-sync with is the toolkit it is allowing access > to modify. Hi Ken, Many thanks for this comprehensive introduction to theme engines. How does this approach "Lumina theme engine is a fork/update of qt5ct which is designed around the concept of a single theme engine being itself configurable" translates to configuration files? When I change a theme in Lumina Theme Engine does it update only files in .config/lumina-desktop or also in some other folders related to other theme engines? And crucially for my problem, why Lumina Theme Engine behaves differently when it's run from the menu and from the Desktop Configuration tool? I guess it's something to do with environment variables being set differently in those two cases? Thanks GrzegorzJ