POV-Ray : Newsgroups : povray.unix : QTPov Editor v0.3.1 : Re: QTPov Editor v0.3.1 Server Time
5 Jul 2024 14:31:44 EDT (-0400)
  Re: QTPov Editor v0.3.1  
From: gRRosminet
Date: 2 Apr 2004 11:04:55
Message: <406d8f27$1@news.povray.org>
Marin Ferecatu wrote:

Actually, I find the start-up logo very nice (and impressive :-)

==> thanks


One typo:
Menu Help->About brings up a dialog with a spelling error:
"GNU __Genreal__ Public License" should be "GNU __General__ Public 
License" (see underscore)

==> oooooops


Florian Brucker wrote:

1. I read the documentation online (the menu item in the editor does not 
work, do I have to set some env-variables?). Now I know a lot more about 
your program

==> and that's the reason for this documentation !
The menu tries to launch 'mozilla 
http://qtpoveditor.sf.net/help/help.html &'


2. Although I now know that there is a way to use custom command lines, 
I still think that a option tab like the old one is pretty useful.

==> You're not the first to say such a thing, but having the two systems 
would be heavy to manage and personnaly, I spend the same time using the 
ini system or the other.


3. As your insert menu only uses files with the .txt extentions, could 
you get rid off the .txt extension in the menu items? (Would simply look 
cooler

==> Good remark ! There is a long time I want to do it, always forgotten :-/


4. When using the assistant to create an ini-file, would it be possible 
to only output those options which differ from the default values? Right 
now if I change only the resolution, I get more than one page of 
options, all but the resolution ones showing the default values...
And if I define a section like this in the ini (without the assistant)

[400x300 no AA]
width=400
height=300

and later use the assistant to add another section to the ini, my own 
custom one (3-liner from above) will be blown up like described above, too

==> I know, I know, but I have no idea of how doing it properly


5. I think it would be a good idea if your editor would still create the 
output-filename automatically (if it is not defined in the ini). If I 
have to change the ini everytime I want to render another file, then I 
have no need for an editor
And of course the ".pov" extension should be cut from the filename (so 
the image is not called "myscene.pov.png" (like in former versions), but 
"myscene.png").

==> there is no need to specify the output filename ! povray does it 
itself !



Christoph Hormann wrote :
It is quite a bit better than the last version i tried but i still have 
a bunch of things i don't like.  Don't take this too seriously of course.

- the POV-Ray output should use a fixed width font
==> I'll add an entry for this in the preferences

- the automatic indention does not really work.  When 'use true tabs' is 
activated it does not at all, otherwise typing:

box {<enter>
-1, 1<enter>
}<enter>

results in:

box {
   -1, 1
   }

==> I'm seriously thinking about solving this problem


- the path selection tool could be so nice and load the library_path 
settings from the main povray.ini as default.

==> in fact, my objective is to load them from the .ini that is in use 
(with a preference item to define the path to the default povray.ini)


- i hate the standard qt file dialogs - the KDE ones are so much better 
to use...

==> everyone does not have KDE (I know people still using fvwm2). And 
using KDE tools implies to install your application in the KDE bin 
directory and to recompile KDE if you recompile QT ....


- the insert menu images are displayed on the upper left of the main 
window - showing them in a separate toolbar element might be a better idea.

==> there is no toolbar : it's only displayed when using the insert menu.


- the file chooser could insert the file name without the path when it 
is in the given search paths (would make scenes more portable).

==> yes, it's a good idea







I hope that all this will answer your questions !

Thierry


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.