Gilles Tran wrote:
> 
> Actually it's not that obvious... Before Ron Parker and Nathan Kopp invested
> a lot of their time to create what was first known as the Superpatch and
> then Megapov, patching was a very scattered effort. For instance, few people
> knew about the isosurface patch before Megapov became widely known, even
> though it had been around since 1996 (and the iso patch already had macros
> and other goodies). While creating 3.5 patches will certainly be a very
> lively activity, merging patches into a usable product is a totally
> different story. Someone will have to appoint him/herself Megapov manager
> and do what Ron and Nathan did before (which includes tasks not-so-loved by
> programmers, like user support and writing documentation), before they
> became Team members.

I completely agree.  For the patches contained in megapov i think it would
be good to have some discussion which patches would be good to be adapted
to POV-Ray 3.5 as they are (like glows, fast macros etc.) and which should
probably be reconsidered because of new functionality in 3.5 (like
displace warp -> function warp etc.) Adapting the patches would be good to
be coordinated somehow, otherwise different people will start to adapt
different patches according to their personal needs.

There is one very good thing about megapov that it formed certain
standards like separating the patches with #ifdef's and the common
documentation.  For the problem of documentation i suggested agreeing on a
common standard without the necessity for the patches to be combined in
one 'megapov' version, see:

news://news.povray.org/3CBAF2B1.F2AD79E2%40gmx.de

Some other standards are now forced by the new licence (like the '#version
unofficial' checking).

Christoph

-- 
POV-Ray tutorials, IsoWood include,                 
TransSkin and more: http://www.tu-bs.de/~y0013390/  
Last updated 30 Jun. 2002 _____./\/^>_*_<^\/\.______

Post a reply to this message