 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I was hunting around povray.org/links and found a small refrence to
Pov-Ray 3.5 (actually a feature expected to be in 3.5). I was wondering
if there was any place that could give me information on the upcomming
edition, like a feature list (what's new type of thing) etc.?
Thx,
Tim Soderstrom
TigerHawk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
TigerHawk wrote:
>
> I was hunting around povray.org/links and found a small refrence to
> Pov-Ray 3.5 (actually a feature expected to be in 3.5). I was wondering
> if there was any place that could give me information on the upcomming
> edition, like a feature list (what's new type of thing) etc.?
Officially:
There is no public information yet available as to what features
will be included in POV-Ray v3.5. This is in keeping with the
POV-Team's current policy of feature non-disclosure prior to a
new release.
Unofficially:
You can expect that many of the features that are included in
the patched version of POV-Ray called "MegaPov" will indeed be
included in the next official release of the program. Not all
will make the cut nor can you be assured that the syntax used
in the patch will make it into the official version but most
things will be close enough that you can get a general idea
of what to expect.
MegaPov - http://nathan.kopp.com/patched.htm
--
Ken Tyler - POV-Ray Technical Assistance Group Member
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I was hunting around povray.org/links and found a small refrence to
> Pov-Ray 3.5 (actually a feature expected to be in 3.5). I was wondering
> if there was any place that could give me information on the upcomming
> edition, like a feature list (what's new type of thing) etc.?
i would rather not know what new feature are planned, i would rather
desperatly wait till its released then spend a week going ' WOW ' :)
(punctuated by ' Why dosnt it work for me!! ' )
Rick
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I wonder if they will finally make Radiosity a non-experimental feature? (I
was never good at using it, though, heh :) Pov-Ray to me is already very
powerful. My fault is getting what is in my head into the syntax of Pov.
(Fortunately Moray has helped that along, though I feel sinful for using it
sometimes :) I remember when 3.1 came out, and it was very anticipated (I
grabbed it off CompuServ before it even hit the website :)
Happy Tracing,
Tim Soderstrom
TigerHawk
Rick wrote:
> > I was hunting around povray.org/links and found a small refrence to
> > Pov-Ray 3.5 (actually a feature expected to be in 3.5). I was wondering
> > if there was any place that could give me information on the upcomming
> > edition, like a feature list (what's new type of thing) etc.?
>
> i would rather not know what new feature are planned, i would rather
> desperatly wait till its released then spend a week going ' WOW ' :)
> (punctuated by ' Why dosnt it work for me!! ' )
>
> Rick
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
TigerHawk <tig### [at] stic net> wrote:
: I wonder if they will finally make Radiosity a non-experimental feature?
I don't know if it will still be experimental in 3.5 (or forever), but I
think that here will always be room for making it better. Although megapov's
radiosity is improved, it still has some problems to be solved.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I wonder if they will finally make Radiosity a non-experimental feature?
(I
didn't you know? povray is just one big experimental feature.....
(they do it to keep up on our toes)
Rick
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Well, I never used Radiosity much because it gave me weird results (probably
because I don't know how to use it), but idea seems sound :) I do hope they
include texutre alignment in 3.5 - It's farily easy to do by hand or with Moray,
but there's always that human error involved. But I don't complain too much,
since it is free and is already very powerful - I just like putting my 2 cents
in every now and then :)
Tim Soderstrom
TigerHawk
Warp wrote:
> TigerHawk <tig### [at] sticnet> wrote:
> : I wonder if they will finally make Radiosity a non-experimental feature?
>
> I don't know if it will still be experimental in 3.5 (or forever), but I
> think that here will always be room for making it better. Although megapov's
> radiosity is improved, it still has some problems to be solved.
>
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hehaehaheae....Yeah, I'll agree with that one :)
Tim Soderstrom
TigerHawk
Rick wrote:
> > I wonder if they will finally make Radiosity a non-experimental feature?
> (I
>
> didn't you know? povray is just one big experimental feature.....
>
> (they do it to keep up on our toes)
>
> Rick
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <395B96C8.135B9B5B@stic.net>, dig### [at] junocom wrote:
> Well, I never used Radiosity much because it gave me weird results
> (probably because I don't know how to use it), but idea seems sound
The radiosity in the official version had some bugs and was slower than
it needed to be. Nathan has fixed a lot of the bugs, and MegaPOV
radiosity is much faster and easier to use.
> I do hope they include texutre alignment in 3.5 - It's farily easy to
> do by hand or with Moray, but there's always that human error
> involved.
Could you explain what you mean by "texture alignment"?
--
Christopher James Huff - Personal e-mail: chr### [at] maccom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://homepage.mac.com/chrishuff/
TAG Web page: http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
> Could you explain what you mean by "texture alignment"?
>
Well, I haven't used MegaPOV itself, but there was a feature I saw in it's
feature list called text alignment (sorry, I typed the 'ure' after by
reflex). I am guessing it solves the problem of having to manually align
the text to the center of an object or wherever you are putting it
Sorry about that :)
Tim Soderstrom
TigerHawk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"TigerHawk" <tig### [at] sticnet> wrote in message
news:395BC4A7.DAFB067F@stic.net...
|
| Well, I haven't used MegaPOV itself, but there was a feature I saw in it's
| feature list called text alignment (sorry, I typed the 'ure' after by
| reflex). I am guessing it solves the problem of having to manually align
| the text to the center of an object or wherever you are putting it
Yes, and it's great. Left-aligned (default), center-aligned, or right-aligned
along the length. There isn't a height alignment, but just being able to
center any length of text is very good.
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Man, no kidding - I wonder why that wasn't done when text was first introduced
into Pov-Ray? Oh well, perhaps with luck it will be in 3.5...
Tim Soderstrom
TigerHawk
Bob Hughes wrote:
> "TigerHawk" <tig### [at] sticnet> wrote in message
> news:395BC4A7.DAFB067F@stic.net...
> |
> | Well, I haven't used MegaPOV itself, but there was a feature I saw in it's
> | feature list called text alignment (sorry, I typed the 'ure' after by
> | reflex). I am guessing it solves the problem of having to manually align
> | the text to the center of an object or wherever you are putting it
>
> Yes, and it's great. Left-aligned (default), center-aligned, or right-aligned
> along the length. There isn't a height alignment, but just being able to
> center any length of text is very good.
>
> Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
TigerHawk wrote:
>
> Man, no kidding - I wonder why that wasn't done when text was first introduced
> into Pov-Ray?
Because the authors of the text-object hadn't much clue about how
to do it, given the rather unclear docs availiable about truetype
specifications.
>Oh well, perhaps with luck it will be in 3.5...
The good news is : even if [any function] doesn't make it into
3.5, you will still be able to use MegaPOV instead...
Fabien.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 30 Jun 2000 23:46:19 +0200, Fabien Mosen wrote:
>TigerHawk wrote:
>>
>> Man, no kidding - I wonder why that wasn't done when text was first introduced
>> into Pov-Ray?
>
>Because the authors of the text-object hadn't much clue about how
>to do it, given the rather unclear docs availiable about truetype
>specifications.
I doubt that. It's pretty simple, and of course they had to know the
bounding box of the object, so alignment is simple.
--
Ron Parker http://www2.fwi.com/~parkerr/traces.html
My opinions. Mine. Not anyone else's.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Ron Parker" <ron### [at] povrayorg> wrote in message
news:slr### [at] linuxparkerrfwicom...
| It's pretty simple, and of course they had to know the
| bounding box of the object, so alignment is simple.
Whoa, hey... a bounding box would show bottom to top of text too, if I'm not
mistaken, meaning it too could be aligned. Front to back also. Wish I were
astute enough to program that in, but alas...
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <395d2f99@news.povray.org>, "Bob Hughes"
<per### [at] aolcom?subject=PoV-News:> wrote:
> Whoa, hey... a bounding box would show bottom to top of text too, if
> I'm not mistaken, meaning it too could be aligned. Front to back
> also. Wish I were astute enough to program that in, but alas...
You don't need to program to do it...MegaPOV also has min_extent() and
max_extent() functions, which provide you with the corners of the
bounding box. Then you can just translate the text to position.
Makes the centering keywords a bit redundant...
--
Christopher James Huff - Personal e-mail: chr### [at] maccom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://homepage.mac.com/chrishuff/
TAG Web page: http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Chris Huff" <chr### [at] maccom> wrote in message
news:chrishuff-6450F5.18504930062000@news.povray.org...
| In article <395d2f99@news.povray.org>, "Bob Hughes"
| <per### [at] aolcom?subject=PoV-News:> wrote:
|
| > Whoa, hey... a bounding box would show bottom to top of text too, if
| > I'm not mistaken, meaning it too could be aligned. Front to back
| > also. Wish I were astute enough to program that in, but alas...
|
| You don't need to program to do it...MegaPOV also has min_extent() and
| max_extent() functions, which provide you with the corners of the
| bounding box. Then you can just translate the text to position.
| Makes the centering keywords a bit redundant...
Uh, yeah, but a keyword is so quick and easy once the feature exists inside of
POV source code
:-)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <chrishuff-6450F5.18504930062000@news.povray.org> , Chris Huff
<chr### [at] maccom> wrote:
> You don't need to program to do it...MegaPOV also has min_extent() and
> max_extent() functions, which provide you with the corners of the
> bounding box. Then you can just translate the text to position.
> Makes the centering keywords a bit redundant...
And you might call this the recommended way for POV-Ray 3.5 :-)
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:395daed5@news.povray.org...
| In article <chrishuff-6450F5.18504930062000@news.povray.org> , Chris Huff
| <chr### [at] maccom> wrote:
|
| > You don't need to program to do it...MegaPOV also has min_extent() and
| > max_extent() functions, which provide you with the corners of the
| > bounding box. Then you can just translate the text to position.
| > Makes the centering keywords a bit redundant...
|
| And you might call this the recommended way for POV-Ray 3.5 :-)
That sounds like a tendency toward lean and fast source code being
contemplated then, if I embellish your words right.
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 1 Jul 2000 08:12:37 -0500, Bob Hughes wrote:
>"Thorsten Froehlich" <tho### [at] trfde> wrote in message
>news:395daed5@news.povray.org...
>| In article <chrishuff-6450F5.18504930062000@news.povray.org> , Chris Huff
>| <chr### [at] maccom> wrote:
>|
>| > You don't need to program to do it...MegaPOV also has min_extent() and
>| > max_extent() functions, which provide you with the corners of the
>| > bounding box. Then you can just translate the text to position.
>| > Makes the centering keywords a bit redundant...
>|
>| And you might call this the recommended way for POV-Ray 3.5 :-)
>
>That sounds like a tendency toward lean and fast source code being
>contemplated then, if I embellish your words right.
You embellish correctly. We are thinking about supplying some macros to
simplify the process a bit, though.
--
Ron Parker http://www2.fwi.com/~parkerr/traces.html
My opinions. Mine. Not anyone else's.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Are there any plans to add some of the more popular include files and
macros, so the users don't have to wander around the net to find them?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <395e14cf@news.povray.org> , "Tony[B]"
<ben### [at] panamac-comnet> wrote:
> Are there any plans to add some of the more popular include files and
> macros, so the users don't have to wander around the net to find them?
We need to make sure we get permission to include any third party include or
scene files. If you have any specific suggestions for files let the TAG or
Dale C. Brodin (he takes care of the include and scene files) know, and then
they will likely be considered. After all we can't add what we don't know
about :-)
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote:
> We need to make sure we get permission to include any third party include or
> scene files. If you have any specific suggestions for files let the TAG or
> Dale C. Brodin (he takes care of the include and scene files) know, and then
> they will likely be considered. After all we can't add what we don't know
> about :-)
If one wants to update his/her macros so that they benefit from the new features
in POV 3.5 and propose them for inclusion in the official distribution, what is
the best solution to proceed, since the list of features (and syntax) is not yet
available ?
G.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <395F7E90.66980114@inapg.inra.fr> , Gilles Tran
<tra### [at] inapginrafr> wrote:
> If one wants to update his/her macros so that they benefit from the new
> features in POV 3.5 and propose them for inclusion in the official
> distribution, what is the best solution to proceed, since the list of features
> (and syntax) is not yet available ?
Hmm, good question! For now just suggest macros, includes, etc based on
3.1. Once POV-Ray 3.5 goes public beta some MegaPOV specific macros can be
adapted to be compatible with POV-Ray 3.5.
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote:
> Hmm, good question! For now just suggest macros, includes, etc based on
> 3.1. Once POV-Ray 3.5 goes public beta some MegaPOV specific macros can be
> adapted to be compatible with POV-Ray 3.5.
The TAG is of course interested in any suggestions the public may
have in this regard. If anyone feels they have a macro that just
has to be included then let us know and we will archive it for
later. If deemed worthy it will then be assimilated into the
collective.
--
Ken Tyler - 1400+ POV-Ray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I think if a 'frequently uses macros' thingie should be in Pov-Ray 3.5, it ought
to be out of choice. I am on a slow connection and the last thing I need is to
wait longer to finish getting Pov-Ray :) I think it's a good idea, but perhaps
having two separate files (ie povray.zip and povray-full.zip) so people who might
not use half of the utilitites provided can save some time.
Just a thought,
Tim Soderstrom
TigerHawk
Ken wrote:
> Thorsten Froehlich wrote:
>
> > Hmm, good question! For now just suggest macros, includes, etc based on
> > 3.1. Once POV-Ray 3.5 goes public beta some MegaPOV specific macros can be
> > adapted to be compatible with POV-Ray 3.5.
>
> The TAG is of course interested in any suggestions the public may
> have in this regard. If anyone feels they have a macro that just
> has to be included then let us know and we will archive it for
> later. If deemed worthy it will then be assimilated into the
> collective.
>
> --
> Ken Tyler - 1400+ POV-Ray, Graphics, 3D Rendering, and Raytracing Links:
> http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sun, 09 Jul 2000 09:42:23 -0500, TigerHawk <tig### [at] sticnet>
wrote:
>I think if a 'frequently uses macros' thingie should be in Pov-Ray 3.5, it ought
>to be out of choice. I am on a slow connection and the last thing I need is to
>wait longer to finish getting Pov-Ray :) I think it's a good idea, but perhaps
>having two separate files (ie povray.zip and povray-full.zip) so people who might
>not use half of the utilitites provided can save some time.
I wish there were enough macros available to, when zipped, slow down
your download time considerably. This is far from the truth, I gather.
Peter Popov ICQ : 15002700
Personal e-mail : pet### [at] usanet
TAG e-mail : pet### [at] tagpovrayorg
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
TigerHawk <tig### [at] sticnet> wrote:
: I think if a 'frequently uses macros' thingie should be in Pov-Ray 3.5, it ought
: to be out of choice. I am on a slow connection and the last thing I need is to
: wait longer to finish getting Pov-Ray
If all those macros take about 10 kilobytes packed, I don't think it's very
relevant compared to the whole povray pack (how large is it? 4 megs or
something?).
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Yeah, that is a good point. Though, it would then seem pretty plausable to include
them in a simple packed zip separate from the archive? I think really what would be
best is to use Twysted's idea and have a whole section on the pov-ray site that is
devoted to things like that. That way it is all there for you to download if ya want
it.
Just some thoughts,
Tim Soderstrom
TigerHawk
Warp wrote:
> TigerHawk <tig### [at] sticnet> wrote:
> : I think if a 'frequently uses macros' thingie should be in Pov-Ray 3.5, it ought
> : to be out of choice. I am on a slow connection and the last thing I need is to
> : wait longer to finish getting Pov-Ray
>
> If all those macros take about 10 kilobytes packed, I don't think it's very
> relevant compared to the whole povray pack (how large is it? 4 megs or
> something?).
>
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <39690D08.895B3A8B@stic.net>, dig### [at] junocom wrote:
> Yeah, that is a good point. Though, it would then seem pretty
> plausable to include them in a simple packed zip separate from the
> archive?
The problem with this is that not everyone would have the same set of
include files...it would make support(and sharing of scene code) a lot
easier if everyone's setup is as similar as possible.
Really, an extra kilobyte or so on a multi-megabyte archive isn't that
big a deal compared to the alternative...
--
Christopher James Huff - Personal e-mail: chr### [at] maccom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://homepage.mac.com/chrishuff/
TAG Web page: http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In my opinion it's better that they are in the same packet specially if
they are documented in the povray documentation.
It doesn't cost anything and you don't have to bother downloading several
files.
Besides, many example scenes can probably use the macros. If they aren't
there, it's a bad thing.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I suppose I can see that - just as long as they are useful and are put nicely
into the directory tree. The only reason I am a bit skeptical is that I don't
use the current include files within the Pov-Ray distribution (except perhaps
for examples). Thoguh they are only color definitions. I still maintain that a
central place for links to macros and includes would be useful on the Pov-Ray
site.
Happy Tracing
Tim Soderstrom
TigerHawk
> In my opinion it's better that they are in the same packet specially if
> they are documented in the povray documentation.
> It doesn't cost anything and you don't have to bother downloading several
> files.
> Besides, many example scenes can probably use the macros. If they aren't
> there, it's a bad thing.
>
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
TigerHawk <tig### [at] sticnet> wrote:
: The only reason I am a bit skeptical is that I don't
: use the current include files within the Pov-Ray distribution
Perhaps not you, but if you download someone other's scene (for example
from this server) and try to render it, it may need those. The same applies
for all the include files and macros downloaded from the net (in the future,
of course).
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Of course, that's not what I was disputing. Origonally I was griping because I
thought they would increase filesize. In the nutshell, idealy I would rather see
Twysted's idea on the Pov-Ray site (whether or not frequently used includes are
in the pov distro or not), but I can understand putting it in the pov
distribution. However, one thing I thought of just now is what if the authors
update their includes? Then you have to go grab them anyway :) So if it's going
to be done, one should consider the space (and that seems to be small) and if
will ever be updated in the future.
Happy tracing,
Tim Soderstrom
TigerHawk
Warp wrote:
> Perhaps not you, but if you download someone other's scene (for example
> from this server) and try to render it, it may need those. The same applies
> for all the include files and macros downloaded from the net (in the future,
> of course).
>
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
TigerHawk <tig### [at] sticnet> wrote:
: However, one thing I thought of just now is what if the authors
: update their includes? Then you have to go grab them anyway :) So if it's going
: to be done, one should consider the space (and that seems to be small) and if
: will ever be updated in the future.
I suppose that most of the macros are of the kind that do not need updates.
For example reorient macros, axis rotation macros and so on.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
>
> TigerHawk <tig### [at] sticnet> wrote:
> : However, one thing I thought of just now is what if the authors
> : update their includes? Then you have to go grab them anyway :) So if it's going
> : to be done, one should consider the space (and that seems to be small) and if
> : will ever be updated in the future.
>
This has been somewhat suggested, but what if there is a system in place
that works like CPAN for Perl (CPAN is a big module repository that
allows anybody to submit to it, and handles dependencies/updates). This
would make a central place for includes and be very useful.
--
--------------------------------------------------------------------
Yann Ramin atr### [at] atrustrivalieeuorg
Atrus Trivalie Productions www.redshift.com/~yramin
Monterey High IT www.montereyhigh.com
ICQ 46805627
AIM oddatrus
Marina, CA
IRM Developer Network Toaster Developer
SNTS Developer * Developer
"All cats die. Socrates is dead. Therefore Socrates is a cat."
- The Logician
--------------------------------------------------------------------
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ack! Will all our POV 3.1 objects become obsolete? Like when POV
3.1 came out it no longer supported the 3.0 objects.
Gilles Tran wrote:
>
> Thorsten Froehlich wrote:
>
> > We need to make sure we get permission to include any third party include or
> > scene files. If you have any specific suggestions for files let the TAG or
> > Dale C. Brodin (he takes care of the include and scene files) know, and then
> > they will likely be considered. After all we can't add what we don't know
> > about :-)
>
> If one wants to update his/her macros so that they benefit from the new features
> in POV 3.5 and propose them for inclusion in the official distribution, what is
> the best solution to proceed, since the list of features (and syntax) is not yet
> available ?
> G.
--
See my Free stuff page. It compares free website providers, and
lists free internet access providers.
http://www.crosswinds.net/~robertsc/free.htm
Win98 help file loaded with hints and tips, including securing a
Win 95/98 PC in a classroom setting. VB4 help file with lots of
code and hints.
At http://www.crosswinds.net/~robertsc/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <39940E1E.EE7FC351@accn.org>, rob### [at] accnorg wrote:
> Ack! Will all our POV 3.1 objects become obsolete? Like when POV
> 3.1 came out it no longer supported the 3.0 objects.
Don't Panic!
Umm, when 3.1 came out, it didn't make any major changes to the object
syntax. All the same objects were supported. Perhaps you mean the
addition of interior and media, and the removal of refraction from
finish and the halo feature?
3.5 is mainly a patch-addition release...if it renders under MegaPOV, it
may render under POV 3.5 with some syntax changes. If it renders under
the official version now, I doubt it will need any changes to render
under 3.5.
--
Christopher James Huff - Personal e-mail: chr### [at] maccom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://homepage.mac.com/chrishuff/
TAG Web page: http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <chrishuff-52CD47.10001011082000@news.povray.org>, Chris
Huff <chr### [at] maccom> wrote:
> ...if it renders under MegaPOV, it may render under POV 3.5 with some
> syntax changes.
I just thought I should emphasize the "may" in this sentence. Not all
the features in MegaPOV will be added: some would interfere with planned
features, some aren't complete enough, and some were just written too
late to be included.
--
Christopher James Huff - Personal e-mail: chr### [at] maccom
TAG(Technical Assistance Group) e-mail: chr### [at] tagpovrayorg
Personal Web page: http://homepage.mac.com/chrishuff/
TAG Web page: http://tag.povray.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chuck Roberts <rob### [at] accnorg> wrote:
: Ack! Will all our POV 3.1 objects become obsolete? Like when POV
: 3.1 came out it no longer supported the 3.0 objects.
Which 3.0 object doesn't the 3.1 not support?
--
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Chuck Roberts <rob### [at] accnorg> wrote:
> : Ack! Will all our POV 3.1 objects become obsolete? Like when POV
> : 3.1 came out it no longer supported the 3.0 objects.
Warp wrote:
> Which 3.0 object doesn't the 3.1 not support?
Halo.
--
Anton Sherwood -- br0### [at] p0b0xcom -- http://ogre.nu/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Anton Sherwood wrote:
>
> > Chuck Roberts <rob### [at] accnorg> wrote:
> > : Ack! Will all our POV 3.1 objects become obsolete? Like when POV
> > : 3.1 came out it no longer supported the 3.0 objects.
>
> Warp wrote:
> > Which 3.0 object doesn't the 3.1 not support?
>
> Halo.
Halo was not an object.
--
Ken Tyler - 1400+ POV-Ray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
