On Saturday, 20 June 2015 at 16:23:47 UTC, ketmar wrote:
On Sat, 20 Jun 2015 16:18:28 +0000, Kagamin wrote:
Windows API would be similar to X11, where you just specify
everything in pixels and toolkits building on top of it
manually do all the recomputations and layout policies, not
the UI server.
only in windows "toolkit" is built into system. and it can't do
anything except pixels and stupid "dialog units".
Well, it's just windows api was simple enough to be usable
directly, while X11 didn't fly that way and didn't receive
development since everybody used toolkits and all features were
implemented in toolkits, which in the end used X11 as plain
canvas rather than windowing system.
And then it's still not simple: with small font you can put a
lot of information into a window, which simply won't fit with
bigger font size, in this case web gets scrolled naturally,
while native UI clunks interface and truncates strings trying
to fit it into the window.
i lol'd. a typical windows rant, where "toolkits" still doesn't
know about such things as "preferred size", "minimal size", and
can't add scrolling if necessary, choosing to make controls
smaller and smaller instead.
Knowing minimal size won't help you if the amount of information
simply doesn't fit. Dialogs can be scrolled, but master-detail
views can't: master and detail views already reserve scrolling
for themselves, so it can't be reused for the entire window,
well, at least it won't work naturally.
