hi,

"GioSeregni" <gms### [at] hotmailcom> wrote:
> ...
> The recognizability at first sight of each mesh object.
> It will take a little time because I want to align on a new feature all my
> plugins and also the executable that I use for the conversions (CAD - STL
> -PovRay) of my models.
> Let me explain better.
> The various formats "understand" which mesh they are translating because the
> finishes are defined in a common and recognizable format that begins with the
> CAD drawing that assigns the layer name.
> In the layer name there is the color information.
> The name is in hexadecimal, because it is easy to read.

:-)


> Example HEXFF0000T7F means rgb red, with alpha (Transparency) equal to 50%, 127
> of 255
> This system creates a database with its pointers to finishes that helps organize
> the meshes and the smooth.
> UDT  for my system details for a model:
> ...
>  LayerCo As Double    ' 8 bytes
>  EntitCo As Double    ' 8 bytes

"Co" as in colour, I assume ?


>  Transp  As Double    ' 8 bytes
> ...
> END OF FILE
>
>  TargetX AS DOUBLE
>  TargetY AS DOUBLE
>  TargetZ AS DOUBLE
>  WPntX   AS DOUBLE 'view = 48 bytes
>  WPntY   AS DOUBLE
>  WPntZ   AS DOUBLE
>  Orto    AS DOUBLE   '8 bytes
>

what are those for ?


> But it's a database that uses long integers (or long ) and I can't add strings
> for various reasons.

exporting to some "common" ASCII format, eg CSV, and importing such formats, is
ime (much) easier than "faffing about" with binary file formats.

is there a reason you don't use (integer) keys to tie together the bits of data
?


> So I thought of a dictionary that uses the color as an index, to remember what
> kind of object it is. A parallel, textual file of specifications.
> Example "shoes"
> In the database HEX000000
> [T00] optional, not needed here.
> But in the dictionary "clean and shiny shoes".
> THIS COMMENT will be in a comment label in the PovRay mesh.
> It will be useful to easily customize the files.
> Not only that, this reminder label, adjustable in "human" language could be used
> by those who want ALSO as a prompt for the AI... which could automatically
> suggest the best finish for the mesh.
> It may all seem very strange, but in this way each model, with a simple label at
> the end of each mesh, becomes very flexible and improvable.

I'd have many more questions now, but will pass, for now.  agree that making
stuff human-readable is a good (the best ? :-)) way to go.


regards, jr.

Post a reply to this message