On Thursday, 15 August 2013 at 01:03:24 UTC, Tyler Jameson Little
wrote:
However, Windows doesn't have this workflow, so mirroring the
entire desktop became necessary.
It does now, Server 2008 I think was the first one, or maybe
Windows 7, they call it Seamless RDP.
In a widget toolkit, I think the same applies: make just enough
controls that most people are satisfied, then make the toolkit
easy to extend with custom controls.
Yeah, and that's a much more modest goal too.
BTW I spent a couple more hours on my crappygui.d today. No
network transparency here, just drawing non-native widgets. So
yeah it sucks, but it is small, simple, and standalone. Take a
look at this screenie!
http://arsdnet.net/gui2.png
My keyboard is literally falling apart and backspace doesn't work
in the text edit yet (big downside of non-native widgets, the
behavior is hard to get right)... so not much of an edit lol...
but yeah it is moving along. I think by the end of this weekend,
it will be good enough for me and I'll put the code on my misc
github.
The event model is lifted from javascript:
button.addEventListener("click", { window.close(); });
and mouseenter, keydown, etc. are implemented too. It does the
capture, bubble, preventDefault, stopPropagation, just like the
w3c dom. I kinda like that model.
