[Lazarus] editor details

[Hans-Peter Diettrich]

Martin schrieb:

> I do admit that the amount of possible combinations of settings is quite 
> large, and that it is not necessarily always obvious how certain 
> combinations are supposed to work:
> 
> for example:
> - Caret-past-eol = false
> - trim spaces = PositionOnly
> 
> Trim spaces = "position only" means that pressing a space at the end of 
> line, doesn't insert that space (the spaces are only generated, once you 
> type some text behind them).

We may have more issues with the now possible multiple views.


>>> 2- the user experience during usage
>>
>> Sometimes it could be a bit less sensitive to errors in related 
>> components. 
> Which related components? Or are you speaking of codetool navigation?

I frequently get FPDoc messages, when scrolling through source code. 
It's nasty to click them away.

The crashes, observed while editing (cut&paste), may be related to some 
other tool (auto format...), but occured only last week, no more now.


>> But except for the current multi-window redesign, the editor and IDE 
>> was usable since 0.9.26, and has become very stable since 0.9.28 :-)
> 
> In which way is the current redesign not working or making the IDE 
> unstable? Sure there were individual revisions that exposed some bugs => 
> that is what it says on the label: current SVN is not a released version...

I had some crashes in the last weeks, but now it seems to have widely 
stabilized :-)


> Except for, if you do not like extra windows, you do not use the feature 
> => that still means the IDE is working and usable.

I *need* multiple editor windows, missed them since my first contact 
with Lazarus! That's how I came to docking, in anticipation of multiple 
code explorers, dockable to the editor windows.

With a more general use of docking, the SynEdits could be replaced by 
other editor components. Not that I don't like the SynEdits, but some 
users (including me) sometimes feel an wish of a different GUI. Maybe a 
split into interface/implementation panes, or navigation from a project 
or unit explorer, with edits restricted to a single selected procedure 
or method. A tighter coupling of the logical caret position to a 
navigation map or tree (code explorer...) sometimes were very nice.

I think that now, when the views have been separated from the source 
files, it should be easy to implement such additional (maybe user 
specific) components or effects.

DoDi