Recent changes to feature-requests

Could you use the standard open dialog

Anonymous — Thu, 16 Sep 2004 18:55:31 -0000

Is it possible to use the standard KDE open dialog
instead yours. I think than the standard dialog is more
powerfull more easy to use.

One another thing. Why do you put shift+insert as
default paste command .... It's not usefull at all i
think. It's not the default in macintosh and windows.
Where is this shortcut come from ?

thx a lot for your work, i use cute every day

save current working directory

Anonymous — Tue, 07 Sep 2004 16:34:10 -0000

When i open a file, there is always the same directory.

/home/~myself/

Is it possible to save the current working dir ?

Refresh the tree side panel

Anonymous — Wed, 25 Aug 2004 09:37:15 -0000

I can't refresh the tree side panel instead restarting
cute. Is it possible to do something with it ?

Good job in the 0.29 anyway

Exploit signature field from ctags

Frank Boehme — Mon, 16 Aug 2004 16:15:44 -0000

I would love if the tags file was built with the switch
--fields +S
and the resulting information about the signature of
functions/methods/features was used to:

1) Enable API tooltips the way nedit does
2) Show the signature in the tags list

That would help a lot when using cute to develop stuff
that makes use of polymorphism or function overloading.

cheers,

tags preview in message panel

Anonymous — Fri, 26 Mar 2004 16:40:13 -0000

Could the behavior of tags be modified so that the tag is
previewed in the message panel in a new "tags" tab? Then
as a second step, you can jump to the tag by double
clicking on it in the message panel - a bit like how grep
works with its search tab.

Sometimes you want to see a definition without actually
jumping to it, since it is difficult to get back when many files
are open. This would also make it possible to jump to a
specific definition when there is more than one match in the
tags file (when you have different variants of the same
function for example).

Ideally, some surrounding context of the tag taken from its
source file would be shown as well, but the filename, line
number and tag pattern would be a good start.

E.g. tag search for is zload_main and I have two:

test/zload.c:104 int zload_main(int argc, char **argv)
released/zload.c:145 int zload_main(int argc, char **argv)

In this case tag searched for is MAX_STREAMS:

include/zheaders.h:23 #define MAX_STREAMS (10)
include/zheaders.h:25 #define MAX_STREAMS (25)

Or better yet, for MAX_STREAMS, get some context as well:

include/zheaders.h:22 #ifdef PLATFORM1
include/zheaders.h:23 #define MAX_STREAMS (10)
include/zheaders.h:24 #else
include/zheaders.h:25 #define MAX_STREAMS (25)
include/zheaders.h:26 #endif

I hope that make some kind of sense.

Keep up the good work. Thanks for CUTE!

Add hooks to basic actions and writable area in status bar

Anonymous — Fri, 26 Mar 2004 11:01:10 -0000

It would be very useful to be able to call definable python
functions when certain actions occur. For example:

File is opened.
File is Closed.
New buffer is selected (tab clicked).

createCommand(<python func>, <command>)
addHook(<hook type>, <command>)
delHook(<hook type>, <command>)

There could be more than one command assigned to each
hook.

This could be combined with a python writable area in the
status bar (next to where the line and col are displayed) to
give interesting information about the currently displayed file.
E.g. Read only file, CVS version, file size, number of lines...

split window mode with optional locked scrolling

Anonymous — Mon, 22 Mar 2004 16:22:45 -0000

A split window mode is often useful for comparing changes
between two files. I do like the tab MDI mode that is now
the default in 0.2.6, but it would be nice to be able to have
two files displayed at once (with left/right and top/bottom
splits). An icon to select locking of the scrollbars so that the
windows scroll together would be a useful feature too.

This will also be useful later, if somebody decides to
implement a python extension to highlight the differences
between the two files.

More python API functions

Anonymous — Mon, 22 Mar 2004 15:44:26 -0000

There are probably a gazillion functions that could be added,
but a few basic new functions would make the python stuff
more useful:

getLineNumber
getIndexPosition
moveCursorRelative (up, down, left and right)
getLine (text on line)
getChar (char at line and index)
typeInsert (insert char and move cursor right - like typing, or
change current insert function to do this)
openNewline (after current line and after specified line
(optional line augument) and then indent)

These functions would give some basic control to python
which will allow inteligent modification of the buffer. My first
idea is like emacs inteligent braces, which would bind to the
{} keys and auto indent themselves.

Do you have a place to build a library of python extensions
as people write them?

Russian codepages

coder — Mon, 22 Mar 2004 11:34:17 -0000

Is it possible to add support of different codepages
for opening files? like in kwrite or something similar.

Setting for edit window background color

Anonymous — Fri, 12 Mar 2004 13:39:12 -0000

White is fine, but hard on the eyes after a few hours. Would
be nice to take same color as other panels or be fully
customizable.