elf
/
xcb-studies
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed a typo in the Journal

This commit is contained in:
Elf M. Sternberg 2022-02-24 17:12:52 -08:00
parent abdc9f184f
commit a97a52c9a5
1 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/Progress.md
View File

@ -24,11 +24,11 @@ doesn't help you understand how to use the library. `XCBWrapper` is
an excellent example of how to use XCB, but it uses some fairly
high-level C++ to accomplish all that it does, and untangling the
relationship between the wrapper template, the macro that does wrapper
declarations, and the XCB Reference; once you find the insight that
XCB's declarations are all derived from a massive XML file, you can
start to understand that XCBWrapper exploits the patterns produced by
the derivative file, but it requires insight and effort that's
unrelated to understanding XCB in the first place.
declarations, and the XCB Reference, was quite a challenge; once you
find the insight that XCB's declarations are all derived from a
massive XML file, you can start to understand that XCBWrapper exploits
the patterns produced by the derivative file, but it requires insight
and effort that's unrelated to understanding XCB in the first place.
This project does show the usual trajectory of one of my learning
exercises, especially since I'm fond of delving in places where no man
@ -37,3 +37,8 @@ now it's all starting to make sense. I also note that I'm doing
_better_ than a lot of the open-source examples, in that I'm batching
many of my requests before processing them. I'm not batching storing
the replies yet, but I don't see why that couldn't happen.
I did attempt at one point to start using `std::unique_ptr` to
automatically free `_reply_t` objects that XCB allocated for me, but
after playing with them for an hour or so my initial impression is
that I'm utterly thrilled with Rust's ergonomics. Just sayin'.