 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
v0.3.1 is out. Special thanks to Marin Ferecatu for his improvements. If
someone wants to work on the logo and especialy on the icon it would be
realy a good thing because mine are quite bad :-/ but they are ! :-)
This release is only available as source tarball.
Changes :
v0.3.1
* recursive insert menu (thanks to Marin Ferecatu)
* insert menu displays the .bmp preview if it exists (thanks to Marin
Ferecatu)
* new logo and icons !
* some other minor improvements
Thanks for your support
Thierry
Downloads :
http://sourceforge.net/project/showfiles.php?group_id=92021&package_id=110070&release_id=228000
Supporting my project :
http://sourceforge.net/donate/index.php?group_id=92021
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> * recursive insert menu (thanks to Marin Ferecatu)
> * insert menu displays the .bmp preview if it exists (thanks to Marin
> Ferecatu)
> * some other minor improvements
You integrated everything very nicely!
> * new logo and icons !
Actually, I find the start-up logo very nice (and impressive :-)
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)
Thank you for this release.
Marin.
--
-----------------------------------------------------------------------------
Replay-to address is fake. Please replace it
with mferecat (at) numericable (dot) fr.
-----------------------------------------------------------------------------
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
gRRosminet wrote:
> v0.3.1 is out.
Hm. Looks nice (although the splash screen only shows for 0.0001 seconds
over here :)
Unfortunately I won't use it, because I think this INI-assistant is too
blown up, especially for test renders, where often only antialiasing
yes/no, and resolution are changed. And one cannot specify a custom
command line in 3.x...
IMHO best thing would be to combine the options-tab from former version
with the assistant from the new ones.
Don't get me wrong, you're doing great stuff and I'm really happy for
having your editor!
Florian
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Unfortunately I won't use it
Just changed my mind :) But only because this tab-bug of the old
versions really sucks *g*
So I'll be able to give you some feedback, soon.
Florian
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> So I'll be able to give you some feedback, soon.
And here it comes:
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 :)
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.
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 :)
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 :(
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").
Florian
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
gRRosminet wrote:
> v0.3.1 is out. Special thanks to Marin Ferecatu for his improvements. If
> someone wants to work on the logo and especialy on the icon it would be
> realy a good thing because mine are quite bad :-/ but they are ! :-)
>
> [...]
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
- 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
}
- the path selection tool could be so nice and load the library_path
settings from the main povray.ini as default.
- i hate the standard qt file dialogs - the KDE ones are so much better
to use... ;-)
- 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.
- the file chooser could insert the file name without the path when it
is in the given search paths (would make scenes more portable).
Christoph
--
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 21 Mar. 2004 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
gRRosminet wrote:
> [...]
>
> - 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 ....
Well - there are surely good reasons to design this as a plain QT
program but i wonder if this is really what people would prefer. Most
Unix users who use POV-Ray will run a fairly modern Linux distribution
and will be able to use a KDE program - no matter if KDE is their DE or
not. They will probably be hardly interested in compiling either QT or KDE.
And making this a KDE program could also have advantages for you as the
programmer - you could use the standard KDE editor component (Kate) and
would not need to worry about syntax highlighting, indention etc...
But that's just my personal and very biased opinion of course and an
important argument for staying with plain QT is surely the much better
portability.
> - 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.
>
I think you misunderstood me - right now they are displayed at a fixed
position that is not very nice - displaying the image in a toolbar would
enable the user to move this somewhere he likes it best.
Christoph
--
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 21 Mar. 2004 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Christoph Hormann wrote:
>> - 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.
>>
>
> I think you misunderstood me - right now they are displayed at a fixed
> position that is not very nice - displaying the image in a toolbar would
> enable the user to move this somewhere he likes it best.
>
The problem is that there is no reason to keep this toolbar at top when
scripting and if you try to move this toolbar when insert menu is open,
insert menu will disapear ... finally, your tool will ever be at a wrong
place whereas with the current solution it is locked in a visible place
: it's not very nice, but functionnal ! :)
Thierry
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Just to inform you that I have installed a new website for QTPov Editor.
There is a lot of work to realize before to get it complete but it is on
the way !
As you'll discover it, I have added a forum to enhance your
brain-storming ;-P
Thierry
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
