"Tony[B]" <ben### [at] panamac-comnet> wrote...
>
> OK. Let me see if I get this: you mean that you people add the same
feature,
> but you make your own code? You redo the thing from scratch, essentially?
Or
> did I misunderstand completely? I mean, I understand that you don't just
go
> POV 3.1 + MegaPOV = POV 3.5. You just add the important stuff after making
> it 200% bug free, right?

Here's how POV 3.5 was made so far:

Start with POV 3.1 (a?)
Merge in the SuperPatch
Add in POV 3.1g modifications and bug fixes
Change some code from C to C++
Make major changes to input and output
Add a totally new system for Core<=>GUI communication
(notice no MegaPov yet)
Merge MegaPov 0.5a features
Remove some MegaPov features that are unstable and/or buggy
Start modifying MegaPov features to make them better
Add in a few more features
All the while continue to fix a _ton_ of tricky bugs that have been coming
in as bug reports.

That's where we're at now.  There are still many bugs that need to be fixed
and new features that need to be updated/improved and documented.

-Nathan

Post a reply to this message

go chris go! 

Nathan Kopp wrote:
> 
> "Chris Huff" <chr### [at] maccom> wrote...
> > Which details are you thinking of? Do you mean getting a stable syntax,
> > getting "size" to work correctly, making glows work more like
> > objects...etc.
> 
> Yes, those would be the details that I'm thinking of.  :-)
> 
> -Nathan

Post a reply to this message

Nathan Kopp wrote:
> 
> 
> Here's how POV 3.5 was made so far:
> 
> Start with POV 3.1 (a?)
> Merge in the SuperPatch
> Add in POV 3.1g modifications and bug fixes
> Change some code from C to C++
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
What this means? Does it mean, that C++ compiler is now required for
core POV-Ray? Or system-dependent part of it requires it? Care to
elaborate?
Inquiring minds want to know ;-)

Post a reply to this message

Nathan Kopp <Nat### [at] koppcom> wrote:
:> Which details are you thinking of? Do you mean getting a stable syntax, 
:> getting "size" to work correctly, making glows work more like 
:> objects...etc.

: Yes, those would be the details that I'm thinking of.  :-)

  Since when has megapov cared about stable syntax?-)

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):_;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

> Start with POV 3.1 (a?)
> Merge in the SuperPatch
> Add in POV 3.1g modifications and bug fixes
> Change some code from C to C++
> Make major changes to input and output
> Add a totally new system for Core<=>GUI communication
> (notice no MegaPov yet)
> Merge MegaPov 0.5a features
> Remove some MegaPov features that are unstable and/or buggy
> Start modifying MegaPov features to make them better
> Add in a few more features
> All the while continue to fix a _ton_ of tricky bugs that have been coming
> in as bug reports.

OK. So what you really did was this:
POV 3.1a + SuperPatch + POV 3.1g + rewiring + MegaPOV 0.5a - garbage +
improvements + bugfixes

Did I get it right now? :)

Post a reply to this message

"Tony[B]" <ben### [at] panamac-comnet> wrote in message
news:39bf7958@news.povray.org...
> > Start with POV 3.1 (a?)
> > Merge in the SuperPatch
> > Add in POV 3.1g modifications and bug fixes
> > Change some code from C to C++
> > Make major changes to input and output
> > Add a totally new system for Core<=>GUI communication
> > (notice no MegaPov yet)
> > Merge MegaPov 0.5a features
> > Remove some MegaPov features that are unstable and/or buggy
> > Start modifying MegaPov features to make them better
> > Add in a few more features
> > All the while continue to fix a _ton_ of tricky bugs that have been
coming
> > in as bug reports.
>
> OK. So what you really did was this:
> POV 3.1a + SuperPatch + POV 3.1g + rewiring + MegaPOV 0.5a - garbage +
> improvements + bugfixes
>
> Did I get it right now? :)
>

Now I'm confused. I thought mp had the superpatch stuff in it, and why pov
3.1a?

Why not POV 3.1g + MP 0.5a - garbage + improvements + bugfixes.

(just out of curiosity)

Post a reply to this message

BTW I should have stressed that I'm not suggesting you are doing it wrong,
I'm suggesting I'm an ignorant fool when it comes to C and in need of
enlightenment. ;)

Post a reply to this message

On Wed, 13 Sep 2000 15:33:06 +0100, Tom Melly wrote:
>Now I'm confused. I thought mp had the superpatch stuff in it, and why pov
>3.1a?
>
>Why not POV 3.1g + MP 0.5a - garbage + improvements + bugfixes.

It's historical.  I think Nathan is a bit confused on the early history,
which happened before either of us were on the team, but I sent the code
for the Superpatch to Chris Young when 3.5 was but a glimmer, and before
MegaPOV even existed (but after 3.1g existed.)  The actual order of things
was  POV 3.1g + Superpatch (based on 3.1d) + ...

The "easy" way you mention would have required the team to have started 
work on 3.5 much later than they actually did.

-- 
Ron Parker   http://www2.fwi.com/~parkerr/traces.html
My opinions.  Mine.  Not anyone else's.

Post a reply to this message

In article <slr### [at] fwicom> , ron### [at] povrayorg (Ron
Parker) wrote:

> It's historical.  I think Nathan is a bit confused on the early history,
> which happened before either of us were on the team, but I sent the code
> for the Superpatch to Chris Young when 3.5 was but a glimmer, and before
> MegaPOV even existed (but after 3.1g existed.)  The actual order of things
> was  POV 3.1g + Superpatch (based on 3.1d) + ...

Actually, it is even more complicated:  POV-Ray 3.5 was based on 3.1d (the
version current at the time development started) and then the bug fixes of
3.1e, 3.1f and 3.1g were merged in as they were made available (Ron, check
out change35.doc in the 3.5 source for the early history).


     Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

In article <39bf7958@news.povray.org> , "Tony[B]" 
<ben### [at] panamac-comnet> wrote:

> OK. So what you really did was this:
> POV 3.1a + SuperPatch + POV 3.1g + rewiring + MegaPOV 0.5a - garbage +
> improvements + bugfixes
>
> Did I get it right now? :)

No, not completely, but you are getting closer!   It is more like:

POV-Ray 3.1d + bugfixes + new stuff + parts of SuperPatch + bugfixes + more
new stuff + 3.1e + more parts of SuperPatch + bugfixes + 3.1f and 3.1g +
more new stuff + bugfixes + MegaPOV 0.5a - unstable features + more new
stuff + bugfixes = POV-Ray 3.5

Get it? ;-)


Or, to add to Nathan's list (I don't claim it is complete):

> Start with POV 3.1d
> Add a totally new system for Core<=>GUI communication
> Merge in some SuperPatch parts
> Make major changes to input and output
> Add in POV 3.1g modifications and bug fixes
> Merge in more SuperPatch parts
> Add other features, i.e. JPEG input
> Change some code from C to C++
> (notice no MegaPov yet)
> Merge MegaPov 0.5a features
> Remove some MegaPov features that are unstable and/or buggy
> Start modifying MegaPov features to make them better
> Add in a few more features
> All the while continue to fix a _ton_ of tricky bugs that have been coming
> in as bug reports.

There is also the situation where there are two independent features of the
same kind that were developed for 3.5 and someone made a patch doing
something similar.


      Thorsten


____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message