azonenberg changed the topic of #scopehal to: ngscopeclient, libscopehal, and libscopeprotocols development and testing | https://github.com/ngscopeclient/scopehal-apps | Logs: https://libera.irclog.whitequark.org/scopehal
<d1b2> <azonenberg> We are currently in a freeze state getting ready for a v0.1 release
<d1b2> <azonenberg> so we want to avoid major changes in the next few weeks
<d1b2> <azonenberg> Once v0.1 ships, GLFW -> SDL is something i have considered for the long term
<d1b2> <azonenberg> there is no formal decision as to whether we will actually execute on it yet, but if you can point to places where GLFW fails and SDL works, that's certainly something to consider
<d1b2> <azonenberg> So if you don't mind sitting on your PR for a few weeks, after v0.1 is out the door I'll definitely play with it
<d1b2> <azonenberg> (we don't have an official release date for v0.1, it's kinda like Debian releases... it'll be done when it's done)
<d1b2> <azonenberg> there's a list of open release blocking bugs and when we've finished those, updated docs, and have no new ones it'll ship
Degi has quit [Ping timeout: 252 seconds]
Degi has joined #scopehal
<d1b2> <josHua> surprising to hear that SDL is better than anything at all in 2024
<d1b2> <hansemro> @azonenberg Sorry for being incredibly slow, but I have done a near-complete conversion to rST markdown + Sphinx: check it out at https://hansemro.github.io/scopehal-docs/index.html; PDF output in the build artifacts (latex/ngscopeclient.pdf): https://github.com/hansemro/scopehal-docs/actions/runs/12387473035. I have not yet handled colored tables for some filters, but will look into it later.
<d1b2> <hansemro> I am also aware of text overlap in the PDF's table of contents due to the large number of filter sections...
<d1b2> <hansemro> Not entirely what to do for that, but I'll look into it
<d1b2> <azonenberg> Keep looking at it. Is this something you can automate and easily sync to ongoing changes I'm making to the docs?
<d1b2> <azonenberg> i'll need to poke around but i think this is likely a good long term direction, however probably something best to push till after v0.1
<d1b2> <hansemro> right
<d1b2> <hansemro> this is for after v0.1
<d1b2> <azonenberg> my focus on docs for v0.1 is just to fix anything obviously out of date and try to get a reasonable level of feature coverage
<d1b2> <azonenberg> then ship it
<d1b2> <azonenberg> I've got a lot more stuff to do as far as release blocking bugs and finishing half-baked stuff like shader grid refactorings for intel gpus
<d1b2> <azonenberg> The target was EOY but it'll probably slip into january the way things are going
<d1b2> <hansemro> You are referring to changes in tex that I should convert to rST in an automated fashion?
<d1b2> <azonenberg> Correct
<d1b2> <azonenberg> or at least, without an excessive amount of manual effort
<d1b2> <hansemro> Converting tables take more effort, but most of the conversion can be done with some regex. I will share scripts when I can
<d1b2> <azonenberg> Sounds good
<d1b2> <hansemro> Table of contents fixed by overriding \sphinxtableofcontents with \tableofcontents and using tocloft package:
<d1b2> <hansemro> Draft .tex to .rst conversion scripts: https://gist.github.com/hansemro/3c7016f216378845625c7ede166f8d98