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