Replacing:

+-l library_path=

initially with:

+-ypdoc_  yuqkpath_doctxt
+-ypfon_  yuqkpath_fonts
+-ypinc_  yuqkpath_includes
+-ypopt_  yuqkpath_options
+-ypsce_  yuqkpath_scenes

These will likely be mapped back to the old, single library_path code 
internally at first. Only the parsing code is in place currently.

The primary reason for the different names is, while yuqk has been 
bending away from official POV-Ray code for a long time, this next 
release is breaking. New "library_path" support is required so not to be 
tangled at all with other POV-Ray (or older yuqk) builds/installs.

The options above more or less align with either the linux debian based 
official 'POV-Ray' package and install partitioning which already exists 
and/or directories which already exist in old-style / personal build 
installs.

---

A secondary reason to move toward additional library paths has to do 
with enabling later support for certain compiled / pre-digested things 
which the we can just reference in the parser:

yuqkpath_cameras   +-yplit_
yuqkpath_colors    +-ypcol_
yuqkpath_finishes  +-ypfin_
yuqkpath_pigments  +-yppig_
yuqkpath_textures  +-yptex_
yuqkpath_interiors +-ypint_
yuqkpath_materials +-ypmat_
yuqkpath_lights    +-yplit_
yuqkpath_images    +-ypimg_
yuqkpath_macros    +-ypmcr_
yuqkpath_ies       +-ypies_
yuqkpath_ldt       +-ypldt_
yuqkpath_meshes    +-ypmsh_

This last me just dreaming at this point, but other tools do support 
pre-read/compiled stuff in this sort of way and it's certainly been 
requested over time for images and large meshes, especially.

I think too it's easier to do some things like transformable user 
function cameras as compiled camera ray collections.

Bill P.

Post a reply to this message