15:56 <mePy2[m]> Nice!

15:56 <mePy2[m]> Nice to see activities here :P xD

15:56 <mePy2[m]> @white

15:58 <mePy2[m]> whitequark: About the macOS flickering. Maybe it is related to OpenGL. How can I start moving the project to Metal?

15:58 <mePy2[m]> I am a totally beginner. Quite. I think a “guide” to the code would be nice.

16:14 <rpavlik> fwiw - I've been using master for at least a year now, and though it might not be a tagged release it's certainly quite usable, and quite an improvement over the last tag. Don't mistake the lack of tags for lack of activity :)

16:16 <rpavlik> mePy2[m]: I haven't looked at the render APIs to know how closely they are tied to OpenGL conventions, but the rendering code is fairly separate: mac-specific code is in https://github.com/solvespace/solvespace/tree/master/src/platform while you can see the OpenGL 1 and OpenGL 3 render backends in https://github.com/solvespace/solvespace/tree/master/src/render

16:22 <mePy2[m]> All of that is about the macOS version?

16:23 <mePy2[m]> The problem with the macOS version is quite common I think. The flickering of the window while resizing it.

16:24 <mePy2[m]> Also, it seems quite “easy” to port from OpenGL to Metal.

16:24 <mePy2[m]> API

16:51 <mePy2[m]> (They said easy xD I know it is not.)

16:53 <mePy2[m]> I insist saying this: I do not have time and/or motivation to study the code. But I would like very much and it would be much more pleasant to just read a book about the project code.

16:53 <mePy2[m]> “Once upon a time... ”

17:16 <ppd> so you want to port SolveSpace to Metal, hardly a beginner project, but you don't want to read the existing code. Is that correct?

17:21 <mePy2[m]> xD

17:22 <mePy2[m]> It’s not I do not want to read the code...

17:22 <mePy2[m]> I need just the “carrot” to begin the journey

17:23 <mePy2[m]> I think something easier to read to just start getting into the project would be nice

17:23 <mePy2[m]> In plain english, with not much of code in it.

18:01 <ppd> true :)

18:27 <mePy2[m]> (I would like to help in this, but I would need to interview as many of you as possible. And it will take some time. But I am confident the result would be nice and I hope appreciated.

18:27 <mePy2[m]> The aim is to make something, a book indeed, to make easier for new people to contribute to the project. Or at least, see what’s going on under the hood in their CPU)

18:28 <mePy2[m]> * (I would like to help in this, but I would need to interview ~~as many of you as possible~~ nah, theoretically I just need one person who truly and deeply knows the code. And it will take some time. But I am confident the result would be nice and I hope appreciated.

18:28 <mePy2[m]> The aim is to make something, a book indeed, to make easier for new people to contribute to the project. Or at least, see what’s going on under the hood in their CPU)

21:29 <whitequark> mePy2[m]: if you do not have time or motivation to study the code I would prefer if you did not contribute to it, to put it bluntly

21:29 <whitequark> there are few developers, I am especially overloaded in the last several months, and I will not have the capacity to review your changes.

21:31 <whitequark> regarding the Metal port specifically, given the overall extreme hostility of Apple to OSS developers I see little point in adding a port to a new graphics API that ~none of us understand or can maintain

21:31 <whitequark> a port to Vulkan plus MoltenVK would make a lot more sense

21:34 <whitequark> ... "last several years" would be more honest at this point

21:44 <whitequark> mePy2[m]: so just to provide some context, it took me something like a year to really understand the codebase, and i was able to work full-time back then

21:44 <whitequark> i no longer can due to worse health, and i also have major other workloads that i need to be able to afford food

21:44 <whitequark> there is absolutely no way i can spend months helping someone writing a book

21:45 <whitequark> not even mentioning that this would eat into the time I could use to actually maintain the project

23:10 <_whitenotifier-f> [solvespace] phkahler opened pull request #626: Fix issue #295 keep circles to 16 edges minimum. - https://git.io/JfXFu

23:10 <_whitenotifier-f> [solvespace] Success. Contributor License Agreement is signed. - https://cla-assistant.io/solvespace/solvespace?pullRequest=626

23:11 <_whitenotifier-f> [solvespace] whitequark commented on pull request #626: Fix issue #295 keep circles to 16 edges minimum. - https://git.io/JfXFV

23:11 <_whitenotifier-f> [solvespace] whitequark edited a comment on pull request #626: Fix issue #295 keep circles to 16 edges minimum. - https://git.io/JfXFV

23:12 <_whitenotifier-f> [solvespace] phkahler commented on issue #295: Circle rendering is very conservative - https://git.io/JfXFo

23:23 <_whitenotifier-f> [solvespace] Failure. The Travis CI build failed - https://travis-ci.org/github/solvespace/solvespace/builds/694841755?utm_source=github_status&utm_medium=notification

23:24 <_whitenotifier-f> [solvespace] Failure. AppVeyor build failed - https://ci.appveyor.com/project/whitequark/solvespace/builds/33327833

23:56 <_whitenotifier-f> [solvespace] phkahler opened pull request #627: default chordTol=0.2% max segments=20 - https://git.io/JfXNY

23:56 <_whitenotifier-f> [solvespace] Success. Contributor License Agreement is signed. - https://cla-assistant.io/solvespace/solvespace?pullRequest=627