At 08:46 AM 7/21/99 -0700, Karl M. Hegbloom wrote:
Maybe if the tabs where on window configurations, rather than on
buffers... Isn't that what Ben's way of doing it would provide?
Each tab's area could be like a frame is now, with its own window
config stack and window stacking order. It would be another thing on
the list of `console', `device', `frame', `window', `buffer'.
^
`tab'
I think this would be way ugly and an even worse visual metphor than Ben
and Bill are complaining about. Redisplay currently considers toolbar +
window + modeline + minibuffer as a whole from the toolkit perspective. So
tabbing this would mean you would get the toolbar etc inside the tabs -
very wierd IMHO. Also what do you do with split windows - again this breaks
the metaphor. If you tab on a per-window basis, a) you have to change
redisplay a lot b) what do you do about split windows.
I think leaving the tab area of control slightly ambiguous actualy *helps*
in our rather strange XEmacs environment.
You could put other things besides text windows inside the tab's
area
then also, I suppose. An `xdvi' subwindow might be neat...
This will be doable eventually anyway. You will eventually be able to embed
image instances inside others so that you could put subwindows inside tabs,
or anything you like.
The tabs need to have keyboard accelerators too obviously. I imagine
that's either already there or planned.
Sure. The code is semi-there its a matter of wiring it all up. I'm hoping
that as a we approach crtical mass, others will tweak the X-side to get it
looking and behaving correctly.
andy
--------------------------------------------------------------
Dr Andy Piper
Senior Consultant Architect, BEA Systems Ltd