On Mon, Oct 5, 2015 at 2:21 PM, Maxim Kovgan <[email protected]> wrote:
> Firstly, it's a lenovo y50-70 laptop. > Interesting. > What I'd really want is NTK (or rather FLTK) to support scalable UI, seems > SVG should be a good candidate, unless you have something else in mind > already. > I have no say in what FLTK does. I'm not sure what you're getting at with SVG. Everything in Non, barring one or two icons icons is entirely vector already and would scale up or down just fine. No need to bring XML anywhere near it. > So the decision how to actually display the graphics should be done based > "on the device", I'd go for a heuristic of resolution+DPI allowing to know > physical size and determine a scaling factor for everything. > This would allow to keep standard proportion of visual objects. > and a "nice to have" - to allow overriding that factor from either apps' > preferences OR via conf file. > So if the user decides to use 100" display, it would be easy to adjust > pixel size of things according to the need at hand. > If you're aware of some reasonable standard heuristic for determining a scaling factor that already exists, I'd be interested in hearing about it. I'm not interested in just making something up, because that's likely to generate more complaints than anything. In my experimental branch, I had a scaling factor added to ntk-chtheme that would impact all NTK programs--but the user would have to go in there and change it. > > > On Mon, Oct 5, 2015 at 11:51 PM, J. Liles <[email protected]> wrote: > >> >> >> On Mon, Oct 5, 2015 at 1:42 PM, Maxim Kovgan <[email protected]> wrote: >> >>> Here's my "Hi" >>> Firstly - kudos for the UI concept and the rather minimal working >>> environment - excellent. >>> My laptop and screen have a resolution of 3840x2160, and non tools look >>> VERY TINY there, >>> Naturally, I'm interested in patching the UI to adopt to my display >>> size, dpi & resolution so the system looks conveniently sized. >>> N.B. >>> If you guys have ideas how and maybe it's part done in someone's >>> branch/fork of the code - I'd be happy to either work on that patch AND/OR >>> test it) >>> pointers would be nice on where the code handling widgets sizing >>> resides, and possibly present refactoring ideas/branches/forks to look at >>> to achieve the above - would be nice. >>> Didn't go through the issues, but I've noticed the FLTK itself is a fork >>> off FLTK, so I guess the only way to understand the fork would be to eat >>> with it :) >>> >>> My availability is an expected one from fully employed deployed family >>> man, but If I start chewing on something - I'm usually finishing it, so >>> it's sporadic, but when my kids wake me up at nights I don't go to sleep >>> right away. >>> >>> Best regards all. >>> >> >> I take it that your laptop has an Apple Retina display? >> >> I've thought about handling this. I actually experimented with some >> changes to NTK a few years ago to scale everything up by a certain >> percentage. But I'm not really sure that's the best thing to do. I have a >> display of the same resolution as yours, but mine is 50", so everything >> looks fine. I can imagine that squeezing that into a 13" laptop screen >> would make everything pretty hard to read... What would you want >> personally? Would having all of the text and graphics scaled up the same >> amount be sufficient? >> >>> >> > > > -- > Maxim Kovgan >
