Re: Food for thought: Why (and how) should KDE and Gnome unite?

[Adam Rotaru <arotaru cs sfu ca>]

   Hidy,

On 23 Dec 1998, Tero Pulkkinen wrote:

> If we want KDE and Gnome interoperate, the following things must happen:
> 1) Set of libraries must be introduced that are independent of the
>    other Gnome or KDE things, especially widget sets. These libraries
>    must have corba interface, so that our existing common ground (IIOP)
>    can be utilized -- access outside corba interfaces to these libraries
>    is banned.

  Wow! Quite a bold requirement. But it's quite logical.
Yes, only widget-independent libraries have a chance to become/survive as
environment-independent.  An example I can imagine is a global
configuration library, for reading/writing config files regarless to where
they are.


> 2) Web pages must be created and published that has corba interfaces
>    that are independent of the other parts of the environment.
>    (no dependencies to the widget sets from the interface, nor its
>    initial implementation) This allows creation of applications that
>    are independent of the environment it runs on.

  As I understand, the CORBA parts are not 100% functional in neither
platforms yet. Hopefully, the mico and ORBit implementations will
understand each other (I'm still skeptical). This should definetly happen.


> I propose the following actions to implement this:
> 1) Start a new cvs repository, independent of the KDE or gnome
>    trees. (its requirement that any code placed to that repository
>    is independent of the gnome vs kde split) (a volunteer needed to
>    maintain the cvs repository/provide resources for it)

  Well, I don't have the resources - but maybe I can contribute with my
meaningless emails :)
  Seriously, I'd like to see that happen, but I doubt such code-sharing
will happen in the near future.

> 2) convince both gnome and kde programmers to start depend on interfaces and
>    code in that repository. (so that everyone using kde or gnome must
>    download it)
  Logical.

> 3) move best and most modular pieces of code from gnome and kde cvs
>    repositories to the new cvs repository - co-operation of many
>    authors of gnome and kde modules are needed.
  Yes, co-operation needed, and stepping through boundaries...

> THere's no way widget libraries will merge in the near future. We need to
> have code that does not depend on the widget libraries.
   Agreed.

> If you have or know some gnome or kde module that is (mostly)
> independent of surrounding libraries, post its name to the list.

  Is there any?


  Apart library-sharing, maybe an easier step would be some common
functional specifications, with both environments implementing on their
own. Basic/simple thing, like mime-type bindings.


  well, thanks, and let's see where do the CVSs keep rolling...
    /Adam/