big YES to the two questions!

I still do not like some features, but I won't complain - yet :) I'll give
the new editor all the chances (and time) to convert me.
I am collecting a small list of bugs, and I will send it as soon as I
feel it to be complete.

BTW such problems as 'save as command doesn't provide
the old file name as default, nor is in the old directory', are to be
sent as a bug report by email, or to be posted here
as a feature proposition ?


Good day to everybody,

Sincerely,

Philippe

Post a reply to this message

>BTW such problems as 'save as command doesn't provide the old file name
>as default, nor is in the old directory', are to be sent as a bug report
>by email, or to be posted here as a feature proposition ?

Either. Posting here as a feature proposition is a better idea.

The 'save as' feature has now been modified to work as expected.

Post a reply to this message

povray.org admin team wrote:

> Does anyone find the new editor in POVWIN beta 6 to be an improvement ?
>
> BTW If there is sufficient interest we will post a new editor DLL that has one
> new feature added since the beta 6 release - it allows you to right-click on a
> #include line and automatically open the file that is being included.

  One major difference between 3.01 and 3.1b6 is the saving speed.

I was working on a file today that was about 6.5 megs in size.

3.01  was able to save after changes in about 2 sec.
3.1b6 was able to save after changes in about 10 - 15 seconds

At least a 10:1 difference.

K.Tyler

My system:
pentium 166 128 megs of ram windows 95 b

Post a reply to this message

In article <35e5f9d1.4652950@news.povray.org>, new### [at] DESPAMpovrayorg 
(povray.org admin team) wrote:

> Does anyone find the new editor in POVWIN beta 6 to be an improvement ?
> 
> BTW If there is sufficient interest we will post a new editor DLL that 
> has one
> new feature added since the beta 6 release - it allows you to right-click 
> on a
> #include line and automatically open the file that is being included.
> 
It's a big improvement, thanks for doing it.  The new feature would be very 
useful as well.


Ian Armstrong
iar### [at] cixcouk

Post a reply to this message

povray.org admin team wrote in message <35e5f9d1.4652950@news.povray.org>...
>Does anyone find the new editor in POVWIN beta 6 to be an improvement ?
>


Are you kidding? This is the best thing that's happened to me since I came
back from vacation at the seaside. Here's a list of the 'little' things that
made me really love it:

- the way the 'home' key works...

- block indent

- match brace

- etc.

And a thing that disturbs me (not enough for a bug report, though): the
default output file type seems to be sys (.BMP). Since .BMPs are written
backwards POV makes an full-sized (900k for 640x480 -ua) empty file and goes
on... OK, but when I instaled POV I started playing around with demo scenes
at 800x600 +sp8 and was kinda bewildered where my HDD space had gone ... and
then I saw about 50 megs of .BMPs. I looked through the manual and the .INIs
and didn't see a notice of sys being default output file type. If this is
so, please document this change or make .TGA default (as it was).

>BTW If there is sufficient interest we will post a new editor DLL that has
one
>new feature added since the beta 6 release - it allows you to right-click
on a
>#include line and automatically open the file that is being included.

Sounds good. What if the .INC is recursive ? <G> Anyway, this will probably
help add a nice feature: what about highlighting undeclared identifiers as
you type (to save some nerve?)

Congratulations to the Team on the great job they've done with beta6!

Regards,

--Peter

pet### [at] usanet

Post a reply to this message

As soon as I installed and ran the new version
I really liked it.  For me, it has a much better feel
to it.  A big Thank You to the POV Team for this
great program.  The new feature also sounds good.
Please keep up the great work.

                David Young

Post a reply to this message

I agree -- the new editor is an excellent upgrade!

However, there are still features in emacs in POV mode
that make that, to me, preferable.   Pardon me if I
am missing features in the current POV-W9x editor.
The features are:

1. Indent-line indent-region and indent-buffer :
   automatically set indentation of a line, region, 
   or the entire buffer
2. Parenthesis matching : when a closing parenthesis is typed,
   the curser briefly highlights the matching opening parenthesis.
   If a closing parenthesis is typed after an opening bracket,
   for example, a warning is issue.   AFAICT, the POV-W9x editor
   only does parenthesis matching on highlighted parentheses,
   which interrupts typing.

   However, the color code and auto-indentation of the POV
   W9x editor does provide a nice visual clue if parenthesis
   matching is off, so I am being picky here.

Still, I can hardly complain -- the new editor is a real programming
editor and a huge improvement over the previous edition, which
itself was quite usable.

I add my thanks to those of others posted here.

Dan

David Young wrote:
> 
>     As soon as I installed and ran the new version
> I really liked it.  For me, it has a much better feel
> to it.  A big Thank You to the POV Team for this
> great program.  The new feature also sounds good.
> Please keep up the great work.
> 
>                 David Young

-- 
http://www.flash.net/~djconnel/

Post a reply to this message

>1. Indent-line indent-region and indent-buffer :
>   automatically set indentation of a line, region, 
>   or the entire buffer

What exactly do you refer to here ? You can block-indent an entire selection if
you want (just as easily as the entire buffer since there's a select all key).
So I presume you mean something else ?

Post a reply to this message

povray.org admin team wrote:
> 
> Does anyone find the new editor in POVWIN beta 6 to be an improvement ?
> 

While the old editor was good and usable, calling the new one an
"improvement"
is a gross understatement, IMHO. The new editor's features represent a
quantum
leap over the old one...three cheers for the POV-Team!!!

Post a reply to this message

The new povwin editor really is great. And, as everything,
as always, as everywhere, it can get even better. For me,
it should involve solving these bugs, including these
suggestions:

BUGS
* intellimouse support? what intellimouse support?
* state flashs in info bar
* 'open' button disabled on unmodified file... but
  not the menu command
* ctrl+] match brace shorcut can't work on an belgian
  azerty keyboard (you have to press ctrl+alt+$ to get
  a ], so you can't add a ctrl over this), and I can't
  change the shortcut
* shift+click doesn't select
* open and save dialogs sometimes give focus to other
  applications on closing
* the end of a render sometimes takes focus from an other
  application (particulary the help)
* = isn't highlighted (either as an assignement or as a
  logical operator)
* copy on no selection does copy an empty string (logical
  but not usual)
* Render/Edit setting/render (alt C) does render the previously
  saved file, bypass the save dialog and the quit-bugging-me.

SUGGESTIONS
* return of the 'open in' command
* 'save' and 'save as' in the context menu
* ability to select and copy text in message window
* many 'strange' shorcuts if you have such standards
  as MS Office, Adobe products or Macintosh's command
  shortcuts:
  redo - ctrl+y
  close - ctrl+w
  print - ctrl+p
  replace - ctrl+h (ctrl+shift+F3 ???)
  Is it so difficult to get all shorcuts customisable?
* toolbars are a bit too big. I would redesign them this
  way if I could: move two help buttons to the 'main'
  toolbar, remove theCD's and web sites buttons (but keep the
  corresponding commands in the Help menu) and remove the
  pretty but totally useless render animation.
* does anybody use the 'overwrite' mode? What is it usefull
  for? If nobody use this, I would gladly see it desappear,
  as I am always confused whenever I turn it on - always
  by accident.
* move 'older files' at the end of the file list
* regroup the 'editor' menu with the 'options' menu
* still no command line editor
* a better and clearer structure for the help



Here are two last suggestion that I know are in conflict
with actual pov team orientation. (I know because I am not
the first to post about them). But I do not understand the
pov team position, as all they said was something like 'no,
we won't'. I do not say that there isn't a good reason, I
just ask what are the practical, design or programing
reason for an answer I do not understand. Maybe I am
missing the point? (Hey, saying 'no, we have enough work as
it is' is a very good reason... an excellent one. And an
unarguable one.)

(1) Why can't the 'quit bugging me' feature be kept from
session to session?

(2) The editor behaviour which permits to select where
there aren't any character is really great. But a normal
text editor behaviour (like the last one) is more
convenient most of the time (I kinda checked this, I
watched myself working). This means: snap to the end of
line clicked in 'vacuum', left and right arrows can jump
to the previous or next line, don't add space at the end
of lines when inserting a carriage return in the 'vacuum'.
The 'select anywhere' feature could be used with
ctrl+click, like the collumn selection (this would be
coherent). Or you could toggle edit modes.

As always, all these suggestions reflect an user approach,
not a programmer's one.


By the way, did you try these wonderfull features or the
new editor?

* tab or shif-tab (= 'back-tab') a selection
* collumn selection (ctrl+drag)
* cut, copy and paste of collumns selection
* click'n'drag a selection


And let all say a big 'THANK YOU POV-TEAM' for their
thruly remarquable work.


Sincerely,


Philippe


P.S. I wrote earlier that I'll give the new pov editor
some time before asking anything... well, I did: I worked
two full days with it since (but as I do not have network
access on my computer I have to wait before posting, that
explains the missing day).

Post a reply to this message