Re: Infrastructural complexity.

[Thomas Lord]

On Sun, 2009-07-26 at 17:14 +0200, martin rudalics wrote:

> We'd still have to specify such objects (I suppose they would get first
> class rating like buffers or windows)

They are frames.  Frames are modified to have a 
`parent' slot which may be nil or may be a
frame that itself has a nil `parent'.



>  decide how they are allowed to
> tile a frame 

Yes.  I have one possibility that seems to cover
all of the use cases people commonly want, but
there are other ways to do it, certainly.


> (which would be mostly a copy of the window making,
> splitting, and deleting code) 

Maybe.  There are other possibilities.  
It could also be done with something like
the layout engines found in some GUI 
toolkits.


> and provide some hooks for the window
> management code to work (alternatively?)
> within a framelet or a frame.


It's not clear that much or any changes to
window code would be needed.  Perhaps 
some changes to `display-buffer';  perhaps
some changes to `buffer-list' that kind
of thing.  These would be ways for an elisp
program to limit which buffers are likely to
be displayed in framelets that are used as control 
panels.

-t






> martin