[Lazarus] Lazarus options

[Martin Friebe]

Hi,

just trying to keep my intentions in sync with the lazarus teams 
expectations.
So a couple of questions to follow up the remarks in 
http://bugs.freepascal.org/view.php?id=9652

- I was planning to add an option to switch on/off the highlight all 
feature in incremental search. Should I? or is it better to have it 
always on? (also consider this with the option below the === mark in 
mind, please)

- I also had the idea to add *options* for
   - match bracket on *before* caret
 curently matches  bracket after caret, which is not usefull, 
because if you typed a closing bracket, it is *before* the caret
 ( maybe even match both sides)

- Add options to match unbalanced brackets (in an error color)
  foo( string[ index );
  is missing a ], so if either on the ) or the [ then they shoudl 
match each other, but highlight in red (or as unbalanced)
  this can help a good deal finding them in bigger terms.

==
- I do agree that on the *current* page, vincent's remark  Less options 
is better is true.
I was thinking about grouping the options into individual sets:

* tabs and spaces
 - smart tabs
 - tabs to spaces
 - trim trailing spaces
 - tab indent block
 - auto indent ??
* Display
 - show special chars
 - use syntax highlight
 - bracket highlight
* Hints
 .
* scroll
  - half page scroll
  - keep caret x ??
  - always visible caret
  - scroll by one less
  - scroll past end of file // line
* mouse and drag ??
 - drag and drop
  - drop files
  - right mouse moves caret
  - double click line
  - mouse links
* misc

If that makes sense, I can see and work out what IMHO would go where.

Also is there a decision when or if the new edit options will be in 
place? It would be nice not do to this twice.
 

then maybe some options should could be combined? (drop down or radio?)
scoll by one less + half page scroll  == half page  - one line ?

that is if half-page was always obeyed, and affected vertical scroll too?



___
Lazarus mailing list
Lazarus@lazarus.freepascal.org
http://www.lazarus.freepascal.org/mailman/listinfo/lazarus

Re: [Lazarus] Lazarus options

[Mattias Gaertner]

On Tue, 22 Jul 2008 18:15:38 +0100
Martin Friebe [EMAIL PROTECTED] wrote:

 Hi,
 
 just trying to keep my intentions in sync with the lazarus teams 
 expectations.
 So a couple of questions to follow up the remarks in 
 http://bugs.freepascal.org/view.php?id=9652
 
 - I was planning to add an option to switch on/off the highlight all 
 feature in incremental search. Should I? or is it better to have it 
 always on? (also consider this with the option below the === mark
 in mind, please)

Don't add an option if no one uses it.

 
 - I also had the idea to add *options* for
- match bracket on *before* caret
  curently matches  bracket after caret, which is not usefull, 
 because if you typed a closing bracket, it is *before* the caret
  ( maybe even match both sides)

I don't see the need. Jut change it to *before*.

 
 - Add options to match unbalanced brackets (in an error color)
   foo( string[ index );
   is missing a ], so if either on the ) or the [ then they shoudl 
 match each other, but highlight in red (or as unbalanced)
   this can help a good deal finding them in bigger terms.

Again: Why an option? This is always a nice feature.

 
 ==
 - I do agree that on the *current* page, vincent's remark  Less
 options is better is true.
 I was thinking about grouping the options into individual sets:
 
 * tabs and spaces
  - smart tabs
  - tabs to spaces
  - trim trailing spaces
  - tab indent block
  - auto indent ??
 * Display
  - show special chars
  - use syntax highlight
  - bracket highlight
 * Hints
  .
 * scroll
   - half page scroll
   - keep caret x ??
   - always visible caret
   - scroll by one less
   - scroll past end of file // line
 * mouse and drag ??
  - drag and drop
   - drop files
   - right mouse moves caret
   - double click line
   - mouse links
 * misc
 
 If that makes sense, I can see and work out what IMHO would go where.

ok

 
 Also is there a decision when or if the new edit options will be in 
 place? It would be nice not do to this twice.

When someone completes it.

 
 then maybe some options should could be combined? (drop down or
 radio?) scoll by one less + half page scroll  == half page  - one
 line ?

ok
 
 that is if half-page was always obeyed, and affected vertical scroll
 too?

?


Mattias
___
Lazarus mailing list
Lazarus@lazarus.freepascal.org
http://www.lazarus.freepascal.org/mailman/listinfo/lazarus