(→DCOP and D-BUS) |
(add link to our own very good D-Bus tutorials) |
||
Line 15: | Line 15: | ||
*[http://www-106.ibm.com/developerworks/linux/library/l-dcop/index.html?ca=dgr-kdeml01KDEDCOP Connect KDE applications using DCOP]<br />''IBM DeveloperWorks tutorial, shows how to use kdcop and dcop with several examples such as instantly messaging a contact in kopete when he comes online, and also how to create a simple DCOP-aware application.'' | *[http://www-106.ibm.com/developerworks/linux/library/l-dcop/index.html?ca=dgr-kdeml01KDEDCOP Connect KDE applications using DCOP]<br />''IBM DeveloperWorks tutorial, shows how to use kdcop and dcop with several examples such as instantly messaging a contact in kopete when he comes online, and also how to create a simple DCOP-aware application.'' | ||
D-Bus will be the message bus used in KDE 4. | D-Bus will be the message bus used in KDE 4. | ||
− | *[ | + | *[[Development/Tutorials#D-Bus|D-Bus Tutorials]]<br/>''This tutorials show what D-Bus is and how to use it.''<br/>See also: [http://dbus.freedesktop.org/doc/dbus-tutorial.html D-Bus tutorial] at freedesktop.org. |
=== KIO-Slaves === | === KIO-Slaves === |
D-Bus will be the message bus used in KDE 4.
KDE is network transparent. This means that each application can access files via many network protocols just as if they were stored locally. There exist access modules (KIO-Slaves) for Samba (Windows Shares), HTTP, FTP and many other protocols.
KDE actively supports The Portland Project aiming at making cross-desktop application development easier. For more information on this fairly young project, please refer to The Portland Project's website hosted on Freedesktop.org.