![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: [GDS|Entropy]
Subject: Re: ANN: 3.7 .inc file improvement project
Date: 27 Mar 2009 20:45:27
Message: <49cd7327@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Kenneth" <kdw### [at] earthlink net> wrote in message
news:web.49cd4bf8b8d33e5f50167bc0@news.povray.org...
> "[GDS|Entropy]" <gds-entropy AT hotmail DOT com> wrote:
>
>> I would also like to have the community donate their best textures to
>> this
>> effort. It will be important for these textures to use features that v3.7
>> will have, no megapov specific textures, please. Compatibility with
>> radiosity also a plus.
>>
>> Depending on the volume of response, I may make a portal available on my
>> site for this purpose. That would be later if needed at all.
>>
>> I will take care of contact sheets.
>>
>> So for now, bring your best textures!
>>
>> ian
>
> Regarding our texture ideas: Should we post them here? If so, I'm thinking
> that
> it might be better to switch this thread over to p.b.i--before it gets too
> involved--so that we can post images of what our textures look like. Just
> a
> thought.
>
> KW
That could be a good idea. If we used the txview342 program we can generate
contact sheets for all textures, then select the ones we wish to submit for
inclusion, and generate contact sheets for those.
You can always e-mail me the files as well, and let me do the dirty work.
BTW your modified shapes.inc and macros would be good to post. Anything that
improves povray should be included.
I'm trying to convert some c++ gaussian/other rand code to povray as well.
That is rather difficult thought do to the fact we don't have datatypes and
proper for/do loops. :-(
ian
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) |
"Jim Holsenback" <jho### [at] hotmail com> wrote in message
news:49cd1fd8@news.povray.org...
> "clipka" <nomail@nomail> wrote in message
> news:web.49cd002843368518208afb30@news.povray.org...
>> "Thomas de Groot" <tDOTdegroot@interDOTnlANOTHERDOTnet> wrote:
>> > Forgive me if I am wrong, but just a question: There has been an major
>> > updating effort of the .inc files done by Jim Holsenback c.s. somewhen
> last
>> > year. Is your project not duplicating their effort to some extent?
>>
>> What has happened to that effort then?
>
> maybe I wasn't clear (wouldn't be the first time) ....
>
> there was work done on sample scene files. I didn't mess with the includes
> with the exception of the glass includes
>
> Cheers
>
Hey, throw those into the mix as well. Anything that helps, helps. :-)
ian
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) |
Given that the .inc and sample scene files are covered under the
povlegal.doc, I doubt that source forge will approve my project for hosting
there, but I tried anyway and sent them a copy of the doc.
If they do not approve it, I will probably setup some kind of hosting on my
website.
I will probably give out usernames and passwords to people who wish to
contribute, and have their submissions go into an XML file within a CDATA
block. I will probably not support image upload, but I might. Hopefully
sourceforge will be cool and approve the project because I really don't feel
like setting up all that crap unless I really have to. ;-D
ian
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) |
"[GDS|Entropy]" <gds-entropy AT hotmail DOT com> wrote:
> I'm trying to convert some c++ gaussian/other rand code to povray as well.
> That is rather difficult thought do to the fact we don't have datatypes and
> proper for/do loops. :-(
Are the rand.inc macros *that* bad?
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) |
"Jim Holsenback" <jho### [at] hotmail com> schreef in bericht
news:49cca446$1@news.povray.org...
>
> yes that's correct, however I did make some changes to glass includes ...
I think that is where I erred in my (faulty) memory... My excuses for the
confusion.
Thomas
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) |
"clipka" <nomail@nomail> wrote in message
news:web.49cd8e2eb8d33e5208afb30@news.povray.org...
> "[GDS|Entropy]" <gds-entropy AT hotmail DOT com> wrote:
>> I'm trying to convert some c++ gaussian/other rand code to povray as
>> well.
>> That is rather difficult thought do to the fact we don't have datatypes
>> and
>> proper for/do loops. :-(
>
> Are the rand.inc macros *that* bad?
>
Hmm....so it appears that it already HAS gaussian rand...lol....less I have
to do now. ;-)
ian
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) |
Yup...sourceforge didn't like the POV terms...oh well...screw them then. ;-p
I guess for now just either post to PBI or e-mail me whatever you guys come
up with for textures..
ian
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) |
"[GDS|Entropy]" <gds-entropy AT hotmail DOT com> wrote:
> Hmm....so it appears that it already HAS gaussian rand...lol....less I have
> to do now. ;-)
One thing that *might* come in handy would be a set of complementary functions
to compute the distribution density.
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) |
> Yup...sourceforge didn't like the POV terms...oh well...screw them then.
> ;-p
Since you are touching up the include files it probably would be best just
to
mark them as LGPL to be licence compatible in the future?
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) |
"Tim Attwood" <tim### [at] anti-spam comcast net> wrote in message
news:49ceaa02$1@news.povray.org...
>> Yup...sourceforge didn't like the POV terms...oh well...screw them then.
>> ;-p
>
> Since you are touching up the include files it probably would be best just
> to
> mark them as LGPL to be licence compatible in the future?
>
THe only problem with that is that those files are covered under the
povlegal.doc and so I can't just go switching licenses on the POV
team....I'd have to get their permission to do something like that. I was
actually suprised to read in the doc that we can't even use sample scenes to
create derivative works! So I guess technically I need to get permission
from the pov team to even do what I'm currently doing. :-|
ian
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |