<pca006132>
not sure where we should triage blocking issues, so I will do it here
<pca006132>
https://github.com/openscad/openscad/issues/5689: I don't think this should be a blocker. The geometry is valid, the triangulation can probably be improved but that requires changing the triangulator quite a bit
<pca006132>
*manifold's triangulator, not openscad's
<pca006132>
the problem is really about degenerate triangles in that case, because the CGAL one generated tons of degenerates, but is better in terms of Delaunay condition
Jerr8 has quit [Remote host closed the connection]
Jerr8 has joined #openscad
snaked has joined #openscad
ccox has quit [Remote host closed the connection]
ccox has joined #openscad
pah_ is now known as pa
pa has quit [Changing host]
pa has joined #openscad
mmu_man has joined #openscad
peeps[zen] has quit [Quit: Connection reset by peep]
peepsalot has joined #openscad
Guest94 has joined #openscad
Guest94 has quit [Client Quit]
howiemnt4 has joined #openscad
howiemnt1 has quit [Ping timeout: 245 seconds]
bitbasher has quit [Ping timeout: 252 seconds]
howiemnt4 has quit [Remote host closed the connection]
howiemnt has joined #openscad
bitbasher has joined #openscad
peepsalot has quit [Remote host closed the connection]
peepsalot has joined #openscad
<bitbasher>
hi folks
<bitbasher>
sorry if it seemed that i was offline .. well, i was sort of .. had family stuff to do all weekend so i did not see the cheat sheet issue blowing up
<bitbasher>
so .. as my apologies are already published .. i am planning to apply all of the info i have learned and feedback i have been given over the next few days
<bitbasher>
which will include a new version of the cheat sheet (currently in progress on my fork of the scad website
<bitbasher>
unless i am told otherwise by the community .. it is a wiki so everyone (with correct permissions) is welcome to make corrections or revert what they dont like .. or keep informing me about anything "bad" so i can fix it
<J25K91>
just let us know if your time frame didn't work as you expect it
<J25K91>
It is great that you put efforts into this, unlucky that you scrambled the live experience a bit
<bitbasher>
well .. heh .. my time frame started as "oh just a few tweaks where my testing showed the docs to be wrong/incomplete" .. that was back in April ..
<J25K91>
your time frame fixing it - it would be terrible to waste all your work by reverting so this should be avoided at all costs
<bitbasher>
i did overlook the links to the cheat sheet .. most of the original pages are still here so i dont think ALL the links broke .. and i did not understand what the {{anchor blah blah}} things were doing .. somehow i did not connect those to HTML anchors, which i do know well .. senior moment ? brain fart
<bitbasher>
time frame is the next few days
<J25K91>
i tried a few and all broke .. some even pointed to websites were the information was removed (not just the anchor or changed heading)
<bitbasher>
like by next weekend .. as a pensioner who finds not much good to watch on telly having a docs update hobby keeps me feeling useful
J25K91 has quit [Quit: Client closed]
J25K has joined #openscad
<bitbasher>
i found a bunch of missing pages on other sites too .. fixed what i could
bitbasher has quit [Changing host]
bitbasher has joined #openscad
<J25K>
we had the problem in the past when people changed headings so we introduced the anchors
<bitbasher>
is there a list of the anchors needed? or is it just all the links in the CS point to anchors?
<bitbasher>
at the moment i need to get offline and get to my workshop .. things to do IRL
<bitbasher>
and .. what is ur id on github please?
<bitbasher>
i am bitbasher there and vulcan_ or even bytebasher in some places
<J25K>
anchors were used when names contain characters like _ $ or when multiple entries need to point to the same lemma
<bitbasher>
ok .. i see that
teepee_ has joined #openscad
<J25K>
or when a user thought the lemma need a different heading so instead of changing the links on the cheat it made sense to keep the proper name of the function
<bitbasher>
oh .. i just now .. finally -- found the anchor template page on wikipedia so i can read up on that
<J25K>
wiki creates anchors for every heading .. so you just add more
<J25K>
.. but in general if you see something you don't fully understand - don't remove it
teepee has quit [Ping timeout: 240 seconds]
teepee_ is now known as teepee
<J25K>
.. i am looking forward how the new wiki structure and cheat sheet structure looks like
<bitbasher>
and re-reading your linked page .. i rem thinking i might have damaged some pages that i was putting transclusions into .. and forgot to check the revision history to see what pages looked like before me
<bitbasher>
well thanks !! that is so nice to hear
<bitbasher>
i can tell you i am not happy with my top level page "OpenSCAD User Manual" and the top page of the language ref .. the old versions were (IMHO) to verbose and untidy .. but i now see i have gone too much the other way
<bitbasher>
now i have to go .. laters
<J25K>
Ü .. well hope we improve
j45_ has joined #openscad
j45 has quit [Ping timeout: 248 seconds]
j45_ is now known as j45
j45 has quit [Changing host]
j45 has joined #openscad
bitbasher has quit [Ping timeout: 248 seconds]
<pca006132>
IMO a reference manual is something that basically tells you how to implement something with the same behavior
<pca006132>
you have to find the algorithms, but things that affect the user should be documented
<pca006132>
examples are supplementary, you should be able to understand things (probably requires more effort) even without examples