> 
> I got as far as pressing the render button before it realised that 
>   it was pointing at a pov executable that didn't exist, it may be 
>   an idea to check this when you open pyvon and allert the user if
>   the executable doesn't exist, you could also do this for 
>   directories listed in pyvon.ini too. 

Ok I'll add a warning message if there is no executable is found where 
the pyvon.ini tells there is one

> 
> On the first run of the program there was a command line box visible
>   at the bottom of the screen, along with some other useful information,
>   on subsequent invocations this line does not appear. 
> 
You mean the command line parameters ?
I don't see why it should disappear while the other windows are still 
there. Do you have an error to the console when you start pyvon ?


> I'd really like to be able to change those editr colours via some menu 
>   options, I hate working on a white background. 
Ok, I'll work on it.

> I'd say your program is working well at this stage, and would encourage 
> you to keep up the good work, this will be a very useful tool for people
> who are new to Linux.  I'll be watching further developments with 
> interest, but you'll never get me to use anything other than emacs for 
> my own work in POV-Ray.  
Ok, I am working on making you change your mind too.
By the way. I have always wondered what is so great about emacs.
  - There are a trillion cascade menus -> You never know where to look 
at the first (and tenth) try. The interface is way too confused
  - I always get \r (return line) at the end of my lines.
  - The open file dialog is unuseful
I have many other grievances that I forget at the moment, but I know why
  I started pyvon : Because I found that emacs was too complicated to 
edit script efficiently.

I guess that I'll get flames from the emacs afficionados now.



Thanks a lot for the comments and ideas

Fabien

Post a reply to this message