 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Shorter words are not easier to read, only slightly faster to type. But you
can already save that typing in POV-Ray (for Windows anyway).
Try to type the following (where *TAB* means pressing TAB):
light*TAB**TAB*
dif*TAB*
pig*TAB*
norm*TAB*
fini*TAB*
spec*TAB*
refl*TAB*
Rune
--
3D images and anims, include files, tutorials and more:
rune|vision: http://runevision.com
POV-Ray Ring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Try to type the following (where *TAB* means pressing TAB):
>
> light*TAB**TAB*
> dif*TAB*
> pig*TAB*
> norm*TAB*
> fini*TAB*
> spec*TAB*
> refl*TAB*
Thank you very much for this tip, I realy didn't know it!
> Seems like a very nice feature to just go $variablename instead of
#declare
> all over in a .pov file. Quicker to type, easier to read, and so on.
I agree with you, on both points (typing and reading). I suggest
implementing only this feature, besides giving the TAB-trick a more
prominent place in the FAQ/manual.
Greetings,
JWV
"Rune" <run### [at] runevision com> wrote in message
news:411e20a7$1@news.povray.org...
> Shorter words are not easier to read, only slightly faster to type. But
you
> can already save that typing in POV-Ray (for Windows anyway).
>
> Try to type the following (where *TAB* means pressing TAB):
>
> light*TAB**TAB*
> dif*TAB*
> pig*TAB*
> norm*TAB*
> fini*TAB*
> spec*TAB*
> refl*TAB*
>
>
> Rune
> --
> 3D images and anims, include files, tutorials and more:
> rune|vision: http://runevision.com
> POV-Ray Ring: http://webring.povray.co.uk
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
run### [at] runevisioncom news:411e20a7$1@news.povray.org
> Try to type the following (where *TAB* means pressing TAB):
> light*TAB**TAB*
Oh, I thought that You where talking about this ctlr+space thingy, this
definetely should be in FAQ, help and Tip of the day.
But I still suggest shortucts for most long expressions, for example
reflection -> refl
specular .5 roughness 0.01 -> spec .5, 0.01
etc... why not?
--
http://www.raf256.com/3d/
Rafal Maj 'Raf256', home page - http://www.raf256.com/me/
Computer Graphics
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Brian Elliott wrote:
<snip>
> Also, though this doesn't help those on open-source ports of PoV-Ray, the
> Windows users of PoV-Ray have that lovely in-built editor. All one need do
> on WinPov is type "sph" then press Tab, and you have your complete word.
> Try it with "pig" as well!
<clip>
I've been using the Tab shortcut for quite sometime now. I can't
remember if I found it accidentally or not... it doesn't matter. What
matters is that it WORKS. I save a lot of time using it.
The more I thought about my 'aliasing' idea last night, the closer to
your opinion I found myself..... and then there was your reply. We don't
need to confuse the code and make it unreadable. It's not so hard to
type out the keywords, especially if we have the Tab feature built into
the editor. Perhaps those working on other operating systems can push to
have this functionality placed into their editor?
-Sam
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Also, though this doesn't help those on open-source ports of PoV-Ray, the
> Windows users of PoV-Ray have that lovely in-built editor. All one need do
> on WinPov is type "sph" then press Tab, and you have your complete word.
> Try it with "pig" as well!
Dunno about povmode for emacs etc., but if you're using QtPOVEditor
(qtpoveditor.sf.net), you have that auto-complete-thingy for both
keywords and custom identifiers.
I normally don't like full-quotes, but I got the impression that if
everyone anticipating in this discussion right now would reread
Christoph's post, there would not be much to discuss anymore:
"It leads to awfully obfuscated code. [...] With the same arguments you
could replace every other keyword with the shortest unique abbreviation
- but no one could read the code any more then."
So, think again - how much time do you really spend with typing only
when you're creating a POV scene? IMHO POV SDL allows some pretty
cryptic stuff already (and yes, I'm using that, too ;) so there's no
need to make it even more complicated.
While talking about SDL changes, the only thing that one would IMHO
benefit from is the #set keyword from former MegaPOV, combined with an
error/warning when trying to re-declare already declared identifiers.
Florian (who would like to have references in POV-SDL, too ;)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Rafal 'Raf256' Maj wrote:
> run### [at] runevisioncom news:411e20a7$1@news.povray.org
>
>
>>Try to type the following (where *TAB* means pressing TAB):
>>light*TAB**TAB*
>
>
> Oh, I thought that You where talking about this ctlr+space thingy, this
> definetely should be in FAQ, help and Tip of the day.
>
> But I still suggest shortucts for most long expressions, for example
> reflection -> refl
> specular .5 roughness 0.01 -> spec .5, 0.01
>
> etc... why not?
>
Because the full English words are standard and self-documenting
Because it adds unnecessary complication to every aspect of the endeavour
Because it would in no way result in better pictures
Because it is a bloat-feature based in a bloat mentality
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <411e6a9c$1@news.povray.org> , Jim Charter <jrc### [at] msncom>
wrote:
>> etc... why not?
>>
> Because the full English words are standard and self-documenting
> Because it adds unnecessary complication to every aspect of the endeavour
> Because it would in no way result in better pictures
> Because it is a bloat-feature based in a bloat mentality
Very well said!
Thorsten
____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg
I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
jrc### [at] msncom news:411e6a9c$1@news.povray.org
> Because the full English words are standard and self-documenting
cone { begin_point x*4 end_point 5*x radius 10 }
this is self-documented
> Because it adds unnecessary complication to every aspect of the endeavour
I dont know what endeavour is, but as for implementation the basic aliases
are very easy to implement
> Because it would in no way result in better pictures
More comfortable work = more time to concentrate on picture itself.
> Because it is a bloat-feature based in a bloat mentality
?
--
http://www.raf256.com/3d/
Rafal Maj 'Raf256', home page - http://www.raf256.com/me/
Computer Graphics
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
spa### [at] raf256com news:Xns9545ED4602E3Craf256com@203.29.75.35
(...)
but anyway I do not insist so hard about aliases, since Tab future is
greate, if only it would be implemented also in linux-editors...
--
http://www.raf256.com/3d/
Rafal Maj 'Raf256', home page - http://www.raf256.com/me/
Computer Graphics
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
agreed.
"Jim Charter" <jrc### [at] msncom> wrote in message
news:411e6a9c$1@news.povray.org...
> Rafal 'Raf256' Maj wrote:
> > run### [at] runevisioncom news:411e20a7$1@news.povray.org
> >
> >
> >>Try to type the following (where *TAB* means pressing TAB):
> >>light*TAB**TAB*
> >
> >
> > Oh, I thought that You where talking about this ctlr+space thingy, this
> > definetely should be in FAQ, help and Tip of the day.
> >
> > But I still suggest shortucts for most long expressions, for example
> > reflection -> refl
> > specular .5 roughness 0.01 -> spec .5, 0.01
> >
> > etc... why not?
> >
> Because the full English words are standard and self-documenting
> Because it adds unnecessary complication to every aspect of the endeavour
> Because it would in no way result in better pictures
> Because it is a bloat-feature based in a bloat mentality
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
