@Skytrias [1/n] I haven't covered that yet (I will probably do it in the next part), but I control properties like size, colors, fonts, and some other things with stacks. So, for example, you might push a default size for each axis on the stack (as well as a default font, etc.), then...
@Skytrias [2/n] ...if you want to deviate a size, color, font, etc. for a button, you would just push a new value onto the associated stack before the button call, and then pop afterwards.
@Skytrias [3/n] I am really not that big of a "go nuts with C macros" guy, but there's one exception, and that's these widget property stacks. It all comes down to this:
@AbnerCoimbre@notnullnotvoid@handmade_net I will provide my personal thoughts about Handmade, and maybe we can work towards an understanding of the manifesto, if/how it should be revised, etc. (1/7)
@AbnerCoimbre@notnullnotvoid@handmade_net My experiences with @handmade_net have provided a lot of insight here, namely in that Handmade *isn't* just about making things fast, it's about knowing when to allow things to be slow, and reasoning about reality. I like @AbnerCoimbre's "computer literacy" idea here. (2/7)
@AbnerCoimbre@notnullnotvoid@handmade_net "Handmade" isn't exactly rigorously defined, though I think it's more important that we gather as a community, dedicate ourselves to making better software, caring about the end user, and wanting to understand the reality of our problems. (3/7)