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