Re: Add function to rotate/transpose all windows

[Pranshu Sharma]

martin rudalics <rudalics@gmx.at> writes:

> The line
>
>> If FRAME-OR-WINDOW window or frame, operate on it. If
>> FRAME-OR-WINDOW is nil.
>
> doesn't make sense.  I'd still go with my earlier proposal

This was just placeholder to check if you like the other parts, I
search-replaced it, now I added

> If FRAME-OR-WINDOW is nil, rotate the main window of the selected
> frame.
> If FRAME-OR-WINDOW specifies a live frame, rotate the main window of
> that frame.  If FRAME-OR-WINDOW specifies a parent window, rotate that
> window.  In any other case and interactively with a prefix argument
> rotate the parent window of the selected window.
>

Nothing pops out to me, thanks.

>> Flip the windows horizontally as so the layout becomes it's
>> horizontal reflection.
>
> should be elaborated as well.  Something like the windows on top move
> to the bottom and vice-versa.

I'm not fan of these usually, makes the function seem less generic than
it is, but I'll go with it.

> Then I misunderstood and you should probably call it RESIZE.  But "the
> size argument is converted" should probably become "the SIDE argument
> is converted".

Nono, I messed it up by adding the non- to the nil.

>
> Our next task will then be to write the documentation of all commands
> for the Elisp manual and we can do a more thorough explanation there.

Ah so after 3(or 4?) months of ~1 email a day, we finished the code.
Thanks a lot for your patiant replies, without them I'd have given up in
a couple of days.

As you can probably tell by now, I'm not good at writing documentation,
I'd prefer not to do this.

> There I'd like to show parent windows as in
>
>      ______________________________________
>     | ______  ____________________________ |
>     ||      || __________________________ ||
>     ||      |||                          |||
>     ||      |||                          |||
>     ||      |||                          |||
>     ||      |||____________W4____________|||
>     ||      || __________________________ ||
>     ||      |||                          |||
>     ||      |||                          |||
>     ||      |||____________W5____________|||
>     ||__W2__||_____________W3_____________ |
>     |__________________W1__________________|
>
>
> (where W1 and W3 are parent windows) and show what rotating,
> transposing
> and flipping the layouts does.

I had to look for a good 10 seconds before I understood was going on.
We are introducing complex concepts like 'internal windows' to users who
don't car about internals, but just want to see some ascii of how
it works.

I belive we should seperate what we show users and hackers, and just add
a diagram of the form (or similar):

+----+-------+
| W1 |___W2__|
|    |   W3  |
+----+-------+

And as for the 1% of users who care about internals, we just show them
the window-tree pre and post tree to show them internal windows remain same,
I don't see another point of having internal windows cluttering up the diagram