Saw a video, read an article or two, decided we needed one. ;) - BE
hi, kurtz le pirate <kur### [at] freefr> wrote: > On 09/07/2025 09:25, jr wrote: > > ... > > way more ambitious though, line numbers ! :-). ... > ... > more ambitious : yes, lines numbers, list of vars and where vars are > used. but it's a wip... agree, a list of the variables and so on is very useful to have, in particular when "playing" with unfamiliar (someone else's :-)) code. I don't know MacOS, do you have/use the 'less' and 'vim' programs ? both can use "tags" files created by 'ctags'. that program, patched[*], can give you variables, and usage; for instance below the first few lines output based on one of your scenes (Oct 31st 2023): $ ectags --sdl-kinds=v -ux pursuitcurve.pov displayAxis variable 33 pursuitcurve.pov #declare displayAxis = false; displayPlane variable 34 pursuitcurve.pov #declare displayPlane = false; AxisLen variable 37 pursuitcurve.pov #declare AxisLen = 16; Scale variable 39 pursuitcurve.pov #declare Scale = AxisLen/image_width; C variable 115 pursuitcurve.pov #local C = _Brightness*_Saturation; X variable 116 pursuitcurve.pov #local X = C - (1 - abs(mod(_Hue/60,2) - 1)); m variable 117 pursuitcurve.pov #local m = _Brightness-C; .... only requesting variables, the '-ux' selects an unsorted cross-reference format to console/terminal; when invoked without options, it'll write a "tags" file. [*] <drive.google.com/file/d/10ikrIHkMopedFPlq6V4YhnnNn3sY59hC/view?usp=sharing> regards, jr.
On 09/07/2025 09:25, jr wrote: > hi, > > kurtz le pirate <kur### [at] freefr> wrote: >> ... >> A long time ago, I started doing the same thing (but in Perl). ... > > way more ambitious though, line numbers ! :-). I don't "speak" perl, and ran > into trouble when i tried the script (for which thanks) on a Debian VM; attached > a screenshot. > > > regards, jr. A yes, the script uses the "File::Basename" module, which is not present in your system. I use cpan to install/manage modules. More infos here : <https://wiki.debian.org/PerlFAQ> :. cpan install File::Basename more ambitious : yes, lines numbers, list of vars and where vars are used. but it's a wip... -- kurtz le pirate compagnie de la banquise
"jr" <cre### [at] gmailcom> wrote: > kurtz le pirate <kur### [at] free
fr> wrote: > > ... > > A long time ago, I started doing the same thing (but in Perl). ... > > way more ambitious though, line numbers ! :-). I don't "speak" perl, and ran > into trouble when i tried the script (for which thanks) on a Debian VM; attached > a screenshot. ignore. the trouble was the 1st line, all good w/out that comment line. regards, jr.
hi, Josh English <Jos### [at] joshuarenglishcom> wrote: > On 7/7/2025 8:40 AM, jr wrote: > > ... 'vim' makes jumping ... a single (shifted) key press. > > I have tried to use vim, but I have fallen into the convenience of the > Run button in the Windows UI. I have a Linux Mint machine but haven't > found a nice workflow with POV-Ray and Vim. looked but cannot, of course, now find the reference. :-) LeForgeron (I think) posted an image / chart depicting his setup. I use the below in my '~/.vimrc', which is based on / derived from that "tip". my "workflow" when writing scene code is to occasionally do a ":make" to confirm there are no typos etc, ie am at that point only interested in the parsing; for that I have a dedicated "one-liner" shell script, "povparse", also below. workflows are v individual, but LeForgeron's "method" works for me. regards, jr. -----<snip>----- " au Filetype pov setlocal makeprg=povparse\ +i% au Filetype povini setlocal makeprg=povparse\ % au BufRead,BufNewFile, *.ini set filetype=povini -----<snip>----- #!/bin/sh /usr/bin/nice -n 19 /usr/local/bin/povray-3.8.0-beta.2 +w32 +h32 -d -f -p -gr -gs $*
hi, kurtz le pirate <kur### [at] freefr> wrote: > ... > A long time ago, I started doing the same thing (but in Perl). ... way more ambitious though, line numbers ! :-). I don't "speak" perl, and ran into trouble when i tried the script (for which thanks) on a Debian VM; attached a screenshot. regards, jr.
On 7/8/2025 10:25 AM, Bald Eagle wrote: > > https://github.com/mxgmn/WaveFunctionCollapse > > https://robertheaton.com/2018/12/17/wavefunction-collapse-algorithm/ > > https://github.com/CodingTrain/Wave-Function-Collapse > > Plus lots more links. Thank you. I spent some time refactoring the code to get the macros in sections in the main include file so I could sort of trace what is going on in the whole process. > > This is definitely something to develop for general use! I'm probably committing the sin of overgeneralizing the code right now because I want to also try this with hexagons and eventually cubes. > > Glad you're still at it Josh - from the days of the POVcyclopedia to now. :) > > - BW > I'm surprised anyone remembers that project. I found the original html and it still had the webring links in. All that's left is on my homepage: https://joshuarenglish.com/povray/ Uncle Josh