"Marc" <jac### [at] wanadoofr> wrote:

> le message de news: 45c31221@news.povray.org...
> > Actually this is happening now - see the long threads on pov-ray includes.
> > The site will be flexible enough to accommodate moray models.
> >
> > -- Chris
>
> pov-ray includes? is that a group that I am not aware of?
> can't find anything like it in the group list :-(
>
> Marc

http://news.povray.org/povray.general/thread/%3C456b29c7$1@news.povray.org%3E/?ttop=237611&toff=50

Stephen

Post a reply to this message

web.45c334164a1d3fd8f1cb1e660@news.povray.org...
>
>
http://news.povray.org/povray.general/thread/%3C456b29c7$1@news.povray.org%3E/?ttop=237611&toff=50
>
> Stephen
>
Thank you :-)

Marc (Flushes ashamed and feels dumb)

Post a reply to this message

In article <45c1c908$1@news.povray.org>, deletethis-newsadmin2
@deletethistoo.povray.org says...
> [Followups set to povray.general]
> 
> 1 February 2007
> ---------------
> 
> The following is a joint announcement from Persistence of Vision Raytrace
r
> Pty. Ltd. ('POV'), Lutz Kretzschmar (Lutz) and Markus Lutz (Markus).
> 
> Persistence of Vision Raytracer Pty. Ltd. is pleased to advise that it ha
s
> acquired the rights to the 3d modeller 'Moray' from Lutz and Markus.
> 
Wow...!!

Does this mean it might finally include, at minimum, a setting to make 
the handedness work the same between them? lol But seriously, this is 
unbelievable news.

-- 
void main () {

    call functional_code()
  else
    call crash_windows();
}

<A HREF='http://www.daz3d.com/index.php?refid=16130551'>Get 3D Models,
 
3D Content, and 3D Software at DAZ3D!</A>

Post a reply to this message

Wow!
Moray was my first approach to 3d - and to POV-Ray.
In spite of the little time I'v used it, I can declare that it is a very
nice application.
Many thanks to Lutz and Markus for the work (and the fish, of course).
;-)
Paolo

> "Chris Cason" wrote:
> [Followups set to povray.general]
>
> 1 February 2007
> ---------------
>
> The following is a joint announcement from Persistence of Vision Raytracer
> Pty. Ltd. ('POV'), Lutz Kretzschmar (Lutz) and Markus Lutz (Markus).
>
> Persistence of Vision Raytracer Pty. Ltd. is pleased to advise that it has
> acquired the rights to the 3d modeller 'Moray' from Lutz and Markus. Moray
is
> a Windows program specifically designed to create 3d models and scenes to
be
> used with the POV-Ray raytracer, and was originally sold as trialware.
[...]

Post a reply to this message

Chris Cason wrote:
> The current version 3.7 development codebase will be made publicly available
> at around the same time as the Moray codebase. This will allow the public to
> assist, if they wish, in completing version 3.7 of POV-Ray and will also
> assist in the transition to 4.0.

Did noone else notice this?  So we'll get access to the 3.7 codebase 
before it's finished?

Cool :)

...Chambers

Post a reply to this message

On Sun, 11 Feb 2007 23:01:39 -0800, Ben Chambers <ben### [at] pacificwebguycom> wrote:

>Chris Cason wrote:
>> The current version 3.7 development codebase will be made publicly available
>> at around the same time as the Moray codebase. This will allow the public to
>> assist, if they wish, in completing version 3.7 of POV-Ray and will also
>> assist in the transition to 4.0.
>
>Did noone else notice this?  So we'll get access to the 3.7 codebase 
>before it's finished?

Hmm, yeah, I read right over that point.  I'll be interested to look at the code,
however, I won't
likely have much to add.  I have studied the 3.6 code quite a bit and, from what I've
read,  it
seems that the 3.7 code is an extensive rewrite towards better management and
extensibility.  Should
be interesting...



Kyle

Post a reply to this message

Kyle <hob### [at] gatenet> wrote:
> I have studied the 3.6 code quite a bit and, from what I've read,  it
> seems that the 3.7 code is an extensive rewrite towards better management
> and extensibility.

  That's indeed true. While 3.7 is not a complete rewrite from scratch,
it's still a vast improvement on the 3.6 code. The latter uses tons and
tons of ugly hacks such as global variables and other solutions which are
thread-unsafe, most of which are needlessly so.

  Making code thread-safe automatically makes code better because
thread-safeness forces a higher degree of modularity. :)

-- 
                                                          - Warp

Post a reply to this message

Warp wrote:
> Kyle <hob### [at] gatenet> wrote:
> 
>>I have studied the 3.6 code quite a bit and, from what I've read,  it
>>seems that the 3.7 code is an extensive rewrite towards better management
>>and extensibility.
> 
> 
>   That's indeed true. While 3.7 is not a complete rewrite from scratch,
> it's still a vast improvement on the 3.6 code. The latter uses tons and
> tons of ugly hacks such as global variables and other solutions which are
> thread-unsafe, most of which are needlessly so.
> 
>   Making code thread-safe automatically makes code better because
> thread-safeness forces a higher degree of modularity. :)

How far along is the conversion to C++ code?  I've been converting my 
modeler from C to C++, and I keep wincing at the evil code that I first 
wrote.

I wonder how many times the POV-Ray coders look at something and say 
"Good lord, did *I* write that?"

Regards,
John

Post a reply to this message

John VanSickle wrote:
> How far along is the conversion to C++ code?  I've been converting my
> modeler from C to C++, and I keep wincing at the evil code that I first
> wrote.

POV-Ray code has been C++ since 3.5 and required a C++ compiler since 3.6.

> I wonder how many times the POV-Ray coders look at something and say
> "Good lord, did *I* write that?"

Not the "I", but "anybody". Especially the lighting code was rather
revealing when it came to the "many cooks" problem. In same cases analysis
showed that perfectly logical looking code into which a lot of time went
maintaining it was either unreachable or conditions were always true. While
in many cases a compiler could probably have figured them out, they just
added to the complexity of the code. In other cases there were really
inefficient linear searches that were not needed at all.

Also, in particular the media code is known to not handle its interval
sorting efficiently, but lack of time did prevent us from rolling out the
replacement code because it had various funny bugs (that was why early media
in 3.7 did not work right). So what was done was simply adding the old
inefficient but flawlessly working code back. In fact, many such instances
in many places are the reason for the various strange bugs that did appear
in early betas. And they do take long to fix because usually the code does
work on the test scenes originally used to check the changes.

	Thorsten

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:
> POV-Ray code has been C++ since 3.5 and required a C++ compiler since 3.6.

  You know, "requires a C++ compiler" and "is C++" (and not C) are two
different things. ;)

  Those gigantic switch-case blocks are the most typical C-style code
in POV-Ray. (Sure, technically speaking switch-cases are C++ too, but
in this case those gigantic switch-cases are actually C code emulating
dynamic binding, something which could be done more directly and much
more easily using C++-specific code.)

-- 
                                                          - Warp

Post a reply to this message