Re: editor settings list

[Dirk Vangestel <dirk_vangestel yahoo com>]

--- Jeroen Zwartepoorte <Jeroen xs4all nl> wrote:
> Hi,
> 
> Although there's still a fatal bug somewhere in
> either my config code or
> in bonobo, i don't want to stop developing the
> config stuff.
> 
> I've drawn up a list of editor settings which i
> think would be useful to
> put in the Editor Settings dialog. Some of these
> settings directly come
> from the Scintilla API, others from the Editor
> Options in JBuilder 4.
> 
> I personally don't have any experience with vi,emacs
> etc. so i don't
> know if these options are also representative for
> those editors. 
> 
> Since the GUI is based on bonobo-conf, libglade
> cannot be used here. I
> do plan to create a prototype GUI using glade and
> then have it generate
> C code and copy & paste that (saves a lot of work).
> 
> Please comment and provide feedback.
> 
> Thanks,
> 
> Jeroen
> 
> 
> 
> Editor options:
> 
> Category:
> Editor
> - Use tab character
> - Indentation size (tab width if "use tab
> character", otherwise number of spaces)
> - Smart home (jump to first character on line,
> second HOME moves to beginning of line)
> - Smart end (jump to last character on line, second
> END moves to EOL)
> - Indent after brace
> - Align closing curly brace
> - Folding code blocks
> - Keymaps? (vi, msvc, emacs etc. Use Bonobo for
> this?)
> Display
> - Highlight braces
> - Show blinking caret
> - Show line-numbers
> - Show indentationguides (visual tab location
> indicator)
> - Show End-Of-Line indicators
> - Show whitespace
> - Show right margin (vertical line usually at column
> 80)
> 	- Set margin location (#columns)
> - Font family
> - Font size
> Color
> - Editor/Lexer styles
> 	- Font style (plain/bold/italic)
> 	- Fore- & background color
> 	- Schemes?
> 	- Preview?
> Macros?
> Templates? (insert predefined codefragments (GPL
> comments, for loop etc.))
> Codeinsight?

I think you're putting too much functionality in the
editor. The things you put in 'display' are more
suited to be put in an editor interface than the stuff
you put in 'editor'. Putting too much functionality in
the editor interface will severely limit the choice of
editors (for example vi will have lots of problems
implementing the stuff in display, let alone the stuff
in editor).
But that's just IMHO of course :)
I'd rather have a 'standard' properties page with
essential features and 'advanced' properties page(s)
whith differ per editor (so that there actually is a
reason to support multiple editors... there's no use
in offering anything but scintilla if you're requiring
all editors to have the same features). The 'standard'
properties could be shared between editors while the
others would be editor specific.
Otherwise you'd have to work with capabilities
(inquire which functions are being implemented by a
certain editor and present options for only those
functions).

Dirk


__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/