 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
To most of us, the mere mortal POV-Ray users, it is as if Pov appears
magically on the web site, created from nothing by no one. There is no
apparent discussion at all by the POV-Team members, at least as far as I
have been able to see, concerning the actual process of writing code. And
yet, there is clearly something going on there behind the curtain. Changes
have numbers assigned to them, bugs are fixed, new beta's are released, our
requests for new features are denied :) and so on.
Would someone on the development team care to elaborate on the process which
brings us this magnificent program? What methods do you use to discuss
changes, track bugs, and convert the work of dozens of coders into one
coherent program?
Best of all would be some kind of read-only "spectator" access to whatever
forum the developers use.
Pretty please?! Can we see behind the scenes?
Chris Jeppesen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Jeppesen <chr### [at] digiquill com> wrote:
: Best of all would be some kind of read-only "spectator" access to whatever
: forum the developers use.
I would let them have their privacy. Knowing that the whole world may be
watching every word you say takes away some freedom of expressing your ideas.
I work in a project in Tampere University of Technology, and I would
certainly not feel comfortable if our meetings were broadcasted over the
internet to the entire world, even when we don't discuss anything that should
be a secret. It's just that when you know that the whole world is watching,
you are a lot more careful about what you say, and you just can't feel
comfortable.
Also if the whole world would see everything they think and plan, people
would certainly discuss that in other groups and people may get wrong
expectations of ideas and the team would have no peace to develop the ideas
in peace (ie. if a wild idea is discarded, many people may complain loudly
about that even though it was just a random and not very serious idea in the
first place).
I don't think that's a very good way of communicating between developers.
It's better to let them have their privacy.
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I think he was asking for more of a "the making of POV-Ray." =)
--
- Slime
[ http://www.slimeland.com/ ]
[ http://www.slimeland.com/images/ ]
"Warp" <war### [at] tagpovrayorg> wrote in message
news:3be25509@news.povray.org...
> Chris Jeppesen <chr### [at] digiquillcom> wrote:
> : Best of all would be some kind of read-only "spectator" access to
whatever
> : forum the developers use.
>
> I would let them have their privacy. Knowing that the whole world may be
> watching every word you say takes away some freedom of expressing your
ideas.
> I work in a project in Tampere University of Technology, and I would
> certainly not feel comfortable if our meetings were broadcasted over the
> internet to the entire world, even when we don't discuss anything that
should
> be a secret. It's just that when you know that the whole world is
watching,
> you are a lot more careful about what you say, and you just can't feel
> comfortable.
> Also if the whole world would see everything they think and plan, people
> would certainly discuss that in other groups and people may get wrong
> expectations of ideas and the team would have no peace to develop the
ideas
> in peace (ie. if a wild idea is discarded, many people may complain loudly
> about that even though it was just a random and not very serious idea in
the
> first place).
> I don't think that's a very good way of communicating between
developers.
> It's better to let them have their privacy.
>
> --
> #macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
> rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
> ],13),8)-3,10>#end blob{N(array[6]{11117333955,
> 7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Slime <noo### [at] hotmailcom> wrote:
: I think he was asking for more of a "the making of POV-Ray." =)
I think that the change log with each beta version works pretty much like
this.
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Slime wrote:
>
> I think he was asking for more of a "the making of POV-Ray." =)
>
Maybe one day, when everyone here is old and the glorious days of Povray
3.5 are long gone, someone will make a nice movie...
Christoph
--
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other
things on: http://www.schunter.etc.tu-bs.de/~chris/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 1 Nov 2001 17:18:48 -0800, Chris Jeppesen wrote:
> To most of us, the mere mortal POV-Ray users, it is as if Pov appears
> magically on the web site, created from nothing by no one.
You mean that's not how it works?
> Would someone on the development team care to elaborate on the process which
> brings us this magnificent program? What methods do you use to discuss
> changes, track bugs, and convert the work of dozens of coders into one
> coherent program?
We discuss changes using English, usually. Pick a technology that allows
you to send messages to someone else over the Internet and there's a good
chance that someone on the Team has used it to communicate with someone
else on the Team at some point.
Tracking bugs and keeping the source working is, as with most projects, the
work of a change management system. It's not really that cool to look at
or to watch, but y'all get most of the entertaining stuff in the lists o'
changes that accompany beta versions (Well, it's sanitized a bit for your
protection. I tend to check things in with comments like "Ron needs a
refresher course in Boolean Logic."[1] or "Actually fixed the bug my last
change was supposed to have fixed." Y'all don't get those comments.)
In any case, there aren't really dozens of coders. There are far, far fewer
than a dozen people actually working on the core code.
> Best of all would be some kind of read-only "spectator" access to whatever
> forum the developers use.
I think Warp's comments are applicable here. It's not likely, both for the
reasons he mentioned and because, while there is an official place that
most discussions that require the participation of everyone take place, there
are always other things being talked about between one or two people in email
or whatever.
Besides, it's like sausage or the law: if you like it, you don't want to
know how it's made.
[1] Those of you with access to the raw, unedited change list will not find
this comment anywhere. It's merely an example, and in fact it's drawn from
the change list of an entirely different project that someone is actually
silly enough to pay me to work on.
--
plane{-z,-3normal{crackle scale.2#local a=5;#while(a)warp{repeat x flip x}rotate
z*60#local a=a-1;#end translate-9*x}pigment{rgb 1}}light_source{-9red 1rotate 60
*z}light_source{-9rgb y rotate-z*60}light_source{9-z*18rgb z}text{ttf"arial.ttf"
"RP".01,0translate-<.6,.4,.02>pigment{bozo}}light_source{-z*3rgb-.2}//Ron Parker
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ron Parker wrote:
>
> [...]
>
> Tracking bugs and keeping the source working is, as with most projects, the
> work of a change management system. It's not really that cool to look at
> or to watch, but y'all get most of the entertaining stuff in the lists o'
> changes that accompany beta versions (Well, it's sanitized a bit for your
> protection. I tend to check things in with comments like "Ron needs a
> refresher course in Boolean Logic."[1] or "Actually fixed the bug my last
> change was supposed to have fixed." Y'all don't get those comments.)
>
Sometimes one slips through, for example change 1199:
'Repeat after me, class... inifinite recursion BAD.'
;-)
Christoph
--
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other
things on: http://www.schunter.etc.tu-bs.de/~chris/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
please allow one comment of mine of a 143244th row and not in this project
involved programmer:
if there is someone who wants to look in my cooking pot i feel disturbed
and the love for my work is going away. then i need much money as support
to do the same superb work as if there is noone who makes a
sightseeing-tour through my kittchen.
i use v3.1 of povray and i am astonished what is possible by merging some
objects together and i get great results. there are in the meaning of
functionality no reasons why upgrades are a must. there are many other
projects which have great concepts but could not be used because the
user-interface is not usable or the results by using one program are not
calculatable. those have more reasons to publicate that their project is
still work in progress.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Christoph Hormann" <chr### [at] gmxde> wrote in message
news:3BE2C5BA.82113BC5@gmx.de...
>
>
> Slime wrote:
> >
> > I think he was asking for more of a "the making of POV-Ray." =)
> >
>
> Maybe one day, when everyone here is old and the glorious days of Povray
> 3.5 are long gone, someone will make a nice movie...
>
> Christoph
Maybe the IMP...
...Chambers
<yup, I'm still grinning :)>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
