--- In koneditor@yahoogroups.com, Björn Andersson <bjorn_and@y...>
wrote:
>
> radekxx wrote:
> > What do you like to see in the next version of the editor? Here
are
> > a few wishes of a new potential user of the editor.
>
> Thanks!
>
> > (1) Allow configuring of the cursor shape.
> > Not everybody likes the huge blinking block of the overwrite
> > cursor :-) This can be mended by allowing to configure the cursor
> > width. Any units of the cursor width are equally good so that the
> > configuration option can want the values of (in case of OS/2)
> > WinCreateCursor parameters. Everybody can set the cursor by
> > experimenting.
>
> Was possible in 1.x, easy to add, yes.
>
> > (2) Add configuration option "Kill trailing blanks".
> > At present - at least, as far as I know - trailing blanks at the
> > ends of the lines are stored with the saved file. When the
option is
> > set, the trailing blanks will be removed during file save.
>
> Easy to write a K-script for that, I'll do that.
>
> > (3) Allow configuring of the command line font.
> > The current font is too small at high resolution screens.
>
> I use 1920x1200 on a 24" TFT-screen and 1280x1024 on a 18.1" TFT-
screen.
> It has been big enough for me. Could you post a screenshot?
> >
> > (4) OS/2: Allow hiding of the message window.
> > Perhaps, it's my lack of experience with the editor but I haven't
> > found how to close it :-) It should be possible to reopen the
window
> > if it is wanted.
>
> Click once on the bar between the arrows.
>
> > (5) Do something with the "sections" highlighting option.
> > The current state is perfect in most cases but not in all cases.
> > Object oriented languages, like C++, have problems. They need to
> > select a group to display in the taglist but the wanted portion
of
> > the name in the taglist need not consist of a single group.
> > Simultaneously, the groups in the regular expression cannot be
> > modified.
> > The current taglist for C++ will display member functions without
> > the class name. Moreover, it will not display operators (this
can be
> > mended). Here is my suggestion:
> >
> > (a) Use *two* "group to use" parameters. The first marks the
> > beginning of the name in the taglist, the second marks it's end.
> > (b) The taglist will display everything between the limiting
groups
> > (including the limiting groups).
> > (c) Define two special "groups": '-1' = beginning of the
expression,
> > and '99' = end of the expression.
> > (d) Compatibility: Allow only one "group to use" as well, and
> > reinterpret 'regexp, N' as 'regexp, N, N' and then
> > reinterpret 'regexp, 0, 0' as 'regexp, -1, 99'.
> >
> > This should fix the problem. We can always create a "no use"
group
> > in a regular ecpression without affecting the regular expression.
> > Well, we can use the "no use" groups for marking. A possible
> > collision - the marked character should be a part of some group,
> > which must be there - should not occur in the case of the
taglist.
>
> I'll have to reread this when I get home (after the weekend.) I
cannot
> say I follow the thoughts right now. To much to do at work :(
>
> Thank you!
> Björn

The command line font:
See the file ke0001.jpg in the "files" area. This is a result from a
21" LCD, 1600x1200 in my work. Of course, winblows, not OS/2. I have
1600x1200 19" (Sony E450) at home. The font is well readable but too
small.
The file is 124 kB. If you are the moderator, please remove the file
when it isn't needed any more.

Radek