Three different tab implementations

Neil Stevens neil at
Fri Jan 31 14:53:56 GMT 2003

Hash: SHA1

On Friday January 31, 2003 06:50, Lubos Lunak wrote:
> On Friday 31 of January 2003 15:02, Neil Stevens wrote:
> [snip]
> > > 5. This is not really an argument against, I'm just curious. How
> > > exactly would you want to represent several windows that form some
> > > kind of "project" together? Say KDevelop with list of files on the
> > > left, output views at the bottom and other windows for the C++
> > > files? Or KSIRC? Tabs seems to fit here nicely, especially if they
> > > can be undocked and become real toplevel windows. If you convince me
> > > here, the opinion of KWin maintainer could matter in this discussion
> > > :).
> >
> > KSirc now (defaults, not the unfortunate MDI mode) is good by me.  I
> > can move a ksirc window to where I need it. If I want to discuss with
> > one person about some code I'm looking at , I can send that ksirc
> > window over to the desktop with that code.  If I want to monitor more
> > than one channel at once, I can do it.  MDI allows neither.
>  KSirc was a bad example, my mistake, I forgot the list of the users is
> different for each view. How about the KDevelop case?

See other sub-thread.  I'd want something like cervisia, with totally 
indepenent editor windows.

- -- 
Neil Stevens - neil at
"Distinctions by race are so evil, so arbitrary and insidious that a
state bound to defend the equal protection of the laws must not allow
them in any public sphere." -- Thurgood Marshall
Version: GnuPG v1.2.1 (GNU/Linux)


More information about the kde-core-devel mailing list