|
 |
hi,
"ingo" <nomail@nomail> wrote:
> "jr" <cre### [at] gmail com> wrote:
> > Tcl "starkit"s,
>
> https://sqlite.org/appfileformat.html
> https://sqlite.org/affcase1.html
>
> What if one did something like the above. The database would contain the
> complete current and past project in one file. Beside that one would have the
> complete set of current versions as text files in the working dir(s). One could
> feed POV-Ray the current text file(s) or the database and it would extract the
> current version and render it.
you're preaching to the converted </grin>. personally, I (and I guess you)
would like to see SQLite at the core of the "next-gen" POV-Ray.
> Several of the editors out there are very configurable (language servers et al) ...
but you're thinking way more "integrated" than self does.
> With a lot of test images and reuse of scenes I loose track of command line
> settings, camera settinges etc.
had me thinking that, at least for the *NIX builds, one could have POV-Ray dump
its argv[] to a '~/.povray_history', to help with that. (WFP ? :-))
regards, jr.
Post a reply to this message
|
 |