 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
At povray.binaries.utilities you will find my latest version of a Python
script that displays a GUI (a la windows) to edit, render,....POV scenes.
As always, should you like it or comment it, the agency......
In short, comments are welcomed.
Fabien HENON
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
How does it handle extra ini and inc files not in the primary inc dir?
Fabien wrote:
> At povray.binaries.utilities you will find my latest version of a Python
> script that displays a GUI (a la windows) to edit, render,....POV scenes.
>
> As always, should you like it or comment it, the agency......
> In short, comments are welcomed.
>
>
> Fabien HENON
--
Your connection failed because: It's not RFC-822 compliant.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
? What do you mean ?
To add a new dir for include files, you just have to use indicate the path in
the parameters line or in the primary ini file.
I hope I understood you question right.
Fabien
> How does it handle extra ini and inc files not in the primary inc dir?
>
> Fabien wrote:
>
> > At povray.binaries.utilities you will find my latest version of a Python
> > script that displays a GUI (a la windows) to edit, render,....POV scenes.
> >
> > As always, should you like it or comment it, the agency......
> > In short, comments are welcomed.
> >
> >
> > Fabien HENON
>
> --
> Your connection failed because: It's not RFC-822 compliant.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Well if you just open the demo files from the POV dir with your editor
some, that have their own .inc will not render.
Should you add (as a default in your editor) the dir of the .pov file to
the include path passed to the renderer, so that any extra .inc that may be
there are found?
The radiosity example for pov 3.1g is one that can't run "out of the box"
from your editor.
Otherwise, great job and thanks for writing the editor.
> ? What do you mean ?
> To add a new dir for include files, you just have to use indicate the path
> in the parameters line or in the primary ini file.
> I hope I understood you question right.
>
> Fabien
>
>
>
>> How does it handle extra ini and inc files not in the primary inc dir?
>>
>> Fabien wrote:
>>
>> > At povray.binaries.utilities you will find my latest version of a
>> > Python script that displays a GUI (a la windows) to edit,
>> > render,....POV scenes.
>> >
>> > As always, should you like it or comment it, the agency......
>> > In short, comments are welcomed.
>> >
>> >
>> > Fabien HENON
>>
>> --
>> Your connection failed because: It's not RFC-822 compliant.
--
Your connection failed because: Your cat tried to eat the mouse.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ok ! I see. I'll fix it.
Thanks
> Well if you just open the demo files from the POV dir with your editor
> some, that have their own .inc will not render.
>
> Should you add (as a default in your editor) the dir of the .pov file to
> the include path passed to the renderer, so that any extra .inc that may be
> there are found?
>
> The radiosity example for pov 3.1g is one that can't run "out of the box"
> from your editor.
>
> Otherwise, great job and thanks for writing the editor.
>
>
> > ? What do you mean ?
> > To add a new dir for include files, you just have to use indicate the path
> > in the parameters line or in the primary ini file.
> > I hope I understood you question right.
> >
> > Fabien
> >
> >
> >
> >> How does it handle extra ini and inc files not in the primary inc dir?
> >>
> >> Fabien wrote:
> >>
> >> > At povray.binaries.utilities you will find my latest version of a
> >> > Python script that displays a GUI (a la windows) to edit,
> >> > render,....POV scenes.
> >> >
> >> > As always, should you like it or comment it, the agency......
> >> > In short, comments are welcomed.
> >> >
> >> >
> >> > Fabien HENON
> >>
> >> --
> >> Your connection failed because: It's not RFC-822 compliant.
>
> --
> Your connection failed because: Your cat tried to eat the mouse.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 24 May 2002 20:28:28 +0200, Fabien wrote:
> At povray.binaries.utilities you will find my latest version of a Python
> script that displays a GUI (a la windows) to edit, render,....POV scenes.
>
> As always, should you like it or comment it, the agency......
> In short, comments are welcomed.
I have now installed python 2.2.1 and have tried your program, a few
comments:
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.
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.
I'd really like to be able to change those editr colours via some menu
options, I hate working on a white background.
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.
--
%HAV-A-NICEDAY email mailto:ste### [at] zeropps uklinuxnet
Steve web http://www.zeropps.uklinux.net/
or http://start.at/zero-pps
10:41pm up 3 days, 20:34, 1 user, load average: 1.08, 1.05, 1.06
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
> 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
|
|
| |
| |
|
|
|
|
| |
|
|
