D GUI Framework (responsive grid teaser)
Ola Fosheim Grøstad
ola.fosheim.grostad at gmail.com
Thu May 23 19:29:26 UTC 2019
On Thursday, 23 May 2019 at 19:13:11 UTC, Nick Sabalausky
(Abscissa) wrote:
> Serious photographers and videographers use things like JPEG
> and MPEG which are *fundamentally based* on cutting
> imperceptible corners and trading accuracy for other benefits.
> The idea of a desktop GUI absolutely requiring perfect pristine
> accuracy in all things is patently laughable.
What do you mean?
Besides, it is wrong. If you create a font editor you want
accuracy. If you create an image editor you want accuracy. If you
create a proofing application you want accuracy. If you create a
PDF application you want accuracy.
When designing a game, you can adapt your game design to the
provided engine.
Or you can design an engine to fit a type of game design.
When creating a user interface framework you should work with
everything from sound editors, oscilloscopes, image editors,
vector editors, CAD programs, spreadsheets etc.
You cannot really assume much about anything. What you want is
max flexibility.
Most GUI frameworks fail at this, so you have to do all yourself
if you want anything with descent quality, but that is not how it
should be.
Apple's libraries provides options for higher accuracy. This is
good. This is what you want. You don't want to roll your own all
the time because the underlying framework is just "barely
passing" in terms of quality.
More information about the Digitalmars-d-announce
mailing list