![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Rafal 'Raf256' Maj wrote:
> Daniel Matthews <dan#@3-e.net> wrote in news:110### [at] 3-e net
>
>> Go ahead type that way, then search and replace before you render.
>> No need to change POV at all!
>
> add-on is a good idea imho. I'll see if it will be usefull
>
add-on what?
There is nothing to add, it is just a question of how you choose to use
what is already there!
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) |
On 23 Jul 2002 22:01:38 -0400, Rafal 'Raf256' Maj wrote:
> Something like "color" and "colour" keywords - the second is in fact aliast
> of 1st, and it is added to make SDL comfortalbe.
Actually, if one can be considered an alias of the other, I'd have to say that
the first is the alias. But of course it doesn't actually work that way.
--
#macro R(L P)sphere{L F}cylinder{L P F}#end#macro P(V)merge{R(z+a z)R(-z a-z)R(a
-z-z-z a+z)torus{1F clipped_by{plane{a 0}}}translate V}#end#macro Z(a F T)merge{
P(z+a)P(z-a)R(-z-z-x a)pigment{rgbt 1}hollow interior{media{emission T}}finish{
reflection.1}}#end Z(-x-x.2y)Z(-x-x.4x)camera{location z*-10rotate x*90}
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) |
I would resign my commission as coordinator of the Shortest Code Contest if
this were implemented.
"Christopher James Huff" <chr### [at] mac com> wrote in message
news:chr### [at] netplex aussie org...
> To be blunt, that looks horrible and I hope POV never supports it.
> Sorry. ;-)
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) |
In article <Xns### [at] 204 213 191 226>,
"Rafal 'Raf256' Maj" <raf### [at] raf256 com> wrote:
> finish { ambient 0 }
> finish { ambient 0 diffuse .3 reflection { .2 .4 } metallic .7 brilliance
> 1.2 }
>
> will need 2 macros to make any sens, or one macro to be used like :
> Fin(0, -1,-1,-1,-1,-1,-1);
> where -1 means "default value"
Far too many parameters to be practical there...and what's wrong with a
set of macros?
> ok, It was just a suggestion. Meany peoples says "what, I had to write 10
> pages to get a simpel image ? no - thanks" and it's not easy to convince
> them... well - theirs problem ;)
And a third as many pages of apparently garbage text is an improvement?
People already balk at the idea of learning the scene language, it helps
if the keywords actually make some sense. Someone new to POV sees
"finish" followed by words that describe real-world surface
characteristics and it is fairly obvious the type of thing it referrs
to, they see "@@fi" followed by a bunch of similar garbage and what do
you expect them to think?
--
Christopher James Huff <chr### [at] mac com>
POV-Ray TAG e-mail: chr### [at] tag povray org
TAG web site: http://tag.povray.org/
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) |
In article <Xns### [at] 204 213 191 226>,
"Rafal 'Raf256' Maj" <raf### [at] raf256 com> wrote:
> > Go ahead type that way, then search and replace before you render.
> > No need to change POV at all!
>
> add-on is a good idea imho. I'll see if it will be usefull
The Windows editor doesn't already have search and replace? I'm pretty
sure it does...
--
Christopher James Huff <chr### [at] mac com>
POV-Ray TAG e-mail: chr### [at] tag povray org
TAG web site: http://tag.povray.org/
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) |
> > #macro Fin(Dif, Amb, Spec, Rough, Refl)
> > finish {
> > diffuse Dif
> > ambient Amb
> > specular Spec
> > roughness Rough
> > reflection Refl
> > }
> > #end
>
No need for all that. Just create an include with macros along the lines
of:
#macro fin() finish #end
and use it like:
fin() { ambient 0 diffuse .3 reflection { .2 .4 } metallic .7 brilliance
1.2 }
no need to pass arguments at all and would use only one extra character
beyond the "@fin" you suggested.
I personally have no use for it as I'm perfectly comfortable with the
current syntax. And that whole "@@" thing just weirds me out.
-tgq
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) |
Christopher James Huff <chr### [at] mac com> wrote in
news:chr### [at] netplex aussie org
> referrs to, they see "@@fi" followed by a bunch of similar garbage and
> what do you expect them to think?
"wow, it looks like bash" ;)
in Pascal/Delphi You have
procedure fun(i : integer):integer; begin end;
for i:=1 to 10 do begin end;
in C
fun(int t) {}
for (i=1;i<=10;i++){}
I like C synax mose, and You ?
--
#macro g(U,V)(.4*abs(sin(9*sqrt(pow(x-U,2)+pow(y-V,2))))*pow(1-min(1,(sqrt(
pow(x-U,2)+pow(y-V,2))*.3)),2)+.9)#end#macro p(c)#if(c>1)#local l=mod(c,100
);g(2*div(l,10)-8,2*mod(l,10)-8)*p(div(c,100))#else 1#end#end light_source{
y 2}sphere{z*20 9pigment{function{p(26252423)*p(36455644)*p(66656463)}}}//M
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) |
On 24 Jul 2002, Rafal 'Raf256' Maj <raf### [at] raf256 com> wrote:
> I like C synax mose, and You ?
Perl is nicer:
@baz = $bar =~ /<img[^>]*src="([^">]*?$pattern[^">]*?)"/gi
But seriously, if POV's clear and descriptive SDL was a real
problem, it would've already been addressed. You know, one
of POV's oft-mentioned strong points is that one does not
need to be a programmer to use it.
That said, if the SDL bothers you, CHANGE IT. Write an
interface module that converts your SDL to POV and runs it
through the renderer. It's not even hard with today's
tools, such as Lex and Yacc, especially since you're only
replicating a well-known and -documented, structurally
simple grammar. If you want the very easy way out, you
could even skip the POV syntax checking and just implement
your shorthand grammar, since POV can report any SDL
errors.
--
Antti Arola, edistyksenvastainen retropaskiainen
This message written by a complete asshole.
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) |
In article <Xns### [at] 204 213 191 226>,
"Rafal 'Raf256' Maj" <raf### [at] raf256 com> wrote:
> > referrs to, they see "@@fi" followed by a bunch of similar garbage and
> > what do you expect them to think?
>
> "wow, it looks like bash" ;)
How many people who don't like the scripting aspect of POV will be that
familiar with bash?
Besides, shell scripting languages aren't exactly the ideal of
programming languages... ;-)
> in Pascal/Delphi You have
> procedure fun(i : integer):integer; begin end;
> for i:=1 to 10 do begin end;
>
> in C
> fun(int t) {}
> for (i=1;i<=10;i++){}
You forgot a return type for the C function...and the Pascal also looks
a little funny, though it's been too long since I used it. Comparing a
function and procedure seems odd. Might be differences between what I
learned and Delphi.
> I like C synax mose, and You ?
C. "==" for equality always seemed more obvious than ":=" for
assignment, and the "{}" braces seem like a nice way to enclose blocks,
visually obvious and short to type.
Your point? I don't see any indecipherable abbreviations or weird
symbols in either of those. The "++" operator and for() statement come
close, but are pretty obvious once explained. Pointers definitely would
qualify, for both languages, but I don't think they are relevant...I
definitely wouldn't say people should use either language for POV, since
they are designed for programmers, though parts of the POV language
could be improved by copying them.
--
Christopher James Huff <chr### [at] mac com>
POV-Ray TAG e-mail: chr### [at] tag povray org
TAG web site: http://tag.povray.org/
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) |
On 24 Jul 2002 14:08:35 -0400, Antti Arola wrote:
> On 24 Jul 2002, Rafal 'Raf256' Maj <raf### [at] raf256 com> wrote:
>> I like C synax mose, and You ?
>
> Perl is nicer:
> @baz = $bar =~ /<img[^>]*src="([^">]*?$pattern[^">]*?)"/gi
Why do you think you need minimal matching here?
--
#macro R(L P)sphere{L F}cylinder{L P F}#end#macro P(V)merge{R(z+a z)R(-z a-z)R(a
-z-z-z a+z)torus{1F clipped_by{plane{a 0}}}translate V}#end#macro Z(a F T)merge{
P(z+a)P(z-a)R(-z-z-x a)pigment{rgbt 1}hollow interior{media{emission T}}finish{
reflection.1}}#end Z(-x-x.2y)Z(-x-x.4x)camera{location z*-10rotate x*90}
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |