|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi everybody.
I'm following advices from Fabien HENON so I annonce you that I have
started to write a new editor for povray under Linux ( Fabien have
nothing to do with it : he's advaice was to post here :-) ). It's based
on the povwin interface but includes many more features
It requires QT 3.2 and X11 and it's not finish, so you can send me
features requests
the project homepage : http://qtpoveditor.sf.net
Thanks
Thierry
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"thierry" <thi### [at] les-charlesnet> wrote in message
news:3fa14ba6$1@news.povray.org...
|From your page:
|
| it only edit your files, colors them to highlight syntax, manage
| the rendering and its options, allow you to include some code like
| does the windows' version of povray and ,finaly, it makes a summary
| of all the declarations of variables and macros in your scenes but
| also in the included files.
|
What else do you have planned?
Also:
In English, present tense, third person, singular nouns ("the cat", "the
bird", etc.) and pronouns (he, she, it) use verbs with "s" or "es" on
the end.
for example:
We *edit* (first person plural)
I *edit* (first person singular)
You all *edit* (second person plural)
You *edit* (second person singular)
They *edit* (third person plural)
==> He *edits* (third person singular)
==> The editor *edits* (third person singular)
==> My program *edits* (third person singular)
-Shay
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have planned to do everything I can do, and I invite you to make
suggestions on sourceforge : http://www.sourceforge.net/projects/qtpoveditor
Thierry
P.S. : I'm sorry for my poor english : I'm not perfect (and that's the
only thing I'm sure to be)
> "thierry" <thi### [at] les-charlesnet> wrote in message
> news:3fa14ba6$1@news.povray.org...
>
> |From your page:
> |
> | it only edit your files, colors them to highlight syntax, manage
> | the rendering and its options, allow you to include some code like
> | does the windows' version of povray and ,finaly, it makes a summary
> | of all the declarations of variables and macros in your scenes but
> | also in the included files.
> |
>
> What else do you have planned?
>
> Also:
> In English, present tense, third person, singular nouns ("the cat", "the
> bird", etc.) and pronouns (he, she, it) use verbs with "s" or "es" on
> the end.
>
> for example:
> We *edit* (first person plural)
> I *edit* (first person singular)
> You all *edit* (second person plural)
> You *edit* (second person singular)
> They *edit* (third person plural)
> ==> He *edits* (third person singular)
> ==> The editor *edits* (third person singular)
> ==> My program *edits* (third person singular)
>
> -Shay
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"gRRosminet" <pov### [at] les-charlesnet> wrote in message
news:3fa186a1@news.povray.org...
|
| I have planned to do everything I can do, and I invite
| you to make suggestions on sourceforge :
I asked because your editor seemed very complete already. I will make
some suggestions on sourceforge in a few days after I have had a chance
to download and try your editor. Error highliting comes immediately to
mind. Some nice additional features would be a reload hot-key and a
mechanism for folding text. The text-folding is less important in Linux,
as the lack of I/O restrictions allows better organization of many small
files.
|
| P.S. : I'm sorry for my poor english :
I hope you don't feel that I was being presumptuous. I *only* gave that
suggestion because I felt that you might want to use it for your
webpage. I don't make a habit of correcting peoples' news-group
postings.<grin>
-Shay
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
I think it's quite normal : French is a little bit more complicated than
english !
Thierry
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Shay wrote:
> The text-folding is less
> important in Linux, as the lack of I/O restrictions allows better
> organization of many small files.
IMO code folding is a killer feature :)
--
Rick
Kitty5 NewMedia http://Kitty5.com
POV-Ray News & Resources http://Povray.co.uk
TEL : +44 (01270) 501101 - ICQ : 15776037
PGP Public Key
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x231E1CEA
Post a reply to this message
|
|
| |
| |
|
|
From: Wolfgang Wieser
Subject: Re: New editor for Linux : QTPOV Editor
Date: 2 Nov 2003 10:08:02
Message: <3fa51dd1@news.povray.org>
|
|
|
| |
| |
|
|
> It requires QT 3.2 and X11 and it's not finish, so you can send me
> features requests
>
Nice concept.
Here is a list of little bugs and missing features:
That's just what comes to my mind to give you some ideas.
>you can now run ./qtpoveditor or install it where you want on your
>system.
Well... I'd suggest that default colors need to be adjusted.
I'm using Qt-3.2.1 and running the editor from the shell:
bash# ./qtpoveditor
loading preferences ... QFile::open: No file name specified
...and all I get is all editor colors being black ending up in
black text on black background.
The "POVRay Output" tab has two entries called "Additional options",
one of them probably meaning "binary path".
Also, the layout allows too small window sizes...
The Replace dialog only has "Find" and "Cancel" buttons.
When quitting, the "Some files open..." dialog shows up even if
all open files are non-modified.
The render button has a tool tip "Unnamed".
The render button will try and render the previously opened file
even if this file is no longer open. Open files A and B, close A
and press render button -> renders A instead of B (the active tab
is the POVRay tab).
Then press the tab for file "B" -> SIGSEGV !
What is definitely missing:
- show matching brackets () {} <> []
- dialog for where to put the output file
- show complete povray command line as first line in the povray
output window
- correct undo behaviour: when inserting text and then some edit menu
code OR from the declarations window and then pressing undo, one would
expect only the edit menu code/decl code to disappear but the
text manually inserted before should stay there (and disappear with
the next undo call)
- what about "Help" -> "About" ?
- support nested C-style comments /* /* cmt */ still cmt */
just as POVRay does
Some cool features which are not as easy to implement:
- context-sensitive completion; if I type in
"prism { li" then it could smartly suggest to complete with
"near_sweep". Have a look at good IDEs on how that is normally done.
- Text "folding".
- Improve editor... Currently the benifits and comfort of a good editor
like nedit still outwage the additional functionality of QTPOV editor,
at least for me.
To be concrete, I mean:
- Shortcuts for adding/subtracting indent space for selected lines.
- Shortcut "jump to matching bracket"
- goto line number
- find selected text
- I like the concept of using the shift key for the oppostite direction
(find next/find prev; undo/redo...)
- cut, paste & move with mouse... unfortunately incompatible with Qt...
IMO, three click selection should select the complete line including
the \n at the end, but that's probably a Qt issue.
Cheers,
Wolfgang
Post a reply to this message
|
|
| |
| |
|
|
From: Nicolas Calimet
Subject: Re: New editor for Linux : QTPOV Editor
Date: 2 Nov 2003 15:10:09
Message: <3FA564A1.3060708@free.fr>
|
|
|
| |
| |
|
|
> The text-folding is less important in Linux,
> as the lack of I/O restrictions allows better organization of many small
> files.
What do you mean by "the lack of I/O restrictions" ?
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Nicolas Calimet" <pov### [at] freefr> wrote in message
news:3FA### [at] freefr...
|
| What do you mean by "the lack of I/O restrictions" ?
|
Believe it or not. I've been creating scenes in win-pov for a long time
under this misconception. I tried to open a file with:
#fopen "C:\~\scenes\projectfolder\subfolder\output.inc" write
a long long time ago. I must have mistyped it, misread the error
message, whatever, because I have mistakenly believed in the time since
that this was not possible. Thanks for asking this question!! It will
help me a lot to clean up the project folder of my next project.
-Shay
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I'd like to thank you for this detailed analysis : it's realy helpfull
Thanks.
Thierry
>>It requires QT 3.2 and X11 and it's not finish, so you can send me
>>features requests
>>
>
> Nice concept.
> Here is a list of little bugs and missing features:
> That's just what comes to my mind to give you some ideas.
>
>
>>you can now run ./qtpoveditor or install it where you want on your
>>system.
>
>
> Well... I'd suggest that default colors need to be adjusted.
> I'm using Qt-3.2.1 and running the editor from the shell:
>
> bash# ./qtpoveditor
> loading preferences ... QFile::open: No file name specified
>
> ...and all I get is all editor colors being black ending up in
> black text on black background.
>
> The "POVRay Output" tab has two entries called "Additional options",
> one of them probably meaning "binary path".
>
> Also, the layout allows too small window sizes...
>
> The Replace dialog only has "Find" and "Cancel" buttons.
>
> When quitting, the "Some files open..." dialog shows up even if
> all open files are non-modified.
>
> The render button has a tool tip "Unnamed".
>
> The render button will try and render the previously opened file
> even if this file is no longer open. Open files A and B, close A
> and press render button -> renders A instead of B (the active tab
> is the POVRay tab).
> Then press the tab for file "B" -> SIGSEGV !
>
> What is definitely missing:
> - show matching brackets () {} <> []
> - dialog for where to put the output file
> - show complete povray command line as first line in the povray
> output window
> - correct undo behaviour: when inserting text and then some edit menu
> code OR from the declarations window and then pressing undo, one would
> expect only the edit menu code/decl code to disappear but the
> text manually inserted before should stay there (and disappear with
> the next undo call)
> - what about "Help" -> "About" ?
> - support nested C-style comments /* /* cmt */ still cmt */
> just as POVRay does
>
> Some cool features which are not as easy to implement:
>
> - context-sensitive completion; if I type in
> "prism { li" then it could smartly suggest to complete with
> "near_sweep". Have a look at good IDEs on how that is normally done.
>
> - Text "folding".
>
> - Improve editor... Currently the benifits and comfort of a good editor
> like nedit still outwage the additional functionality of QTPOV editor,
> at least for me.
> To be concrete, I mean:
> - Shortcuts for adding/subtracting indent space for selected lines.
> - Shortcut "jump to matching bracket"
> - goto line number
> - find selected text
> - I like the concept of using the shift key for the oppostite direction
> (find next/find prev; undo/redo...)
> - cut, paste & move with mouse... unfortunately incompatible with Qt...
>
> IMO, three click selection should select the complete line including
> the \n at the end, but that's probably a Qt issue.
>
> Cheers,
> Wolfgang
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |