Re: D GUI Framework (responsive grid teaser)
On Tuesday, 28 May 2019 at 05:52:23 UTC, Ola Fosheim Grøstad wrote: Also embedded have fixed screen dimensions... No need for real time resizing... Every element that can include other elements and can be resized behaves *the same* as the resizable main window. Examples: floating window, docked window, SplitView, table's column. You can change the element dimensions programmatically - directly or via styling, maybe with transition effects. They can be dependent on each other or on the parent/sibling dimensions. In all these cases, the computations layout engine performs are the same. What is certain is that the long page browser layout engine isn't very well suited for fixed dimensions... Why fixed screen device cannot have scrolling? Logic?
Re: dlang.ru is updated
On Friday, 17 May 2019 at 13:39:35 UTC, drug wrote: First of all, you are totally wrong. Crimea ... It's not a fact, it's just your opinion, very similar to one that russian federal TV transmits. And the last but no least - nobody suppresses me or my friends in Russia. Have you ever been in Russia? What will you say when all the foreign Internet gets blocked? When the borders get closed? When Putin meddles into one more needless conflict? I don't see anything wrong in blocking illegal site like site about narcotic drugs, arms trafficking and so on. Don't you see something wrong in blocking LinkedIn, Telegram? In trying to block Wikipedia, YouTube? And you feel it's okay that some increadibly corrupted people have a power to decide, what you should see, and what not? But the world is too complex to guilt Putin into doing it. It's really funny. No doubts. It's also funny how you are trying to justify that very nice government.
Re: Blog post: What D got wrong
On Thursday, 13 December 2018 at 18:29:39 UTC, Adam D. Ruppe
wrote:
I wanna show you something:
/// Static convenience functions for common color names
nothrow pure @nogc @safe
static Color transparent() { return Color(0, 0, 0, 0); }
Enums could resolve this particular case.
My thought on this situation is to implement tuple expansion in
attributes just like in function parameters, and complete
DIP1012. Then we can write so:
---
alias noble = AliasSeq!(pure, nothrow, nogc, safe);
int queryStuff() const @noble
{
...
}
---
Re: Blog post: What D got wrong
On Tuesday, 11 December 2018 at 13:42:03 UTC, Guillaume Piolat wrote: One could say getters and particularly setters don't really deserve a nicer way to write them. It's a code stink, it deserve a long ugly name. (10 years ago I would be in the other camp) Can you please explain it in more detail? I never read such about getters and setters.
