Hello Tiago,
Tiago Vignatti is wrote:
>I agree with you that we must reuse some components in the various
>technologies (UNO, QtDBUS, etc..) to deliver interoperability among
>applications but I'm afraid that we must "move down the stack" a
>little.
>
>For instance, how a developer of KDE, GNOME, Mozilla or other would not
>change some component technology if a low level application changes (say
>some API inside X server)?
Although I can't understand your fear completely,
I write under my understanding.
The API inside X servers is not related.
The component technologies have to be changed to some extent for
realizing interoperability.
The application developers may have to change the code a little.
But, almost all change will be limitted in the component technologies.
>In my conception only if we have a steady
>graphical architecture interface in Linux we can start something like
>the Common Desktop Infrastructure development platform to connect the
>existing components/protocols.
You mean embedded UI?
If so, there is XEMBED Protocol Specification.
But, I heard that it is very limited.
Perhaps, we have to discuss about embedded UI specification.
It is quite interesting.
Regards,
--
Daisuke Kameda
Japan KDE Users' Group: President
mailto:[EMAIL PROTECTED] http://www.kde.gr.jp/~daisuke/
immodule for Qt Project: Project Maintainer
http://www.freedesktop.org/wiki/Software_2fimmodule_2dqt
SMG Co., Ltd.: Engineering Creator
mailto:[EMAIL PROTECTED] http://www.smg.co.jp/
http://www.smg.co.jp/opensource/CommonDesktopInfrastructure/
_______________________________________________
Desktop_architects mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/desktop_architects
