Right now there's the Editor Window (EW). A "fake" split would work like this:

In split mode the main window consists of the original EW, a splitter and a View Window (VW)The EW is active and works as normal. The VW is just a snapshot (image) of the editor view at specific position.Then when the user clicks the VW and makes that active, the two windows "swap place". So now the EW is in the position that was occupied by the VW and vice versa.That way you only have to update the VW in certain cases.

There are 10 types of people in the world: Those who understand binary and those who don't.

I'll bring this up for the next major features review. Personally I feel like this is one of those features that are for the show. I have never seen anyone use it professionally neither personally, nor in coding videos/streams. But that's just my personal opinion and that has never stopped me from adding a highly requested feature if it can be done so that the user experience is great.

There are situations where a splitview is extremely useful, like when you are manually refactoring code.

But a lot of it's use could be done with a good bookmark system, which WeBuilder is still lacking.

The bookmark system needs a way to name the bookmarks (Similar to editors like UltraEdit, which has a very similar/simple bookmarking system)And it also needs a docking panel, so you can switch between bookmarks quickly.

With these 2 extra bookmark features, I could manage without a splitview for a while

There are 10 types of people in the world: Those who understand binary and those who don't.

Use ctrl + shift + 1..9 to toggle a bookmark and ctrl + 1..9 to jump to corresponding bookmark quickly. What I often do is add ctrl + shift + 1 to the function that I'm editing and ctrl + shift + 2 to the place where I call this function and then I just jump back and forth using ctrl + 1 and ctrl + 2.