Zack Rusin wrote:
> Yeah, it's great but it still doesn't work with some mimetypes. To try=20
> it go over to www.kernel.org and click on one of the changelogs, in=20
> fact try to open any link containing a reference to a simple txt=20
> document in a new tab. I just compiled kdelibs and kdebase and I get an=20
> error box when I click on any link referencing anything else than a=20
> html page, the error box says=20
> "Could not create view for text/plain
> The diagnostics is:"

I don't get that over here, for me it works just as excpected.  Maybe its=20
something else thats causing the problem.  However, I do have a build from=
=20
about a week and a half a ago (except for konqueror which is new).

> Doug do you have time to look into it or do you want me to take the=20
> honors? :) Oh, and as always on Saturday afternoon, I did something=20
> completely useless and added a custom paintEvent to KonqTabBar to add a=20
> custom widget to close the tabs since right clicking and picking a menu=20
> item was a little cumbersome. For now it looks super corny, since I=20
> only cared about getting the basic functionality there, so it's just a=20
> plain button, without anything on it (probably it'd be a good idea to=20
> draw there the same widget KWin draws for the close window button) and=20
> looks like this:
> http://vortex.bd.psu.edu/~mus11/img/konq1.png

Great work, I think it looks really good personally!  And I think having it=
=20
the same as KWin is a good idea too.  One question, what happens when the t=
ab=20
bar gets too wide, does it play well with those little scroll arrow thingie=
s?

> Should I add this to 3.2 features list, or does anyone think that=20
> there's a better/cleaner way of doing this (close button on every tab?=20
> close button somewhere on the frame? something even weirder than the=20
> last two?)

I think this is the best way to do it.  I've used it a lot on mozilla and I=
've=20
always liked it.