On 2008-04-10 at 12:31:24 [+0200], Stephan Assmus <superstippi@xxxxxx> wrote: > > Rainer Riedl wrote: > > > be implemented by having one view (PText) per split-pane. Eddie does it > > > this way and that makes it possible to cater for more than two views, > > > too [not that I have many uses for that, though ;-)]. > > > > Hmm, I have. Sometimes I copy some pieces of code to the place I work at > > the moment and the I have to lookup another piece of code. At the moment > > that means use one split-pane for searching and then I have to find the > > previous part again. Sometimes timeconsuming > > IMHO, a better feature alltogether for this thing would be "bookmarks". The > bookmark should probably be smart and remember not only offset in the file, > but also context, so it follows the passage along. I wouldn't remove > splitting though, since it can be nice to see two passages at once. > However, to jump forth and back between two or more passages, I think > bookmarks are more to the point and probably easier to implement as well. I personally never liked the split approach. When splitting I would obviously get only half the visible area for each of the views, which is pretty annoying, since I set the window size to what it is not for no reason. Also, I'm fan of the 80 colums limit, which means I have lots of horizontal space on the screen, but a vertical split uses none of it. I'd much rather be able to simply open the same document in another window. Oliver's refactoring proposal didn't say so explicitly, but I guess he meant to imply it, obviously the model should be separated from the views and controllers. I.e. we would have a PTextModel (or maybe just PText, if preferred), which would be shared between the windows, and a PTextSelectionModel, as well as view/editor and controller components, which would not be shared. Regarding bookmarks respectively cursor history, the one in Eclipse works pretty well, I think. CU, Ingo