I am writing an editor for POV-RAY using Python ( a highly portable
scripting language and Tkinter which is included).

It is still in beta stage : It is working, but a lot of features have
still to be added.

You just have to have python installed ( it is included in most linux
distributions).
You can find at www.python.org

Once installed just type the following line where 82.py is saved :
  >python 82.py

I also assumed that x-povray is installed in /usr/bin/

Comments are appreciated
I know it still a long way

NB : It works with Windows 2000 ( and Mac ?). The render process doesn't.


TODO:
Include output, error streams in the application.
Save the parameters before exiting.
Implement syntax color highlight (Any help there would be appreciated)
Add a horizontal scrollbar to the text editor.
Improve the 'not-too-accurate' line number.
Implement the edit menu. It is useless for the time being.


Fabien

Post a reply to this message

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

What advantages does this editor have over Emacs+povmode?

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

Warp wrote:

>   What advantages does this editor have over Emacs+povmode?

I haven't looked at the editor, but probably it's smaller. :-)

SCNR
Thomas

Post a reply to this message

Thomas Willhalm <wil### [at] fmiuni-konstanzde> wrote:
> I haven't looked at the editor, but probably it's smaller. :-)

  By the same logic my own sphere raytracer is better than POV-Ray because
it certainly is a lot smaller.

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

Warp wrote:

>   By the same logic my own sphere raytracer is better than POV-Ray because
> it certainly is a lot smaller.


   Of course! It's better for raytracing scenes with spheres only...




-- 
Jaime Vives Piqueres

http://www.ignorancia.org/
La Persistencia de la Ignorancia

Post a reply to this message

What I don't like in emacs is that is that, you have to twiddle with parameters
and see at the end that it does not work.
It can do many things ( too many ?).

I just want to fire up an editor that allows debbugging, and launches POV with a
keypress or a button.

My application is meant for the newbies in Linux who don't want to bother
parameters and files to move and edit.

I say it again, this is a starter. I knew nothing of Python 2 months ago.



>   What advantages does this editor have over Emacs+povmode?
>
> --
> #macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
> N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
> N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

I get this:

[sjlen:News]$ python 82-2.py
Traceback (innermost last):
  File "82-2.py", line 4, in ?
    from os import spawnv, P_NOWAIT
ImportError: cannot import name spawnv
[sjlen:News]$ 

And in future if you're going to post the code how about just copying
and pasting it into the message rather than making it an attachment,
it's a bit confusing trying to work out where the file starts. 

povray.utilities might have been a better place to post the code, and 
put a message in here to announce it. 

Here's the python version information if it's any help. 

Python 1.5.2 (#1, Jul  5 2001, 03:02:19)  [GCC 2.96 20000731 (Red Hat 
Linux 7.1 2 on linux-i386

--
#local i=.1;#local I=(i/i)/i;#local l=(i+i)/i;#local ll=(I/i)/l;box{<-ll,
-((I/I)+l),-ll><ll,-l,ll>pigment{checker scale l}finish{ambient((I/l)/I)+
(l/I)}}sphere{<i-i,l-l,(I/l)>l/l pigment{rgb((I/l)/I)}finish{reflection((
I/l)/I)-(l/I)specular(I/l)/I}}light_source{<I-l,I+I,(I-l)/l>l/l} // Steve

Post a reply to this message

Jaime Vives <jai### [at] ignoranciaorg> wrote:
>>   By the same logic my own sphere raytracer is better than POV-Ray because
>> it certainly is a lot smaller.

>    Of course! It's better for raytracing scenes with spheres only...

  No, it isn't, because it's a *LOT* slower than POV-Ray even with a modest
amount of spheres (some tens of them).

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

> What I don't like in emacs is that is that, you have to twiddle with parameters
> and see at the end that it does not work.

  But you don't have to do that each time you want to edit a povray file.
You configure emacs _once_, and then you just edit pov files.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

> > What I don't like in emacs is that is that, you have to twiddle with parameters
> > and see at the end that it does not work.
>
>   But you don't have to do that each time you want to edit a povray file.
> You configure emacs _once_, and then you just edit pov files.
>

I know but I never managed to do it once. I may be dumb ( yet I followed the
instructions ).

>
> --
> #macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
> [1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
> -1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message