Hi,

What you want is typically called a binary format in programming jargon.
This binary format exists in custom versions of POV, i.e. POB. Don't ask me
for a URL I did not store any and my memory ain't that good - but I did see
it, I'm sure you can find it.
My understanding is the POV team does not want to implement such a binary
format because it involves difficult questions when you come to
cross-platform portability. As well as that they claim it would not be a
major advantage in terms of performance (parse+render time) in most cases.
Besides their to do list is probably big enough not to add this low priority
item - given the small ratio benefit/cost.

Cheers,
Al.


Spider wrote:

> Hello, just me and my wild ideas here.
> I have been working a lot with macro's and creating lot's of objects(See
> my fireworks posts)
> While doing this, I have to check lightsourses and fog settings, and
> since the fireworks are lightsources I need to wait for parse every
> time.
> Now I wondered, is there a possibility to add something of a expander to
> pov?
>
> By storing the parsed data in a new file, ex. example.pov ->example.par
> ->example.tga
>
> This could be specified with a command line argument, or a setting in
> global_settings {
>   write_parse true
>   load_parse false
> }
>
> This is only an idea, I'm not sure if it'd work, or if it is implemented
> somewhere already, but I think it might come in hadny in several cases.
>
> //Spider

--
ANTI SPAM / ANTI ARROSAGE COMMERCIAL :

To answer me, please take out the Z from my address.

Post a reply to this message