![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Nikodemus Siivola
Subject: Re: Standard include files - not a proposal, yet
Date: 16 Sep 2001 12:51:53
Message: <3ba4d8a9@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Warp" <war### [at] tag povray org> wrote:
> POV-Ray 3.5 contains lots of standard include files which are well
> documented, which is a great improvement compared to previous versions.
True ;) But could the standard include files should be distributed
separately? This way the standard library could (maybe) be evolve more
rapidly, instead of being updated per release...
-- Nikodemus
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
You might want to talk to Ken about inclusion of a set of links that are
specific to include files. Also, why don't you start compiling and
organizing a set of include files and keep them on your web site for
everyone to access?
Jim
"Nikodemus Siivola" <tsi### [at] cc hut fi> wrote in message
news:3ba4d8a9@news.povray.org...
>
> "Warp" <war### [at] tag povray org> wrote:
>
> > POV-Ray 3.5 contains lots of standard include files which are well
> > documented, which is a great improvement compared to previous versions.
>
> True ;) But could the standard include files should be distributed
> separately? This way the standard library could (maybe) be evolve more
> rapidly, instead of being updated per release...
>
> -- Nikodemus
>
>
>
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Nikodemus Siivola
Subject: Re: Standard include files - not a proposal, yet
Date: 16 Sep 2001 13:28:04
Message: <3ba4e124@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Jim Kress" <kre### [at] kressworks com> wrote:
> You might want to talk to Ken about inclusion of a set of links that are
> specific to include files. Also, why don't you start compiling and
> organizing a set of include files and keep them on your web site for
> everyone to access?
I could, but the point is that
a) I am an individual person, and my website might vanish like so many
others...
b) It would be nice to have a set of include-files with the team's stamp
of approval on them, published under a single licence or at most two.
One benefit I have not yet mentioned: Names. A standard include library
would prevent name collisions, or at least help avoid them.
- Nikodemus
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Thorsten Froehlich
Subject: Re: Standard include files - not a proposal, yet
Date: 16 Sep 2001 14:14:13
Message: <3ba4ebf5@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <3ba4bff8@news.povray.org> , "Nikodemus Siivola"
<tsi### [at] cc hut fi> wrote:
> A set of standard include files, published under POV-licence (or GPL, or
> other), hosted on the povray.org -- with version control, etc.
A really good idea the POV-Team has been playing with for years.
Unfortunately, even creating simple database driven websites takes a real
lot of time and testing. Just the newsgroup interface took well over 200
hours of work, and it has no "critical" user interaction yet (which is one
of the _many_ (other) reasons why there isn't something as "complex" as
posting available).
Thorsten
____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povray org
I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Warp
Subject: Re: Standard include files - not a proposal, yet
Date: 17 Sep 2001 05:14:40
Message: <3ba5bf00@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Nikodemus Siivola <tsi### [at] cc hut fi> wrote:
: True ;) But could the standard include files should be distributed
: separately? This way the standard library could (maybe) be evolve more
: rapidly, instead of being updated per release...
Because it would be more complicated for the users.
They would have to know there are a set of standard include files somewhere
else, they have to find them, they have to download them and they have to
know how to install them. Also the documentation would have to be separate
from the povray main documentation, which causes even more problems (it's not
a good idea to include in the main povray documentation something which doesn't
come with povray).
And besides, a continuously updated set of include files can be a good
thing, but it can also be a bad thing: If some include files are changed,
then lots of existing pov files can become incompatible with them. That is
there will be a lot of versioning problems. There may be pov-files which
work with the library version 3.5a5, but not with versions 3.5a4 nor 3.5a6.
This can be a headache.
--
#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/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Rick [Kitty5]
Subject: Re: Standard include files - not a proposal, yet
Date: 17 Sep 2001 05:58:41
Message: <3ba5c951@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> It may be that something like this was already planned, or though about
and
> shot down, but here goes...
a similar idea is on the cards for povray.co.uk, however its another idea
that would require significant development time, and I have none free atm :(
--
Rick
Kitty5 WebDesign - http://Kitty5.com
POV-Ray News & Resources - http://Povray.co.uk
TEL : +44 (01270) 501101 - FAX : +44 (01270) 251105 - ICQ : 15776037
PGP Public Key
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x231E1CEA
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Nikodemus Siivola
Subject: Re: Standard include files - not a proposal, yet
Date: 17 Sep 2001 18:36:57
Message: <3ba67b09$1@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Warp" <war### [at] tag povray org> wrote:
> : True ;) But could the standard include files should be distributed
> : separately? This way the standard library could (maybe) be evolve more
> : rapidly, instead of being updated per release...
>
> Because it would be more complicated for the users.
> They would have to know there are a set of standard include files
> somewhere else, they have to find them, they have to download them and
Ok. I buy this. So what we want is a CPAN-like pov-archive, prefrably one
with official status, hosted on povray.org, under a single licence?
- Nikodemus
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
is that legal? i mean, can somebody distribute somebody
else's include files? i'm no lawyer, but i know that just cuz
something is free doesn't imply that anybody can distribute
it... i believe thats even the case with povray.
but i do agree that it would be GREAT to have a hundred
or two of the best includes in a central repository.
miker
"Jim Kress" <kre### [at] kressworks com> wrote in message
news:3ba4daf4$1@news.povray.org...
> You might want to talk to Ken about inclusion of a set of links that are
> specific to include files. Also, why don't you start compiling and
> organizing a set of include files and keep them on your web site for
> everyone to access?
>
> Jim
>
> "Nikodemus Siivola" <tsi### [at] cc hut fi> wrote in message
> news:3ba4d8a9@news.povray.org...
> >
> > "Warp" <war### [at] tag povray org> wrote:
> >
> > > POV-Ray 3.5 contains lots of standard include files which are well
> > > documented, which is a great improvement compared to previous
versions.
> >
> > True ;) But could the standard include files should be distributed
> > separately? This way the standard library could (maybe) be evolve more
> > rapidly, instead of being updated per release...
> >
> > -- Nikodemus
> >
> >
> >
>
>
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Warp wrote:
>
> And besides, a continuously updated set of include files can be a
> good thing, but it can also be a bad thing: If some include files are
> changed, then lots of existing pov files can become incompatible with
> them. That is there will be a lot of versioning problems. There may be
> pov-files which work with the library version 3.5a5, but not with
> versions 3.5a4 nor 3.5a6. This can be a headache.
Good public-macro writing habits can prevent this. I have re-written
my macros from time to time, primarily when a macro does not work as
advertised. New ideas are implemented in new macros, instead of being
tacked onto old ones.
Regards,
John
--
ICQ: 46085459
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Nikodemus Siivola
Subject: Re: Standard include files - not a proposal, yet
Date: 25 Sep 2001 04:55:07
Message: <3bb0466b@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"John VanSickle" <evi### [at] hotmail com> wrote:
> > And besides, a continuously updated set of include files can be a
> > good thing, but it can also be a bad thing: If some include files are
> > changed, then lots of existing pov files can become incompatible with
> Good public-macro writing habits can prevent this. I have re-written
Indeed. And I would think that a moderated collection would not be prone
to functionality changing modifications: if it's not broken -- don't fix
it.
-- Nikodemus
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |