|
![](/i/fill.gif) |
I've had a look through this thread and there are a lot of ideas there.
There certainly seem to be some consistent themes emerging but before trying
to summarize them I'd like to clarify one point.
One large part of the thread discusses the potential to implement name
spaces in the POV-Ray parser and there are a couple of other ideas to
address naming conflicts and other issues that would require parser changes.
This seems great to me for the future, but it seems that if parser changes
are introduced then people are likely to take a while to get used to them
and start to develop techniques around them. Some time after that we would
be well positioned to discuss how to use them to implement standards.
I don't dispute that it would be good to anticipate such potential future
parser changes and build our current standards in a way that might be
compatible with them, but it seems to me that to get this collection off the
ground in the near future we'd be well advised to implement standards that
we're able to adhere to with existing versions of POV-Ray.
Would everyone be ok to limit the 'standards' discussion to existing, well
established features for now. This would also enable a greater number of
people to use the collection from the outset, without forcing everyone to
upgrade the moment the new version is released.
Regards,
Chris B.
Post a reply to this message
|
![](/i/fill.gif) |