 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Antti Arola <aea### [at] iobox fi> wrote in news:slr### [at] skavaraese
> That said, if the SDL bothers you, CHANGE IT. Write an
> interface module that converts your SDL to POV and runs it
yes I will try
--
#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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 24 Jul 2002 14:48:06 -0400, Ron Parker <ron### [at] povrayorg> wrote:
> On 24 Jul 2002 14:08:35 -0400, Antti Arola wrote:
>> Perl is nicer:
>> @baz = $bar =~ /<img[^>]*src="([^">]*?$pattern[^">]*?)"/gi
>
> Why do you think you need minimal matching here?
I have no idea; I merely wrote that, surely you cannot
ask me to *understand* it as well?-)
(To be honest, it does what it's supposed to do, with
enough reliability for its purpose, and that's enough
incentive for me to stop trying to fix it. <g>)
[no POV here, f'ups set.]
--
Antti Arola, edistyksenvastainen retropaskiainen
This message written by a complete asshole.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello guys,
I don't think it is a good idea to add that ugly syntax to povray.
The best solution is write a preprocessor to do the translation just like
Antti said.
Povray looks great as it is. We don't mind typing extra because it looks
nice.
Anyway, All the best.
Fidel.
in article Xns### [at] 204213191226, Rafal 'Raf256' Maj at
raf### [at] raf256com wrote on 24/7/02 1:45 am:
> Hi,
> I have a little suggeston / future-request.
> Myself I like usign Pov without any editor (to type code "by hands" :)
> but there are one thing that IMHO makes it unnesesarly uncomfortalbe -
> [too] long names.
>
> Compare i.e.:
>
> difference {
> sphere { ... }
> torus { ... }
> finish { roughness 1 brillaince 2 relfection { .2 .5 } metallic 9 diffuse
> 0.7 }
> } superellipsoid { ... }
>
> with :
>
> @@diff {
> s { } tr { }
> fi { rou 1 bril 2 ref { .2 .5 } met 9 diff 0.7 }
> } @sup { ... }
>
>
> So the idea is to use aliases for important names, and to mark them with
> '@'.
>
> Implementation imho would be quite easy - ther is probalby one function
> that reads next element, and tells is it an object, float, string,
> undeclared identyfier, etc...
>
> So only we have to do something like
> void interprate(char *s) {
> if (s[0]=='@') {
> char *x = // match alias name, "s","tr","fi" etc
> interprate(x);
> }
> }
>
>
>
>
> The more advanced idea is :
>
> if alias is marked by "@@" like @@diff { ... } then assume that every name
> in it can be an alias, even it it is not marked with "@" (or "@@")
>
> example :
> @sp { @fi { @ref } } // ok. sp=sphere fi=finish ref=reflection
> @sp { fi { ref { } } // errors, fi and ref must be marked by "@"
> @@sp { fi { ref { } } // ok fi and ref are inside "@@" block
> @sp {@@fi { ref { } } // ok ref is inside "@@" block
>
> maybe alsow it will be a good idea to implement @! operator, that removes
> aliases from following block (i.e when we need names like "fi" in it)
>
> #declare fi = 5.0;
> @@sp {
> fi { }
> @!pig {
> fi // fi is here an 5.0 float
> }
> }
>
> this new syntax might look strange now, but it will shorten code about x3
> times ! x3 shorter code = x3 more writing, x3 more comfortable
> x3 more code on ona page (or screen)
>
>
>
>
> My suggestions :
>
> @tex texture
> @mat material
> @fin finish
> @nor normal
> @int interior
>
> @cmap color_map
> @nmap normal_map
> @mmap material_map
>
> @sp sphere
> @bo box
> @pl plane
> @to torus
>
> @sup superellipsoid (that's a good example ;)
> @blo blob
>
> @br brilliance (only in finish block)
> @di diffuse (only in finish block)
>
>
> I want to *help* to implement aliases, but I can not do it my self (I do
> not understand Pov's souces enought)
>
>
> what do You thing about it ? If You agree that this is usefull, and
> somebody also want's to implement it - I will help :)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Rafal 'Raf256' Maj wrote:
> So the idea is to use aliases for important names, and to mark them with
> '@'.
>
> Implementation imho would be quite easy - ther is probalby one function
> that reads next element, and tells is it an object, float, string,
> undeclared identyfier, etc...
>
If you use a Win32 environment, you might want to consider something
like NoteTab for your editor (http://www.notetab.com/). Here's some
of the options it could invoke to help you with what you are
describing...
1. Notetab supports user defined "auto-replace" libraries, which will
scan for certain keywords you define and replace them on the fly as you
type. You could define "@am" as a keyword and have Notetab automatically
change it to "ambient" as soon as you hit the spacebar, and the editor
is sure you are done with that word. This is nearly what you are asking
to do, except that no changes to POV are required. Same saved typing,
though.
2. The built in "clipbook" scripting can do things as simple as letting
you click on a named link and have it auto-insert the text, to as
complicated as popping up a dialog box for the parameters and typing the
whole block of code for you. So, assuming you set up the custom clipbook
items you find most helpful, you can do something as easy as click on
the word "ambient" and have Notetab insert the text "ambient" at the
current cursor position, or as complex as click on "sphere" and Notetab
prompts you for a radius and center then generates a skeletal code for
a sphere based on your input. You write the clipbooks yourself, so you
get to decide what commonly needed features need to be automated and
even change your mind as your coding needs change over time. These
clipbooks can also execute command lines so you can launch the file
in POV-Ray with just another click.
3. My favorite feature: Notetab has support to shell out to any perl
or gawk interpreter you may have installed allow you to process the
current active file thru a script automagically. It works like this:
If there's a user selection in the text, that selection is fed to your
script via STDIN and any output the script returns via STDOUT is dumped
in as a replacement for the selection. If no user selection exists,
Notetab by default does a select all on the complete file, so the entire
active file gets processed. This allows maniuplations of darn near
any complexity in a relatively painless, automated fashion. You could
write a script that preprocesses your code by scanning for any custom
abbrievations or syntax extensions you've defined and output regular,
POV standard code as the final result. This is the most complicated
option and the one requiring the most programming knowledge, but it
allows for the greatest possible flexibility in manipulating your code.
Heck, you could write a whole second language and have your script
pre-process it into POV SDL output if you were that ambitious. :)
Charles
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
