KDE-CVS-Digest for June 20, 2003

As Androgynous Howard already described, it doesn't work like this, since it really look more like this (in a single inheritance case, let's not talk about MI :-) ):

struct Foo
{
Foo_vtable* vptr;
int data1;
int data2;
//..
}

struct Foo_vtable
{
int base_offset;
someFunctionPtr1 typeID;
someFunctionPtr2 virtualFunc1;
someFunctionPtr2 virtualFunc2;
...
}

Adding more virtuals becomes a problem when there is a class that inherited off
the base and added a new one. The traditional way of doing that would be for
the child to create a virtual table that has additional slots at the end. If the
parent puts something else in these locations, funny stuff happens, of course..

The size issue of course exists if you add more data members.
But it can also exist even when the allocation size of the object doesn't change.

Consider this:

struct Base
{
char v1;
char v2;
char v3;
};

Here, sizeof(Base) == 4 on most platforms due to alignment/padding. So can you safely add a char v4, since it'd still allocate 4 bytes? Nope.

If you had a
struct Child: public Base
{
char c1;
};

Many C++ implementations (I believe including g++-3.x) would pack the
new value into the padding of the parent class, so making the base class use it
is not a very good idea...

Anyway, the point of all this:
Most (all?) C++ ABIs are designed for performance, at the expense of making binary compatibility difficult. Therefore there are generally no easy answers --
just a lot of discipline plus some tricks...

Since KDE is C++, and C++ doesn't really allow this (because of virtual function tables, etc), it would be difficult to do this. But, another language, objective-C, does this quite nicely, using messages for doing method calls. The way a message works is through a proxy function, which just browses the object's message table, and calls the right method. It's pretty cool, just check it out at apple's site. IMHO it's much better than C++.

http://women.kde.org has its own design and will not be ported to the new one.
For the other sites you list, very often webmasters are also developers and they cannot find time to port the website. I guess the dot has always had a style different from www.kde.org
I suggest that when you are available again (in 2 months), you cvs co the www module, you subscribe to the kde-www mailing list and you port those websites locally. Then you can make a tarball and send it to someone from the mailing list.
:-)
In my opinion, events and promo must be the first to be ported.

The +/- keys are indeed shared between all apps using the treeview control. The problem was that in cervisia, + and - were overridden to perform other functions, and therefore could not be used to expand and collapse the tree. These other functions were now remapped to the Ins/Del keys, so that +/- are again available for expanding/collapsing the tree.