07:50 <J1A84> hm

08:07 <J1A84> teepee  the scadvent script is updating automatically or did i need to do something (or you)   (added an entry and squeeze between yours to spread them a little more)

08:16 <teepee> deployment is manual, but I guess we need to give it some sorting anyway, right now it's just in order of the readme, I did not look in detail

08:25 <J1A84> ok ..  just tried to follow the "process"

08:27 <J1A84> ... we could make an backup scadvent that shuffle all previous years and select one if a day isn't filled - Ü

12:19 <Guest49> I am adding a QWebView to my editor so the cheat sheet and documentation can be accessed in the same window. Is there currently a way of doing this within the program that I am missing? Additionally is there any better way of adding this to the program instead of just downloading the rebuilding everything?

12:28 <buZz> Guest49: a subwindow?

12:28 <buZz> imho 'help' should open in a second window, not reduce screen realestate

12:29 <buZz> like most programs do afaik

12:38 <Guest49> Yes same behaviour as the editor, console and error log then mapped to a hotkey for easy access.

13:17 <teepee> Guest49: Qt calls those things Dock

13:18 <teepee> so it should be possible to add, but the current code does not allow that yet

13:20 <teepee> J1A84: some more automation would be nice, but I'm not sure if that's easily possible with a private repo, it's all so much easier with the public stuff

13:34 <teepee> uh, nice, fine grained personal access token \o/

13:34 <teepee> (beta)

17:40 <JordanBrown[m]> Do we really want to embed a web browser in OpenSCAD? (OK, technically an HTML interpreter, but that has many of the same issues.)

18:21 <J1A84> didn't the HTML was blocked for the editor since 2021  ..   not sure what attack vector this could enable and i am sure we will not update every few weeks like my other browser do Ü

18:38 <JordanBrown[m]> I wasn't so much concerned about security as I was about other issues. If it's a full HTML interpreter (including, for instance, CSS and possibly JavaScript) then it's a really big component. If it's not a full HTML interpreter, then what do you leave out, and will that omission be a problem for compatibility with the web version of the documentation? Our documentation is in Wikibooks; will Wikibooks ever use whatever pieces we

18:38 <JordanBrown[m]> omitted?

19:22 <Scopeuk> We did have a pdf export of the docs done for summer of code at one point

19:25 <teepee> yes, the offline docs exists, it's not yet enabled for the snapshot builds, but some people use it, notably the Arch builds

20:20 <peepsalot> the GUI Console was stopped from displaying HTML because it was ungodly slow, and echo wasn't ever intended to support HTML. the underlying QPlainTextEdit widget is still technically capable of displaying (a subset of) HTML though

20:22 <peepsalot> so, it's not a full Web browser, but HTML parsing -> "Rich Text" support is already there to some extent

20:23 <peepsalot> also, the AboutDialog

21:33 <linext> embed a web browser into openscad so you can run openscad wasm

21:33 <linext> then you can openscad while you openscad

21:43 <Friithian> recursive openscad

21:45 <InPhase> Finally adding the dys to functional programming language.

22:17 <teepee> you should run a linux emulator in that browser so you can run the full ui version in that :P

23:50 <gbruno> [github] sugizo opened issue #4427 (list variable assign to another variable) https://github.com/openscad/openscad/issues/4427