|
|
| (29 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| <languages />
| | == How to use tables == |
| '''Sites that need to be edited for the release of the new KDE main site'''
| |
|
| |
|
| {| width="100%" border="1" cellpadding="1" cellspacing="1"
| | ===This is a plain table=== |
| | |
| | {| |
| | |One |
| | |Two |
| |- | | |- |
| ! scope="col" | Site
| | |Three |
| ! scope="col" | Info
| | |Four |
| ! scope="col" | Status
| |
| |- | | |- |
| | Community | | |Five |
| | What is the community, how can it be descrbed + link to gettinginvolved | | |Six |
| | missing | | |} |
| | |
| | ===One with borders=== |
| | |
| | {| class="wikitable" |
| | |One |
| | |Two |
| |- | | |- |
| | Events | | |Three |
| | | | |Four |
| | needs porting
| |
| |- | | |- |
| | Talks | | |Five |
| | list of talks with links to material (slides etc) | | |Six |
| | missing | | |} |
| | |
| | ===This is with labels=== |
| | |
| | {| |
| | ! |
| | !One |
| | !Two |
| |- | | |- |
| | Get Involved
| | !More |
| | Original: http://www.kde.org/getinvolved/ | | |Three |
| | done, needs review | | |Four |
| |- | | |- |
| | Donation | | !Again |
| | | | |Five |
| | missing | | |Six |
| | |} |
| | |
| | ===This one can be sorted=== |
| | |
| | {| class="sortable" |
| | |One |
| | |Two |
| |- | | |- |
| | Mailinglist | | |Three |
| | Original: http://www.kde.org/mailinglists/ | | |Four |
| | done, needs review
| |
| |- | | |- |
| | History | | |Five |
| | | | |Six |
| Original: http://www.kde.org/history/
| | |} |
|
| |
|
| (is it really necessary to have all those dev related items there or would it be better to put them onto techbase?) and shouldn't GCDS be listed along with Akademy meets?
| | ===Now all of them combined=== |
|
| |
|
| | needs rewrite | | {| class="wikitable sortable" |
| | ! |
| | !One |
| | !Two |
| |- | | |- |
| | Press Releases
| | !More |
| | Original: http://www.kde.org/presspage/ | | |Three |
| | done, needs review | | |Four |
| |- | | |- |
| | Workspaces
| | !Again |
| | http://www-devel.kde.org/workspaces/
| | |Five |
| | done, needs review
| | |Six |
| |-
| |
| | Plasma Desktop
| |
| |
| |
| | missing
| |
| |-
| |
| | Plasma Netbook
| |
| |
| |
| | missing
| |
| |-
| |
| | Plasma Mobile (??)
| |
| |
| |
| | missing
| |
| |-
| |
| | Applications
| |
| |
| |
| | automatically (?)
| |
| |-
| |
| | Developer Platform
| |
| |
| |
| | in progress: [http://techbase.kde.org/User:Dhillonv10 dhillonv10]
| |
| |-
| |
| | Howtos
| |
| |
| |
| | xbase links
| |
| |-
| |
| | IDE
| |
| |
| |
| | in progress: [http://techbase.kde.org/User:Dhillonv10 dhillonv10]
| |
| |-
| |
| | SDK
| |
| |
| |
| | in progress: [http://techbase.kde.org/User:Dhillonv10 dhillonv10]
| |
| |-
| |
| | Case Studies
| |
| |
| |
| | missing
| |
| |-
| |
| | Support
| |
| | Original: http://www.kde.org/support/ | |
| | done, needs review | |
| |} | | |} |
|
| |
|
| <br>
| | == Fonts and Boxes == |
| | |
| Most pages can be ported from the old site as-is and are marked with "done, needs review". Links are noted.
| |
| | |
| Some are already included in the testing area, which can be found on http://www-devel.kde.org/community/ (starting at a subdir as the main page is a different matter).
| |
| | |
| To make it easy all i would need is a plain txt file, html tags can be applied afterwards.
| |
| | |
| * One
| |
| * Two
| |
| ** Two point one
| |
| * Three
| |
| | |
| <translate>
| |
| === Der Aufruf einer D-Bus Methode === | |
| Eine [http://doc.qt.nokia.com/latest/QDBusMessage.html QDBusMessage] kann direkt mit der statischen Methode [http://doc.qt.nokia.com/latest/QDBusMessage.html QDBusMessage]<tt>::createMethodCall( const QString & service, const QString & path, const QString & interface, const QString & method )</tt> benutzt werden, um Methoden in D-Bus Diensten aufzurufen. Der Rückgabewert ist ein [http://doc.qt.nokia.com/latest/QDBusMessage.html QDBusMessage] Objekt, welches dann für den eigentlichen Aufruf benutzt wird.
| |
| | |
| Der <tt>interface</tt> Parameter ist optional und nur erforderlich, wenn die Methode nicht eindeutig identifizierbar im, mit dem Pfad assoziierten, Objekt ist.Dies kann passieren, wenn das Objekt mehrere Schnittstellen implementiert, die Methoden, mit den gleichen Namen haben. In solchen (seltenen) Fällen, gibt es keine Garantie darüber, welche Methode tatsächlich aufgerufen wird, wenn man die gewünschte Schnittstelle nicht explizit definiert. Allerdings kann man in der Regel einfach eine leere Zeichenfolge (z.B. ""), als Argument für <tt>interface</tt> übergeben.
| |
|
| |
|
| Als Beispiel für den Zugriff auf einen Dienst der (fiktiven) <tt>ping</tt>-Methode für das {{path|/network}} object in der <tt>org.foo.bar</tt>, könnte man dies zu tun:
| | <blockquote> This is a blockquote </blockquote> |
| | <em>This is an em </em> |
|
| |
|
| <code cppqt>
| | = Header1 = |
| QDBusMessage m = QDBusMessage::createMethodCall("org.foo.bar",
| |
| "/network",
| |
| "",
| |
| "ping");
| |
| bool queued = QDBusConnection::sessionBus().send(m);
| |
| </code>
| |
|
| |
|
| In Zeile 5 im obigen Beispiel haben wir die Nachrichten-Warteschlange für das Senden über den aktuelle Session-Bus. Der Rückgabewert vom Typ <tt>bool</tt> lässt uns wissen, ob das Einstellen in die Warteschlange erfolgreich war, oder nicht.
| | Lorem ipsum |
|
| |
|
| Dies lässt noch zwei Fragen offen:
| | ==Header2== |
| * Wie werden die Parameter für einen Methodenaufruf korrekt gesetzt?
| | Lorem ipsum |
| * Wie kommt man an die Rückmeldung im Falle der D-Bus-Methoden, die einen Rückgabewert haben?
| | ===Header3=== |
| </translate>
| | Lorem ipsum |
| | ====Header4==== |
| | Lorem ipsum |
| | =====Header5===== |
| | Lorem ipsum |
| | ======Header6====== |
| | Lorem ipsum |
