[Cuis-dev] Fwd: Blueprint – May 2026 update

[Juan Vuletich]

On 2026-06-04 3:56 PM, Juan Vuletich via Cuis-dev wrote:
>> I read up on the scaling problem. From what I read, I assume that the 
>> your intention is to have UI that has dimensions based on the font 
>> size. So when you increase the base font size, the UI scales with 
>> that. And font size takes `hostOSScaleFactor` already into account.
>>
>> Which means to create a rect around the text, e.g. a button, you are 
>> setting the padding that has some fraction of line height, which is 
>> some multiply of font size. This becomes tangled pretty fast.
>>
>> The more direct approach is to factor out the font size. That way you 
>> can use points (logical pixels) for the size of UI (including the 
>> font size) and have independent "zoom factor" that can be 
>> user-definable. And then the system would compute size of 1pt as 
>> `hostOSScaleFactor * zoomFactor` in physical pixels.
>>
>> This is just describing what is sometimes called "density-independent 
>> pixel" (dp on Android), or "effective pixel" (epx on Windows UWP). On 
>> Apple platforms it is just called "point". The independent zoom 
>> factor corrects for inability to know physical dimensions of the 
>> screen and viewing distance. So you can tune the base font size to 
>> be ~0.33°.
>
> Yes. Something like that can be done.
>
And most likely it means building a new UI based on points and not on 
the Real plane (with floating point coordinates). Just a suggestion.

-- 
Juan Vuletich
www.cuis.st
github.com/jvuletich
researchgate.net/profile/Juan-Vuletich
independent.academia.edu/JuanVuletich
patents.justia.com/inventor/juan-manuel-vuletich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20260604/a8102a48/attachment.htm>