make FUNCTIONs like so
    function {FORMULA (<parameters>) }
  map{[<1Dval>, <XDmapentry>][<2Dval>, <XDmapentry>][<XDval>,
<XDmapentry>]...}// this maps a function from a 1D var to a colour,
normal etc & others.
  FORMULA = ( ["dll-name"] func-name) | macro-name | formula
   if dll-name is not used pov functions are used
and revamp textures, normals, etc to be able to use these
eg I could use this to have a different pattern for each rgbft channel
by adding the values ...

allow the type of a variable to be obtainable eg gettype(myvar)

Drop "#declare" for non-new variables

"extendable objects, finishes, media, etc"
    #declare myobjtype = new object{ intersections FUNCTION,
surfacehandler FUNCTION, interiorhandler FUNCTION...}
so that you can make custom shaped objects, do freaky stuff to the ray
when it leaves a surface, do freaky stuff to the ray as it goes through
an interior

make POV an object oriented program so the above is possible
    #declare myobj = struct {...}

get the PolyRay author to add a tesselate object modifier

line lights - interpolate between the ends somehow??
with spline stuff
and go from there to triangle lights and then to object lights (maybe
using photons)

displacement  mapping, mapping of any and all texture parameters using
images

have the struct that determines syntax highlighting in the POV-Ray src
(instead of the CodeMax support code) so that
patches can use proper syntax highlighting for their new keywords etc.

Post a reply to this message

Attachments:
Download 'us-ascii' (2 KB)

Pabs <pab### [at] hotmailcom> wrote:
:   FORMULA = ( ["dll-name"] func-name) | macro-name | formula
:    if dll-name is not used pov functions are used

: have the struct that determines syntax highlighting in the POV-Ray src
: (instead of the CodeMax support code) so that
: patches can use proper syntax highlighting for their new keywords etc.

  Povray is NOT a windows program.

-- 
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

Nieminen Juha wrote:
> 
> Pabs <pab### [at] hotmailcom> wrote:
> :   FORMULA = ( ["dll-name"] func-name) | macro-name | formula
> :    if dll-name is not used pov functions are used
> 
> : have the struct that determines syntax highlighting in the POV-Ray src
> : (instead of the CodeMax support code) so that
> : patches can use proper syntax highlighting for their new keywords etc.
> 
>   Povray is NOT a windows program.

So what's wrong with windows platform specific suggestions where the
codemax editor is concerned ? I mean like the Mac version has built
in Quicktime support for compiling animation the other platforms
don't have and you don't hear me bitching about that do you ? Well
not much anyway :)

-- 
Ken Tyler -  1300+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/

Post a reply to this message

Ken <tyl### [at] pacbellnet> wrote:
: So what's wrong with windows platform specific suggestions where the
: codemax editor is concerned ? I mean like the Mac version has built
: in Quicktime support for compiling animation the other platforms
: don't have and you don't hear me bitching about that do you ? Well
: not much anyway :)

  If I understood correctly, he suggested that it would be possible to
specify a "dll-name" in the pov-script. This makes no sense since the
povray script is not platform-dependant.
  It was also unclear how the struct for syntax highlighting would work and
where would it be located.

-- 
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

> >   Povray is NOT a windows program.

	It isn't?  I wonder what I installed on my Windows NT box
	then...  A forgery?  A fake?

	Lets get serious.  When POV came out, the command line
	was the standard thing, DOS, UNIX, lowest common 
	denominator.  Now we have a Windows GUI, a Mac GUI,
	but we're still running around talking about portability.
	
	That's silly.  The core should be kept portable,
	but people should be able to use current technology
	to get what they want out of POVray.

	It's possible to write platform independent code in 
	C++ - but it's not enforced.  The same philosophy should
	apply to POV.

	Things like POV-CSDL - grafting an interpreted C'ish
	kind of thing onto POV - goes to show the extreme
	measures we'd need to enforce the portablity of
	pov scenes, while still not giving people what they 
	really want - a true programmatic interface, in the
	language of their choice.
	
--
Nigel Stewart (nig### [at] nigelscom)
Research Student, Software Developer
Y2K is the new millenium for the mathematically challenged.

Post a reply to this message

On Thu, 16 Mar 2000 15:16:50 +0800, Pabs wrote:

>have the struct that determines syntax highlighting in the POV-Ray src
>(instead of the CodeMax support code) so that
>patches can use proper syntax highlighting for their new keywords etc.

This, at least, should be available before 4.0, assuming all goes according
to plan and so on.  But note the disclaimer; this is not an official 
proclamation.

-- 
These are my opinions.  I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html

Post a reply to this message

On 16 Mar 2000 04:53:15 -0500, Nieminen Juha wrote:

>  If I understood correctly, he suggested that it would be possible to
>specify a "dll-name" in the pov-script. This makes no sense since the
>povray script is not platform-dependant.

Well... it's possible in SuperPatch, which runs on platforms where DLLs
don't make sense.  But it won't be in 3.5, or in 4.0.

>  It was also unclear how the struct for syntax highlighting would work and
>where would it be located.

If we just used the patch I sent to Chris back just before I joined the 
POV-Team, it'd be built on the fly by the Windows support code and sent to 
the Codemax handler.  It's currently hard-coded in the Codemax support DLL.  
But we won't be using that patch, so that's not how it will work.

Don't worry, it's not intended to be cross-platform; this is a Windows-only 
thing, for a Windows-only editor. You may continue to use pov-mode.el syntax 
highlighting.

-- 
These are my opinions.  I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html

Post a reply to this message

Nigel Stewart <nig### [at] nigelscom> wrote:
:> >   Povray is NOT a windows program.

: 	It isn't?  I wonder what I installed on my Windows NT box
: 	then...  A forgery?  A fake?

  Nope, povray is an ANSI-C program. It has been ported to several platforms,
like Windows, but that doesn't make it a Windows program. The binary you
installed is a windows compile of the program, but povray itself is not a
windows program.

: 	Lets get serious.  When POV came out, the command line
: 	was the standard thing, DOS, UNIX, lowest common 
: 	denominator.  Now we have a Windows GUI, a Mac GUI,
: 	but we're still running around talking about portability.
: 	
: 	That's silly.

  Nope, it's not silly. Many people are using povray in a wide variety of
platforms (which support or don't graphical user interfaces).

: 	It's possible to write platform independent code in 
: 	C++ - but it's not enforced.  The same philosophy should
: 	apply to POV.

  No it shouldn't. Povray has to be able to compile in any platform which
has the proper compiler. Portability is a very serious issue.
  I understand why most windows users just can't understand how someone likes
to use something else than windows and graphical programs.

: 	Things like POV-CSDL - grafting an interpreted C'ish
: 	kind of thing onto POV - goes to show the extreme
: 	measures we'd need to enforce the portablity of
: 	pov scenes

  Pov scenes and the povray source code are two completely different things.
Don't mix them.

-- 
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

> :       It's possible to write platform independent code in
> :       C++ - but it's not enforced.  The same philosophy should
> :       apply to POV.
> 
>   No it shouldn't. Povray has to be able to compile in any platform which
> has the proper compiler. Portability is a very serious issue.

	Yes it should.  Enforced portability is very limiting.
	I'm talking about the portability of POV scenes,
	not the C implementation - which I agree should be
	kept portable.

>   Pov scenes and the povray source code are two completely different things.
> Don't mix them.

	I'm not, you are.

--
Nigel Stewart (nig### [at] nigelscom)
Research Student, Software Developer
Y2K is the new millenium for the mathematically challenged.

Post a reply to this message

On Fri, 17 Mar 2000 01:53:12 +1100, Nigel Stewart wrote:
>	Yes it should.  Enforced portability is very limiting.
>	I'm talking about the portability of POV scenes,
>	not the C implementation - which I agree should be
>	kept portable.

*boggle*  You're saying it would be good to be able to make POV scenes that 
don't render on every platform for a given version of POV?  Can we just send
all the support questions to you?  What color is the sky in your world?

-- 
These are my opinions.  I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html

Post a reply to this message