http://techbase.kde.org/api.php?action=feedcontributions&user=Danimo&feedformat=atomKDE TechBase - User contributions [en]2013-05-18T17:51:03ZUser contributionsMediaWiki 1.20.2http://techbase.kde.org/User_talk:DhaumannUser talk:Dhaumann2011-02-22T06:33:33Z<p>Danimo: Reverted edits by Koko351152 (Talk) to last version by Karel</p>
<hr />
<div>Its fine to delete the kdesvn-build page. I will merge my content into the existing page. Also, I will also modify the link from the Getting Started page to point to the existing kdesvn-build page.<br />
[[User:Kunalthakar|Kunalthakar]] 19:51, 7 November 2007 (CET)<br />
<br />
== Please block ==<br />
User:38 buy tribulus<br />
and make me an administrator, thanks! --[[User:Tstaerk|Tstaerk]] 11:52, 12 July 2009 (UTC)<br />
<br />
== Title Translation ==<br />
<br />
Hi guy !!!<br />
I would like to know if menu bar translation is possible... If true, how could I do this?<br />
Thank you...<br />
<br />
:You can use the template <nowiki>{{DISPLAYTITLE:foo}}</nowiki>, where 'foo' is the translation. However, the display title reflects the wiki link, that's why a text "link to this page as <nowiki>[[...]]</nowiki>" will appear then. --[[User:Dhaumann|Dhaumann]] 15:40, 18 June 2007 (CEST)<br />
<br />
::Actually not, I have hidden that text with display:none for on-screen printing. One bug though: When using DISPLAYTITLE, the <title> tag is not filled for some reason... --[[User:Danimo|Danimo]] 16:33, 18 June 2007 (CEST)<br />
<br />
:::Damn... If you need help with this, you can ask me as you want for help... ;) --[[User:Fatalerrors|Fatalerrors]] 10:52, 20 June 2007 (CEST)<br />
<br />
----<br />
<br />
Hi, Dhaumann, can you read and write Chinese? Cool! --[[User:Liangqi|Liangqi]] 23:00, 18 June 2007 (CEST)<br />
<br />
: Unfortunately no. I can't read nor write it. But I still try my best to fix links in a language where I mostly see squares :-) --[[User:Dhaumann|Dhaumann]] 23:22, 18 June 2007 (CEST)<br />
<br />
:: I see, I had found it in the diff. Thanks. I had mentioned this link problem in our mailing list. --[[User:Liangqi|Liangqi]] 11:36, 20 June 2007 (CEST)<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
== Sorting in feature list ==<br />
<br />
Why did you manually move (to sort) the stuff in the feature list?<br />
It totally breaks the history... :(<br />
<br />
IMHO it should had been some kind of automatic sorting... or this sadly proves once again the old system was quite better..<br />
<br />
--[[user:Pino|pino]] 11:32, 17 March 2008 (CET)<br />
<br />
== Do me a favour... ==<br />
<br />
Could you somehow take care of [[Development/Tutorials/Phonon/Introduction]]? It's in no usable state and I would recommend deleting it, and rather directly point a link to the API. I'm asking here, cause you once moved the page. --[[Special:Contributions/88.66.153.231|88.66.153.231]] 00:44, 3 June 2008 (CEST)<br />
<br />
== Wiki Structure - sub-pages ==<br />
<br />
The example [[Help:Wiki_Structure#Sub-pages|here]] is not valid anymore (or at least there's nothing like that "on the very top of the page"). What's better to do with it? Thanks.<br />
<br />
: True, will investigate. --dhaumann<br />
<br />
{{Excellent|2009-06-28}}<br />
<br />
== sub pages ==<br />
<br />
I'm wanting to move pages out of sub pages because It is very difficult to write wiki links and remember where everything is, also I would set up categories before moving the pages, I'm telling / asking you because I think I saw a note asking people to use sub pages, and I do think there are times for them, I just note that categorizing wiki pages by sub page defeats some of the usefulness of wiki's... subpages are most appropriate for version specific content, would like to discuss, contact info is on my user page --[[User:AaronPeterson|AaronPeterson]] 09:31, 29 July 2010 (UTC)<br />
<br />
== new page submission? ==<br />
<br />
Hi, I could not really determine where I could submit my new page for review: http://techbase.kde.org/User:Karel/EasyStartDevelopmentOnDebian<br />
So I decided to submit it here :) Is this article good enough to be move to the tutorials section somewhere? Thanks for the review!</div>Danimohttp://techbase.kde.org/User_talk:DanimoUser talk:Danimo2011-02-22T06:33:06Z<p>Danimo: Undo revision 57075 by Koko351152 (Talk)</p>
<hr />
<div>==CAPTCHAs that won't go away==<br />
Aseigo [[Talk:Main_Page#Something_wrong_with_the_CAPTCHAs|suggested]] that I ask you about this. Everytime I make an edit, it claims that I am adding a URL, and wants me to do some math. Is it even supposed to do this to registered users? In any case, ''most'' times I am not adding a url at all, and I tire of the systems inordinate appetite for elementary arithmetic. Can this be fixed? Thanks. --[[User:Axiom|Axiom]] 20:27, 28 March 2007 (CEST)<br />
<br />
== <nowiki>{{file}}</nowiki> ==<br />
<br />
As you asked me, I removed all the occurrences of <nowiki>{{file}}</nowiki> with <nowiki>{{path}}</nowiki>, and removed the obsolete template <nowiki>{{file}}</nowiki>. -- [[user:Pino|pino]] 02:16, 29 May 2007 (CEST)<br />
<br />
:There is also a template called <nowiki>{{module}}</nowiki> for KDE modules (kdelibs, kdebase), etc. I initially used path here, too, and thought that's enough. It's not widely used, only by 2 articles. Maybe we should replace it by path again? What do you think? --[[User:Dhaumann|Dhaumann]] 09:14, 29 May 2007 (CEST)<br />
<br />
::I agree. --[[User:Danimo|Danimo]] 09:28, 29 May 2007 (CEST)<br />
<br />
::Or maybe link it to the module page in the apidocs (e.g [http://api.kde.org/4.0-api/kdelibs-apidocs/ kdelibs])? --[[User:Milliams|milliams]] 14:47, 29 May 2007 (CEST)<br />
<br />
:::Good idea, <nowiki>{{kdelibs}}, {{kdebase}}</nowiki> etc... +1 from my side :) --[[User:Dhaumann|Dhaumann]] 15:11, 29 May 2007 (CEST)<br />
<br />
::::Sounds good. Or how about <nowiki>{{module|foo}}</nowiki> linking to http://api.kde.org/4.0-api/foo-apidocs/? I don't know how flexible this method is though? --[[User:Milliams|milliams]] 19:41, 29 May 2007 (CEST)<br />
<br />
:::::+1 on [[User:Milliams|milliams]]' idea --[[user:Pino|pino]] 21:35, 29 May 2007 (CEST)<br />
<br />
<br />
==Assistance needed for new contributor to Techbase==<br />
Hi. My name is Thor, I am a new contributor to KDE and I am looking to provide some help with regard to one of the KDE Games, KTuberling (The Potato dude). I am a Polyglot, and work in many different languages, and I have noticed on issues of KTuberling that even with correct software in place, certain speech selections do not function (Notably; Serbian and Danish). I have been working on these for a while and would like to obtain source code for the Tuberling to try and correct the error. Could you tell me please how I find out who is working on what, and what they are doing to it? Thanks and Regards. [[User:ThunderGod|ThunderGod]] 15:40, 30 December 2007 (CET)<br />
:The best place to find assistance with this is by visiting the #kdegames or #kde-edu channels on irc.freenode.org or by sending an joining the KDE Games mailing list at [https://mail.kde.org/mailman/listinfo/kde-games-devel https://mail.kde.org/mailman/listinfo/kde-games-devel]. I believe tsdgeos (Albert Astals Cid) is the best person to speak to. --[[User:Milliams|milliams]] 17:13, 30 December 2007 (CET)<br />
<br />
== More readable URLs ==<br />
<br />
At the moment all links on this site are in the form [http://techbase.kde.org/index.php?title=Development/Tutorials http://techbase.kde.org/index.php?title=Development/Tutorials]. I think it would make the site much more readable to convert these links into something like [http://techbase.kde.org/Development/Tutorials http://techbase.kde.org/Development/Tutorials]. Now, as you can see, if you click on that link it does indeed work and takes you to the same page (so you've obviously got mod_rewrite working correctly) so the problem is that mediawiki itself isn't formatting it's links to take advantage of this. I think you basically need to do step 2 from [http://www.mediawiki.org/wiki/Manual:Short_URL#Setup_steps here]. --[[User:Milliams|milliams]] 14:53, 18 April 2008 (CEST)<br />
:It seems this is working now. Thanks a lot :) --[[User:Milliams|milliams]] 14:34, 28 April 2008 (CEST)<br />
<br />
== Remove my account ==<br />
<br />
Please remove my account; i'd like to choose another username. Thank you. [[User:Krf|KRF]]<br />
<br />
:Mediawiki has no concept of user account deletion, since that would mess up the history. Just create a new user and add redirects from your current user accounts user page. --[[User:Danimo|Danimo]] 17:55, 20 April 2008 (CEST)<br />
<br />
Okay, would be nice if you could make my username uppercase then... Some database tweaking maybe? ;). No need to answer this, you can remove my entry when you've read it. Thank you anyway. [[User:Krf|KRF]]<br />
<br />
== Hidden search button text in french localized ktechbase==<br />
<br />
When switching ktechbase language to french the button search text is really too small. I have read somewhere that the css file will use fixed width for a while so changing the search button width from 4em to 6em will fix that small issue.<br />
<br />
== The problem with images in article ==<br />
<br />
When adding the existing image file i can't save the whole article.<br> <br />
<br />
Article: http://techbase.kde.org/Projects/Plasma/Plasmoids_(ru)<br> <br />
<br />
Adding image (ex. kickoff.png), typing the code, saving and got "http://techbase.kde.org/index.php?title=Projects/Plasma/Plasmoids_(ru)&amp;action=submit" and&nbsp; a blank page. When i reload a page, i've got old text back, without any changes. Using Firefox 3.0. Can save only the text. What can we do about it? Thanks.<br><br />
<br />
== Where can I post a patch? ==<br />
<br />
My article on building the dependencies for KDE-4.x:<br />
<br />
http://techbase.kde.org/Getting_Started/Build/KDE4/LFS#QCA-2.0.2_.28crypto_add_on_for_Qt.29<br />
<br />
requires a patch for a file that will not build. Is there somewhere on the TechBase site where I can post this? Currently it is linked to my private web site and I would rather not have that.<br />
<br />
[[User:JRT|JRT]] 10:56, 13 September 2009 (UTC)<br />
<br />
== Wiki software revealed ==<br />
<br />
=== Powered by please ===<br />
It would be nice to reveal the software used in the [http://www.mediawiki.org/wiki/Manual:Footer page footer]. [http://techbase.kde.org/skins/common/images/poweredby_mediawiki_88x31.png (with this image)]<br />
<br />
<P STYLE="TEXT-ALIGN: RIGHT" >[http://www.mediawiki.org/wiki/MediaWiki Powered by MediaWiki]<br />
<br />
=== Database configuration bug ===<br />
See e.g. &lt;URL:{{fullurl:złocień}}>:<br />
<BLOCKQUOTE ><br />
<br />
<h4 STYLE="COLOR: BLACK" >Database error</h4><br />
A database query syntax error has occurred.<br />
This may indicate a bug in the software.<br />
The last attempted database query was:<br />
<blockquote><tt>(SQL query hidden)</tt></blockquote><br />
<br />
from within function "<tt>Article::pageData</tt>".<br />
MySQL returned error "<tt>1267: Illegal mix of collations (latin1_bin,IMPLICIT) and (utf8_unicode_ci,COERCIBLE) for operation '=' (localhost)</tt>".<br />
<br />
</BLOCKQUOTE ><br />
<br />
This should never happen, compare &lt;URL:http://www.mediawiki.org/wiki/Z%C5%82ocie%C5%84>. This problem will prevents Wiki for having non-Western-European page names in translations. The most probable cause is a misconfiguration of the database engine; however, it is also worth noting that the current MediaWiki software is [http://lists.wikimedia.org/pipermail/mediawiki-announce/2010-July/000092.html 1.16] whereas you are using 1.14 (from HTML metadata, otherwise unmentioned), so maybe it would be time to upgrade?<br />
<br />
--[[User:Yecril71pl|Yecril71pl]] 15:03, 14 September 2010 (UTC)</div>Danimohttp://techbase.kde.org/User:DanimoUser:Danimo2009-08-01T20:56:14Z<p>Danimo: </p>
<hr />
<div>== Subpages ==<br />
<br />
{{List_subpages}}<br />
<br />
== TODO ==<br />
<br />
* Beautify Subpage titles<br />
<br />
<br />
== Bugs ==<br />
sorry for reporting a bug here; but this seems like as good a place as any :)<br />
When using <nowiki><code cpp></nowiki> tags I noted a bug. Specifically when you use the colon (or other means) to indent it. [[User:Zander|Zander]] 20:39, 9 April 2007 (CEST)<br />
Example code:<br />
<br />
:<code cpp><br />
#include <iostream><br />
#include <QtCore/QDate><br />
#include <zlib.h><br />
</code></div>Danimohttp://techbase.kde.org/Template:ClassTemplate:Class2009-08-01T20:24:28Z<p>Danimo: </p>
<hr />
<div>[http://api.kde.org/classmapper.php?class={{{1}}}&module={{{2|kdelibs}}}&version={{{3|4.x}}} {{{1}}}]<noinclude><br />
=== Usage Examples ===<br />
<br />
* <nowiki>{{class|kcolordialog}}</nowiki> looks for the docs of KColorDialog in kdelibs from KDE trunk.<br />
* <nowiki>{{class|Syndication::Feed|kdepimlibs}}</nowiki> shows optional parameter for lookup in other modules.<br />
* <nowiki>{{class|kcolordialog|kdelibs|3.5}}</nowiki> shows optional parameter to look up the docs in a different version.<br />
<br />
<br />
[[Category:Template]]</noinclude></div>Danimohttp://techbase.kde.org/Development/Tutorials/Using_KActionsDevelopment/Tutorials/Using KActions2009-07-26T12:28:25Z<p>Danimo: Reverted edits by Danimo (Talk) to last version by Sreich</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Development/Tutorials/Using_KActions}}<br />
<br />
{{TutorialBrowser|<br />
<br />
series=Beginner Tutorial|<br />
<br />
name=How To Use KActions and XMLGUI|<br />
<br />
pre=[[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 - KXmlGuiWindow]], Basic XML knowledge|<br />
<br />
next=[[Development/Tutorials/Saving_and_loading|Tutorial 4 - Saving and loading]]| <br />
<br />
reading=None<br />
}}<br />
<br />
==Abstract==<br />
This tutorial introduces the concept of actions. Actions are a unified way of supplying the user with ways to interact with your program.<br />
<br />
For example, if we wanted to let the user of [[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 ]] clear the text box by clicking a button in the toolbar, from an option in the File menu or through a keyboard shortcut, it could all be done with one {{class|KAction}}.<br />
<br />
[[image:introtokdetutorial3.png|frame|center]]<br />
<br />
==KAction==<br />
A {{class|KAction}} is an object which contains all the information about the icon and shortcuts that is associated with a certain action. The action is then connected to a [http://doc.trolltech.com/latest/signalsandslots.html slot] which carries out the work of your action.<br />
<br />
== The Code ==<br />
<br />
===main.cpp===<br />
<code cppqt><br />
#include <KApplication><br />
#include <KAboutData><br />
#include <KCmdLineArgs><br />
<br />
#include "mainwindow.h"<br />
<br />
int main (int argc, char *argv[])<br />
{<br />
KAboutData aboutData( "tutorial3", "tutorial3",<br />
ki18n("Tutorial 3"), "1.0",<br />
ki18n("A simple text area using KAction etc."),<br />
KAboutData::License_GPL,<br />
ki18n("Copyright (c) 2007 Developer") );<br />
KCmdLineArgs::init( argc, argv, &aboutData );<br />
KApplication app;<br />
<br />
MainWindow* window = new MainWindow();<br />
window->show();<br />
return app.exec();<br />
}<br />
</code><br />
This time, very little has changed in <tt>main.cpp</tt>, only the KAboutData constructor has been updated to show that we are now on tutorial 3.<br />
<br />
===mainwindow.h===<br />
<code cppqt><br />
#ifndef MAINWINDOW_H<br />
#define MAINWINDOW_H<br />
<br />
#include <KXmlGuiWindow><br />
#include <KTextEdit><br />
<br />
class MainWindow : public KXmlGuiWindow<br />
{<br />
public:<br />
MainWindow(QWidget *parent=0);<br />
<br />
private:<br />
KTextEdit* textArea;<br />
void setupActions();<br />
};<br />
<br />
#endif<br />
</code><br />
Only a function <tt>void setupActions()</tt> has been added which will do all the work setting up the KActions.<br />
<br />
===mainwindow.cpp===<br />
<code cppqt><br />
#include "mainwindow.h"<br />
<br />
#include <KApplication><br />
#include <KAction><br />
#include <KLocale><br />
#include <KActionCollection><br />
#include <KStandardAction><br />
<br />
MainWindow::MainWindow(QWidget *parent)<br />
: KXmlGuiWindow(parent)<br />
{<br />
textArea = new KTextEdit;<br />
setCentralWidget(textArea);<br />
<br />
setupActions();<br />
}<br />
<br />
void MainWindow::setupActions()<br />
{<br />
KAction* clearAction = new KAction(this);<br />
clearAction->setText(i18n("Clear"));<br />
clearAction->setIcon(KIcon("document-new"));<br />
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);<br />
actionCollection()->addAction("clear", clearAction);<br />
connect(clearAction, SIGNAL(triggered(bool)),<br />
textArea, SLOT(clear()));<br />
<br />
KStandardAction::quit(kapp, SLOT(quit()),<br />
actionCollection());<br />
<br />
setupGUI();<br />
}<br />
</code><br />
<br />
==Explanation==<br />
This builds upon the KXmlGuiWindow code from [[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2]]. Most of the changes are to <tt>mainwindow.cpp</tt>, an important structural change being that the constructor for MainWindow now calls <tt>setupActions()</tt> instead of <tt>setupGUI()</tt>. <tt>setupActions()</tt> is where the new KAction code goes before finally calling <tt>setupGUI()</tt> itself.<br />
<br />
===Creating the KAction object===<br />
The KAction is built up in a number of steps. The first is including the <tt>KAction</tt> library and then creating the KAction:<br />
<code cppqt><br />
#include <KAction><br />
...<br />
KAction* clearAction = new KAction(this);<br />
</code><br />
This creates a new KAction called <tt>clearAction</tt>.<br />
<br />
===Setting KAction Properties===<br />
====Text====<br />
Now we have our KAction object, we can start setting its properties. The following code sets the text that will be displayed in the menu and under the <tt>KAction</tt>'s icon in the toolbar.<br />
<code cppqt>clearAction->setText(i18n("Clear"));</code><br />
Note that the text is passed through the i18n() function; this is necessary for the UI to be translatable (more information on this can be found in the [[Development/Tutorials/Localization/i18n|i18n tutorial]]).<br />
<br />
====Icon====<br />
If the action is going to be displayed in a toolbar, it's nice to have an icon depicting the action. The following code sets the icon to the standard KDE <tt>document-new</tt> icon through the use of the <tt>setIcon()</tt> function:<br />
<code cppqt>clearAction->setIcon(KIcon("document-new"));</code><br />
<br />
====Keyboard Shortcut====<br />
Setting a keyboard shortcut to perform our action is equally simple:<br />
<code cppqt>clearAction->setShortcut(Qt::CTRL + Qt::Key_W);</code><br />
This associates Ctrl+W with the KAction.<br />
<br />
===Adding to the Collection===<br />
In order for the action to be accessed by the XMLGUI framework (explained in depth later) it must be added to the application's ''action collection''. The action collection is accessed via the <tt>actionCollection()</tt> function like this: <br />
<code cppqt><br />
actionCollection()->addAction("clear", clearAction);<br />
</code><br />
Here, the <tt>clearAction</tt> KAction is added to the collection and given a name of ''clear''. This name (''clear'') is used by the XMLGUI framework to refer to the action, ergo, it should not be localized, since it is used internally only.<br />
<br />
====Connecting the action====<br />
Now that the action is fully set up, it needs to be connected to something useful. In this case (because we want to clear the text area), we connect our action to the <tt>clear()</tt> action belonging to a KTextEdit (which, unsurprisingly, clears the KTextEdit)<br />
<code cppqt><br />
connect( clearAction, SIGNAL( triggered(bool) ), <br />
textArea, SLOT( clear() ) );<br />
</code><br />
This is the same as it would be done in Qt with a {{qt|QAction}}.<br />
<br />
===KStandardAction===<br />
<br />
For actions which would likely appear in almost every KDE application such as 'quit', 'save', and 'load' there are pre-created convenience KActions, accessed through [http://api.kde.org/4.0-api/kdelibs-apidocs/kdeui/html/namespaceKStandardAction.html KStandardAction].<br />
<br />
They are very simple to use. Once the library has been included (<tt>#include <KStandardAction></tt>), simply supply it with what you want the function to do and which KActionCollection to add it to. For example:<br />
<code cppqt>KStandardAction::quit(kapp, SLOT(quit()), actionCollection());</code><br />
This creates a KAction with the correct icon, text and shortcut and even adds it to the File menu.<br />
<br />
==Adding the action to menus and toolbars==<br />
At the moment, the new "Clear" action has been created but it hasn't been associated with any menus or toolbars. This is done with a KDE technology called XMLGUI, which does nice things like movable toolbars for you.<br />
<br />
{{note|In a later version of KDE4, XMLGUI, may be replaced with a new framework called liveui. For now, XMLGUI, is the only and correct way to set up the UI.}}<br />
<br />
==XMLGUI==<br />
<br />
The <tt>setupGUI()</tt> function in {{class|KXmlGuiWindow}} depends on the XMLGUI system to construct the GUI, which XMLGUI does by parsing an XML file description of the interface.<br />
<br />
The rule for naming this XML file is <tt>appnameui.rc</tt>, where <tt>appname</tt> is the name you set in {{class|KAboutData}} (in this case, ''tutorial3''). So in our example, the file is called <tt>tutorial3ui.rc</tt>, and is located in the build directory. Where the file will ultimately be placed is handled by CMake.<br />
<br />
''See also'' [http://developer.kde.org/documentation/library/kdeqt/kde3arch/xmlgui.html developer.kde.org] which still provides valid information for KDE4.<br />
<br />
==''appname''ui.rc File==<br />
<br />
Since the description of the UI is defined with XML, the layout must follow strict rules. This tutorial will not go into great depth on this topic, but for more information, see the [[Development/Architecture/KDE4/XMLGUI_Technology|detailed XMLGUI page]] (here is an older tutorial: [http://developer.kde.org/documentation/tutorials/xmlui/preface.html]).<br />
<br />
===tutorial3ui.rc===<br />
<code xml><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<gui name="tutorial3"<br />
version="1"<br />
xmlns="http://www.kde.org/standards/kxmlgui/1.0"<br />
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"<br />
xsi:schemaLocation="http://www.kde.org/standards/kxmlgui/1.0<br />
http://www.kde.org/standards/kxmlgui/1.0/kxmlgui.xsd" ><br />
<br />
<MenuBar><br />
<Menu name="file" ><br />
<Action name="clear" /><br />
</Menu><br />
</MenuBar><br />
<br />
<ToolBar name="mainToolBar" ><br />
<text>Main Toolbar</text><br />
<Action name="clear" /><br />
</ToolBar><br />
<br />
</gui><br />
</code><br />
<br />
The <tt><Toolbar></tt> tag allows you to describe the toolbar, which is the bar across the top of the window normally with icons. Here it is given the unique name ''mainToolBar'' and its user visible name set to ''Main Toolbar'' using the <tt><text></tt> tag. The clear action is added to the toolbar using the <tt><Action></tt> tag, the name parameter in this tag being the string that was passed to the KActionCollection with <tt>addAction()</tt> in <tt>mainwindow.cpp</tt>.<br />
<br />
Besides having the action in the toolbar, it can also be added to the menubar. Here the action is being added to the ''File'' menu of the <tt>MenuBar</tt> the same way it was added to the toolbar.<br />
<br />
Change the 'version' attribute of the <tt><nowiki><gui></nowiki></tt> tag if you changed .rc file since the last install to force a system cache update. Be sure it is an integer, if you use a decimal value, it will not work, but will not notify that it didn't.<br />
<br />
Some notes on the interaction between code and the .rc file: Menus appear automatically and should have a <tt><nowiki><text/></nowiki></tt> child tag unless they refer to standard menus. Actions need to be created manually and inserted into the actionCollection() using the name in the .rc file. Actions can be hidden or disabled, whereas menus can't.<br />
<br />
==CMake==<br />
Finally, the <tt>tutorial3ui.rc</tt> needs to go somewhere where KDE can find it (can't just leave it in the source directory!). '''This means the project needs to be installed somewhere.'''<br />
===CMakeLists.txt===<br />
<code ini><br />
project(tutorial3)<br />
<br />
find_package(KDE4 REQUIRED)<br />
include_directories(${KDE4_INCLUDES})<br />
<br />
set(tutorial3_SRCS <br />
main.cpp<br />
mainwindow.cpp<br />
)<br />
<br />
kde4_add_executable(tutorial3 ${tutorial3_SRCS})<br />
<br />
target_link_libraries(tutorial3 ${KDE4_KDEUI_LIBS})<br />
<br />
install(TARGETS tutorial3 DESTINATION ${BIN_INSTALL_DIR})<br />
install(FILES tutorial3ui.rc <br />
DESTINATION ${DATA_INSTALL_DIR}/tutorial3)<br />
</code><br />
<br />
This file is almost identical to the one for tutorial2, but with two extra lines at the end that describe where the files are to be installed. Firstly, the <tt>tutorial3</tt> target is installed to the <tt>BIN_INSTALL_DIR</tt> then the <tt>tutorial3ui.rc</tt> file that describes the layout of the user interface is installed to the application's data directory.<br />
<br />
===Make, Install And Run===<br />
If you don't have write access to where your KDE4 installation directory, you can install it to a folder in your home directory.<br />
<br />
To tell CMake where to install the program, set the <tt>DCMAKE_INSTALL_PREFIX</tt> switch. You probably just want to install it somewhere local for testing (it's probably a bit silly to go to the effort of installing these tutorials to your KDE directory), so the following might be appropriate:<br />
mkdir build && cd build<br />
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME<br />
make install<br />
$HOME/bin/tutorial3<br />
which will create a KDE-like directory structure in your user's home directory directory and will install the executable to {{path|$HOME/bin/tutorial3}}.<br />
<br />
==Moving On==<br />
Now you can move on to [[Development/Tutorials/Saving_and_loading|saving and loading]].<br />
<br />
[[Category:C++]]</div>Danimohttp://techbase.kde.org/Development/Tutorials/Using_KActionsDevelopment/Tutorials/Using KActions2009-07-26T12:28:06Z<p>Danimo: </p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Development/Tutorials/Using_KActions}}<br />
<br />
{{TutorialBrowser|<br />
<br />
series=Beginner Tutorial|<br />
<br />
name=How To Use KActions and XMLGUI|<br />
<br />
pre=[[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 - KXmlGuiWindow]], Basic XML knowledge|<br />
<br />
next=[[Development/Tutorials/Saving_and_loading|Tutorial 4 - Saving and loading]]| <br />
<br />
reading=None<br />
}}<br />
<br />
==Abstract==<br />
This tutorial introduces the concept of actions. Actions are a unified way of supplying the user with ways to interact with your program.<br />
<br />
For example, if we wanted to let the user of [[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2 ]] clear the text box by clicking a button in the toolbar, from an option in the File menu or through a keyboard shortcut, it could all be done with one {{class|KAction}}.<br />
<br />
[[image:introtokdetutorial3.png|frame|center]]<br />
<br />
==KAction==<br />
A {{class|KAction}} is an object which contains all the information about the icon and shortcuts that is associated with a certain action. The action is then connected to a [http://doc.trolltech.com/latest/signalsandslots.html slot] which carries out the work of your action.<br />
<br />
== The Code ==<br />
<br />
===main.cpp===<br />
<code cppqt><br />
#include <KApplication><br />
#include <KAboutData><br />
#include <KCmdLineArgs><br />
<br />
#include "mainwindow.h"<br />
<br />
int main (int argc, char *argv[])<br />
{<br />
KAboutData aboutData( "tutorial3", "tutorial3",<br />
ki18n("Tutorial 3"), "1.0",<br />
ki18n("A simple text area using KAction etc."),<br />
KAboutData::License_GPL,<br />
ki18n("Copyright (c) 2007 Developer") );<br />
KCmdLineArgs::init( argc, argv, &aboutData );<br />
KApplication app;<br />
<br />
MainWindow* window = new MainWindow();<br />
window->show();<br />
return app.exec();<br />
}<br />
</code><br />
This time, very little has changed in <tt>main.cpp</tt>, only the KAboutData constructor has been updated to show that we are now on tutorial 3.<br />
<br />
===mainwindow.h===<br />
<code cppqt><br />
#ifndef MAINWINDOW_H<br />
#define MAINWINDOW_H<br />
<br />
#include <KXmlGuiWindow><br />
#include <KTextEdit><br />
<br />
class MainWindow : public KXmlGuiWindow<br />
{<br />
public:<br />
MainWindow(QWidget *parent=0);<br />
<br />
private:<br />
KTextEdit* textArea;<br />
void setupActions();<br />
};<br />
<br />
#endif<br />
</code><br />
Only a function <tt>void setupActions()</tt> has been added which will do all the work setting up the KActions.<br />
<br />
===mainwindow.cpp===<br />
<code cppqt><br />
#include "mainwindow.h"<br />
<br />
#include <KApplication><br />
#include <KAction><br />
#include <KLocale><br />
#include <KActionCollection><br />
#include <KStandardAction><br />
<br />
MainWindow::MainWindow(QWidget *parent)<br />
: KXmlGuiWindow(parent)<br />
{<br />
textArea = new KTextEdit;<br />
setCentralWidget(textArea);<br />
<br />
setupActions();<br />
}<br />
<br />
void MainWindow::setupActions()<br />
{<br />
KAction* clearAction = new KAction(this);<br />
clearAction->setText(i18n("Clear"));<br />
clearAction->setIcon(KIcon("document-new"));<br />
clearAction->setShortcut(Qt::CTRL + Qt::Key_W);<br />
actionCollection()->addAction("clear", clearAction);<br />
connect(clearAction, SIGNAL(triggered(bool)),<br />
textArea, SLOT(clear()));<br />
<br />
KStandardAction::quit(kapp, SLOT(quit()),<br />
actionCollection());<br />
<br />
setupGUI();<br />
}<br />
</code><br />
<br />
==Explanation==<br />
This builds upon the KXmlGuiWindow code from [[Development/Tutorials/Using_KXmlGuiWindow|Tutorial 2]]. Most of the changes are to <tt>mainwindow.cpp</tt>, an important structural change being that the constructor for MainWindow now calls <tt>setupActions()</tt> instead of <tt>setupGUI()</tt>. <tt>setupActions()</tt> is where the new KAction code goes before finally calling <tt>setupGUI()</tt> itself.<br />
<br />
===Creating the KAction object===<br />
The KAction is built up in a number of steps. The first is including the <tt>KAction</tt> library and then creating the KAction:<br />
<code cppqt><br />
#include <KAction><br />
...<br />
KAction* clearAction = new KAction(this);<br />
</code><br />
This creates a new KAction called <tt>clearAction</tt>.<br />
<br />
===Setting KAction Properties===<br />
====Text====<br />
Now we have our KAction object, we can start setting its properties. The following code sets the text that will be displayed in the menu and under the <tt>KAction</tt>'s icon in the toolbar.<br />
<code cppqt>clearAction->setText(i18n("Clear"));</code><br />
Note that the text is passed through the i18n() function; this is necessary for the UI to be translatable (more information on this can be found in the [[Development/Tutorials/Localization/i18n|i18n tutorial]]).<br />
<br />
====Icon====<br />
If the action is going to be displayed in a toolbar, it's nice to have an icon depicting the action. The following code sets the icon to the standard KDE <tt>document-new</tt> icon through the use of the <tt>setIcon()</tt> function:<br />
<code cppqt>clearAction->setIcon(KIcon("document-new"));</code><br />
<br />
====Keyboard Shortcut====<br />
Setting a keyboard shortcut to perform our action is equally simple:<br />
<code cppqt>clearAction->setShortcut(Qt::CTRL + Qt::Key_W);</code><br />
This associates Ctrl+W with the KAction.<br />
<br />
===Adding to the Collection===<br />
In order for the action to be accessed by the XMLGUI framework (explained in depth later) it must be added to the application's ''action collection''. The action collection is accessed via the <tt>actionCollection()</tt> function like this: <br />
<code cppqt><br />
actionCollection()->addAction("clear", clearAction);<br />
</code><br />
Here, the <tt>clearAction</tt> KAction is added to the collection and given a name of ''clear''. This name (''clear'') is used by the XMLGUI framework to refer to the action, ergo, it should not be localized, since it is used internally only.<br />
<br />
====Connecting the action====<br />
Now that the action is fully set up, it needs to be connected to something useful. In this case (because we want to clear the text area), we connect our action to the <tt>clear()</tt> action belonging to a KTextEdit (which, unsurprisingly, clears the KTextEdit)<br />
<code cppqt><br />
connect( clearAction, SIGNAL( triggered(bool) ), <br />
textArea, SLOT( clear() ) );<br />
</code><br />
This is the same as it would be done in Qt with a {{qt|QAction}}.<br />
<br />
===KStandardAction===<br />
<br />
For actions which would likely appear in almost every KDE application such as 'quit', 'save', and 'load' there are pre-created convenience KActions, accessed through [http://api.kde.org/4.0-api/kdelibs-apidocs/kdeui/html/namespaceKStandardAction.html KStandardAction].<br />
<br />
They are very simple to use. Once the library has been included (<tt>#include <KStandardAction></tt>), simply supply it with what you want the function to do and which KActionCollection to add it to. For example:<br />
<code cppqt>KStandardAction::quit(kapp, SLOT(quit()), actionCollection());</code><br />
This creates a KAction with the correct icon, text and shortcut and even adds it to the File menu.<br />
<br />
==Adding the action to menus and toolbars==<br />
At the moment, the new "Clear" action has been created but it hasn't been associated with any menus or toolbars. This is done with a KDE technology called XMLGUI, which does nice things like movable toolbars for you.<br />
<br />
{{note|In a later version of KDE4, XMLGUI, may be replaced with a new framework called liveui. For now, XMLGUI, is the only and correct way to set up the UI.}}<br />
<br />
==XMLGUI==<br />
<br />
The <tt>setupGUI()</tt> function in {{class|KXmlGuiWindow}} depends on the XMLGUI system to construct the GUI, which XMLGUI does by parsing an XML file description of the interface.<br />
<br />
The rule for naming this XML file is <tt>appnameui.rc</tt>, where <tt>appname</tt> is the name you set in {{class|KAboutData}} (in this case, ''tutorial3''). So in our example, the file is called <tt>tutorial3ui.rc</tt>, and is located in the build directory. Where the file will ultimately be placed is handled by CMake.<br />
<br />
''See also'' [http://developer.kde.org/documentation/library/kdeqt/kde3arch/xmlgui.html developer.kde.org] which still provides valid information for KDE4.<br />
<br />
==''appname''ui.rc File==<br />
<br />
Since the description of the UI is defined with XML, the layout must follow strict rules. This tutorial will not go into great depth on this topic, but for more information, see the [[Development/Architecture/KDE4/XMLGUI_Technology|detailed XMLGUI page]] (here is an older tutorial: [http://developer.kde.org/documentation/tutorials/xmlui/preface.html]).<br />
<br />
===tutorial3ui.rc===<br />
<code xml><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<gui name="tutorial3"<br />
version="1"<br />
xmlns="http://www.kde.org/standards/kxmlgui/1.0"<br />
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"<br />
xsi:schemaLocation="http://www.kde.org/standards/kxmlgui/1.0<br />
http://www.kde.org/standards/kxmlgui/1.0/kxmlgui.xsd" ><br />
<br />
<MenuBar><br />
<Menu name="file" ><br />
<Action name="clear" /><br />
</Menu><br />
</MenuBar><br />
<br />
<ToolBar name="mainToolBar" ><br />
<text>Main Toolbar</text><br />
<Action name="clear" /><br />
</ToolBar><br />
<br />
</gui><br />
</code><br />
<br />
The <tt><Toolbar></tt> tag allows you to describe the toolbar, which is the bar across the top of the window normally with icons. Here it is given the unique name ''mainToolBar'' and its user visible name set to ''Main Toolbar'' using the <tt><text></tt> tag. The clear action is added to the toolbar using the <tt><Action></tt> tag, the name parameter in this tag being the string that was passed to the KActionCollection with <tt>addAction()</tt> in <tt>mainwindow.cpp</tt>.<br />
<br />
Besides having the action in the toolbar, it can also be added to the menubar. Here the action is being added to the ''File'' menu of the <tt>MenuBar</tt> the same way it was added to the toolbar.<br />
<br />
Change the 'version' attribute of the <tt><nowiki><gui></nowiki></tt> tag if you changed .rc file since the last install to force a system cache update. Be sure it is an integer, if you use a decimal value, it will not work, but will not notify that it didn't.<br />
<br />
Some notes on the interaction between code and the .rc file: Menus appear automatically and should have a <tt><nowiki><text/></nowiki></tt> child tag unless they refer to standard menus. Actions need to be created manually and inserted into the actionCollection() using the name in the .rc file. Actions can be hidden or disabled, whereas menus can't.<br />
<br />
==CMake==<br />
Finally, the <tt>tutorial3ui.rc</tt> needs to go somewhere where KDE can find it (can't just leave it in the source directory!). '''This means the project needs to be installed somewhere.'''<br />
===CMakeLists.txt===<br />
<code ini><br />
project(tutorial3)<br />
<br />
find_package(KDE4 REQUIRED)<br />
include_directories(${KDE4_INCLUDES})<br />
<br />
set(tutorial3_SRCS <br />
main.cpp<br />
mainwindow.cpp<br />
)<br />
<br />
kde4_add_executable(tutorial3 ${tutorial3_SRCS})<br />
<br />
target_link_libraries(tutorial3 ${KDE4_KDEUI_LIBS})<br />
<br />
install(TARGETS tutorial3 DESTINATION ${BIN_INSTALL_DIR})<br />
install(FILES tutorial3ui.rc <br />
DESTINATION ${DATA_INSTALL_DIR}/tutorial3)<br />
</code><br />
<br />
This file is almost identical to the one for tutorial2, but with two extra lines at the end that describe where the files are to be installed. Firstly, the <tt>tutorial3</tt> target is installed to the <tt>BIN_INSTALL_DIR</tt> then the <tt>tutorial3ui.rc</tt> file that describes the layout of the user interface is installed to the application's data directory.<br />
<br />
===Make, Install And Run===<br />
If you don't have write access to where your KDE4 installation directory, you can install it to a folder in your home directory.<br />
<br />
To tell CMake where to install the program, set the <tt>DCMAKE_INSTALL_PREFIX</tt> switch. You probably just want to install it somewhere local for testing (it's probably a bit silly to go to the effort of installing these tutorials to your KDE directory), so the following might be appropriate:<br />
mkdir build && cd build<br />
cmake .. -DCMAKE_INSTALL_PREFIX=$HOME<br />
make install<br />
$HOME/bin/tutorial3<br />
which will create a KDE-like directory structure in your user's home directory directory and will install the executable to {{path|$HOME/bin/tutorial3}}.<br />
<br />
==Moving On==<br />
Now you can move on to [[Development/Tutorials/Saving_and_loading|saving and loading]].<br />
<br />
[[Category:C++]]</div>Danimohttp://techbase.kde.org/Template:ImproveTemplate:Improve2009-06-28T10:28:35Z<p>Danimo: add category to improve message</p>
<hr />
<div>{{Warning|<br />
'''This section needs improvements''': Please help us to<br />
''cleanup'' confusing sections and<br />
''fix sections'' which contain a '''todo''' <br />
<!--<remove these comments once ParserFunctions are installed?>{{#if:{{{1|}}} |--> <br /> {{{1|}}} <!--}}--> }}<br />
<noinclude>[[Category:Maintenance Templates]] [[Category:Template]]</noinclude><br />
<br />
[[Category:Improve]]</div>Danimohttp://techbase.kde.org/MediaWiki:Common.js/search.jsMediaWiki:Common.js/search.js2009-05-06T20:56:56Z<p>Danimo: Created page with '//<source lang="JavaScript"> /** Change Special:Search to use a drop-down menu ******************************************************* * * Description: Change Special:Searc...'</p>
<hr />
<div>//<source lang="JavaScript"><br />
<br />
/** Change Special:Search to use a drop-down menu *******************************************************<br />
*<br />
* Description: Change Special:Search to use a drop-down menu, with the default being<br />
* the internal MediaWiki engine<br />
* Created and maintained by: [[User:Gracenotes]]<br />
*/<br />
<br />
function SpecialSearchEnhanced() {<br />
var createOption = function(site, action, mainQ, addQ, addV) {<br />
var opt = document.createElement('option');<br />
opt.appendChild(document.createTextNode(site));<br />
searchEngines.push([action, mainQ, addQ, addV]);<br />
return opt;<br />
}<br />
<br />
if (document.forms['powersearch'])<br />
var searchForm = document.forms['powersearch'];<br />
if (document.forms['search'])<br />
var searchForm = document.forms['search'];<br />
<br />
if (searchForm.lsearchbox) {<br />
var searchBox = searchForm.lsearchbox;<br />
} else {<br />
var searchBox = searchForm.search;<br />
}<br />
var selectBox = document.createElement('select');<br />
selectBox.id = 'searchEngine';<br />
searchForm.onsubmit = function() {<br />
var optSelected = searchEngines[document.getElementById('searchEngine').selectedIndex];<br />
searchForm.action = optSelected[0];<br />
searchBox.name = optSelected[1];<br />
searchForm.title.value = optSelected[3];<br />
searchForm.title.name = optSelected[2];<br />
}<br />
selectBox.appendChild(createOption('MediaWiki search', wgScriptPath + '/index.php', 'search', 'title', 'Special:Search'));<br />
selectBox.appendChild(createOption('Google', 'http://www.google.com/search', 'q', 'sitesearch', 'en.wikipedia.org'));<br />
selectBox.appendChild(createOption('Yahoo', 'http://search.yahoo.com/search', 'p', 'vs', 'en.wikipedia.org'));<br />
selectBox.appendChild(createOption('Windows Live', 'http://search.live.com/results.aspx', 'q', 'q1', 'site:http://en.wikipedia.org'));<br />
selectBox.appendChild(createOption('Wikiwix', 'http://www.wikiwix.com/', 'action', 'lang', 'en'));<br />
selectBox.appendChild(createOption('Exalead', 'http://www.exalead.com/wikipedia/results', 'q', 'language', 'en'));<br />
searchBox.style.marginLeft = '0px';<br />
if (document.getElementById('loadStatus')) {<br />
var lStat = document.getElementById('loadStatus');<br />
} else {<br />
var lStat = searchForm.title;<br />
}<br />
lStat.parentNode.insertBefore(selectBox, lStat);<br />
}<br />
<br />
var searchEngines = [];<br />
addOnloadHook(SpecialSearchEnhanced);<br />
<br />
//</source></div>Danimohttp://techbase.kde.org/MediaWiki:Common.jsMediaWiki:Common.js2009-05-06T20:56:17Z<p>Danimo: </p>
<hr />
<div>/* Any JavaScript here will be loaded for all users on every page load. */<br />
<br />
/*<source lang="javascript">*/<br />
<br />
/* Any JavaScript here will be loaded for all users on every page load. */<br />
<br />
if (wgPageName == "Special:Search") //scripts specific to Special:Search<br />
{<br />
importScript("MediaWiki:Common.js/search.js")<br />
}<br />
<br />
//Overrides the function with the same name in http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/skins/common/wikibits.js<br />
//Fixes a bug: for the sorting order, takes the whole number, not the number before the second comma. <br />
//Also, removes spaces. See [[Help:Sorting]].<br />
function ts_parseFloat(num) {<br />
if (!num) return 0;<br />
num = removeSpaces(num);<br />
num = parseFloat(num.replace(/,/g, ""));<br />
return (isNaN(num) ? 0 : num);<br />
}<br />
<br />
//Keep spaces in "currency" mode, to sort a range "70 to 80" at 70, not 7080<br />
function ts_parseFloat_ks(num) {<br />
if (!num) return 0;<br />
num = parseFloat(num.replace(/,/g, ""));<br />
return (isNaN(num) ? 0 : num);<br />
}<br />
<br />
//Auxiliary function for function ts_resortTable(lnk)<br />
function removeSpaces(string) {<br />
var tstring = "";<br />
string = '' + string;<br />
splitstring = string.split(" ");<br />
for(i = 0; i < splitstring.length; i++)<br />
tstring += splitstring[i];<br />
return tstring;<br />
}<br />
<br />
//Overrides the function with the same name in http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/skins/common/wikibits.js<br />
//Changes the criteria for various sorting modes, see [[Help:Sorting]].<br />
//For easy maintenance the difference with wikibits.js is kept limited to a few lines.<br />
function ts_resortTable(lnk) {<br />
// get the span<br />
var span = lnk.getElementsByTagName('span')[0];<br />
<br />
var td = lnk.parentNode;<br />
var tr = td.parentNode;<br />
var column = td.cellIndex;<br />
<br />
var table = tr.parentNode;<br />
while (table && !(table.tagName && table.tagName.toLowerCase() == 'table'))<br />
table = table.parentNode;<br />
if (!table) return;<br />
<br />
// Work out a type for the column<br />
if (table.rows.length <= 1) return;<br />
<br />
// Skip the first row if that's where the headings are<br />
var rowStart = (table.tHead && table.tHead.rows.length > 0 ? 0 : 1);<br />
<br />
var itm = "";<br />
for (var i = rowStart; i < table.rows.length; i++) {<br />
if (table.rows[i].cells.length > column) {<br />
itm = ts_getInnerText(table.rows[i].cells[column]);<br />
itm = itm.replace(/^[\s\xa0]+/, "").replace(/[\s\xa0]+$/, "");<br />
if (itm != "") break;<br />
}<br />
}<br />
<br />
sortfn = ts_sort_caseinsensitive;<br />
itmns = removeSpaces(itm);<br />
if (itmns.match(/^[\d\.\,\-\+]+\%?$/)) sortfn = ts_sort_numeric;<br />
if (itmns.match(/^[\d\.\,\-\+]+[eE][\d\-\+]+\%?$/)) sortfn = ts_sort_numeric;<br />
if (itmns.match(/^[\d\.\,\-\+]+e[\d\-\+]+\u00d710[\d\-\+]+\%?$/)) sortfn = ts_sort_numeric;<br />
if (itm.match(/^\d\d[\/. -][a-zA-Z]{3}[\/. -]\d\d\d\d$/))<br />
sortfn = ts_sort_date;<br />
if (itm.match(/^\d\d[\/.-]\d\d[\/.-]\d\d\d\d$/))<br />
sortfn = ts_sort_date;<br />
if (itm.match(/^\d\d[\/.-]\d\d[\/.-]\d\d$/))<br />
sortfn = ts_sort_date;<br />
if (itm.match(/^[\u00a3$\u20ac\u00a5]/)) // pound dollar euro yen<br />
sortfn = ts_sort_currency;<br />
if (itm.match(/sm=c$/)) sortfn = ts_sort_currency;<br />
if (itm.match(/sm=d$/)) sortfn = ts_sort_date;<br />
if (itm.match(/sm=n$/)) sortfn = ts_sort_numeric;<br />
<br />
var reverse = (span.getAttribute("sortdir") == 'down');<br />
<br />
var newRows = new Array();<br />
for (var j = rowStart; j < table.rows.length; j++) {<br />
var row = table.rows[j];<br />
var keyText = ts_getInnerText(row.cells[column]);<br />
var oldIndex = (reverse ? -j : j);<br />
<br />
newRows[newRows.length] = new Array(row, keyText, oldIndex);<br />
}<br />
<br />
newRows.sort(sortfn);<br />
<br />
var arrowHTML;<br />
if (reverse) {<br />
arrowHTML = '<img src="'+ ts_image_path + ts_image_down + '" alt="&darr;"/>';<br />
newRows.reverse();<br />
span.setAttribute('sortdir','up');<br />
} else {<br />
arrowHTML = '<img src="'+ ts_image_path + ts_image_up + '" alt="&uarr;"/>';<br />
span.setAttribute('sortdir','down');<br />
}<br />
<br />
// We appendChild rows that already exist to the tbody, so it moves them rather than creating new ones<br />
// don't do sortbottom rows<br />
for (var i = 0; i < newRows.length; i++) {<br />
if ((" "+newRows[i][0].className+" ").indexOf(" sortbottom ") == -1)<br />
table.tBodies[0].appendChild(newRows[i][0]);<br />
}<br />
// do sortbottom rows only<br />
for (var i = 0; i < newRows.length; i++) {<br />
if ((" "+newRows[i][0].className+" ").indexOf(" sortbottom ") != -1)<br />
table.tBodies[0].appendChild(newRows[i][0]);<br />
}<br />
<br />
// Delete any other arrows there may be showing<br />
var spans = getElementsByClassName(tr, "span", "sortarrow");<br />
for (var i = 0; i < spans.length; i++) {<br />
spans[i].innerHTML = '<img src="'+ ts_image_path + ts_image_none + '" alt="&darr;"/>';<br />
}<br />
span.innerHTML = arrowHTML;<br />
<br />
ts_alternate(table); <br />
}<br />
<br />
function ts_dateToSortKey(date) { <br />
// y2k notes: two digit years less than 50 are treated as 20XX, greater than 50 are treated as 19XX<br />
if (date.length > 10) {<br />
switch (date.substr(3,3).toLowerCase()) {<br />
case "jan": var month = "01"; break;<br />
case "feb": var month = "02"; break;<br />
case "mar": var month = "03"; break;<br />
case "apr": var month = "04"; break;<br />
case "may": var month = "05"; break;<br />
case "jun": var month = "06"; break;<br />
case "jul": var month = "07"; break;<br />
case "aug": var month = "08"; break;<br />
case "sep": var month = "09"; break;<br />
case "oct": var month = "10"; break;<br />
case "nov": var month = "11"; break;<br />
case "dec": var month = "12"; break;<br />
// default: var month = "00";<br />
}<br />
return date.substr(7,4)+month+date.substr(0,2);<br />
} else if (date.length == 10) {<br />
return date.substr(6,4)+date.substr(3,2)+date.substr(0,2);<br />
} else if (date.length == 8) {<br />
yr = date.substr(6,2);<br />
if (parseInt(yr) < 50) { <br />
yr = '20'+yr; <br />
} else { <br />
yr = '19'+yr; <br />
}<br />
return yr+date.substr(3,2)+date.substr(0,2);<br />
}<br />
return "00000000";<br />
}<br />
<br />
function ts_sort_currency(a,b) {<br />
var aa = ts_parseFloat_ks(a[1].replace(/[\u00a3$\u20ac\u00a5a-zA-Z]/g,''));<br />
var bb = ts_parseFloat_ks(b[1].replace(/[\u00a3$\u20ac\u00a5a-zA-Z]/g,''));<br />
return (aa != bb ? aa - bb : a[2] - b[2]);<br />
}<br />
<br />
/** Collapsible tables *********************************************************<br />
*<br />
* Description: Allows tables to be collapsed, showing only the header. See<br />
* [[Wikipedia:NavFrame]].<br />
* Maintainer on Wikipedia: [[User:R. Koot]]<br />
*/<br />
<br />
var autoCollapse = 2;<br />
var collapseCaption = "hide";<br />
var expandCaption = "show";<br />
<br />
function hasClass( element, className ) {<br />
var Classes = element.className.split( " " );<br />
for ( var i = 0; i < Classes.length; i++ ) {<br />
if ( Classes[i] == className ) {<br />
return ( true );<br />
}<br />
}<br />
return ( false );<br />
}<br />
<br />
function collapseTable( tableIndex )<br />
{<br />
var Button = document.getElementById( "collapseButton" + tableIndex );<br />
var Table = document.getElementById( "collapsibleTable" + tableIndex );<br />
<br />
if ( !Table || !Button ) {<br />
return false;<br />
}<br />
<br />
var Rows = Table.getElementsByTagName( "tr" ); <br />
<br />
if ( Button.firstChild.data == collapseCaption ) {<br />
for ( var i = 1; i < Rows.length; i++ ) {<br />
Rows[i].style.display = "none";<br />
}<br />
Button.firstChild.data = expandCaption;<br />
} else {<br />
for ( var i = 1; i < Rows.length; i++ ) {<br />
Rows[i].style.display = Rows[0].style.display;<br />
}<br />
Button.firstChild.data = collapseCaption;<br />
}<br />
}<br />
<br />
function createCollapseButtons()<br />
{<br />
var tableIndex = 0;<br />
var NavigationBoxes = new Object();<br />
var Tables = document.getElementsByTagName( "table" );<br />
<br />
for ( var i = 0; i < Tables.length; i++ ) {<br />
if ( hasClass( Tables[i], "collapsible" ) ) {<br />
NavigationBoxes[ tableIndex ] = Tables[i];<br />
Tables[i].setAttribute( "id", "collapsibleTable" + tableIndex );<br />
<br />
var Button = document.createElement( "span" );<br />
var ButtonLink = document.createElement( "a" );<br />
var ButtonText = document.createTextNode( collapseCaption );<br />
<br />
Button.style.styleFloat = "right";<br />
Button.style.cssFloat = "right";<br />
Button.style.fontWeight = "normal";<br />
Button.style.textAlign = "right";<br />
Button.style.width = "6em";<br />
<br />
ButtonLink.setAttribute( "id", "collapseButton" + tableIndex );<br />
ButtonLink.setAttribute( "href", "javascript:collapseTable(" + tableIndex + ");" );<br />
ButtonLink.appendChild( ButtonText );<br />
<br />
Button.appendChild( document.createTextNode( "[" ) );<br />
Button.appendChild( ButtonLink );<br />
Button.appendChild( document.createTextNode( "]" ) );<br />
<br />
var Header = Tables[i].getElementsByTagName( "tr" )[0].getElementsByTagName( "th" )[0];<br />
/* only add button and increment count if there is a header row to work with */<br />
if (Header) {<br />
Header.insertBefore( Button, Header.childNodes[0] );<br />
tableIndex++;<br />
}<br />
}<br />
}<br />
<br />
for ( var i = 0; i < tableIndex; i++ ) {<br />
if ( hasClass( NavigationBoxes[i], "collapsed" ) || ( tableIndex >= autoCollapse && hasClass( NavigationBoxes[i], "autocollapse" ) ) ) {<br />
collapseTable( i );<br />
}<br />
}<br />
}<br />
<br />
addOnloadHook( createCollapseButtons );<br />
<br />
//Shuffle for election candidates<br />
function dshuf(){<br />
var shufsets=new Object()<br />
var rx=new RegExp('dshuf'+'\\s+(dshufset\\d+)', 'i') <br />
var divs=document.getElementsByTagName("div")<br />
for (var i=0; i<divs.length; i++){<br />
if (rx.test(divs[i].className)){<br />
if (typeof shufsets[RegExp.$1]=="undefined"){ <br />
shufsets[RegExp.$1]=new Object() <br />
shufsets[RegExp.$1].inner=[] <br />
shufsets[RegExp.$1].member=[]<br />
}<br />
shufsets[RegExp.$1].inner.push(divs[i].innerHTML) <br />
shufsets[RegExp.$1].member.push(divs[i]) <br />
}<br />
}<br />
for (shufset in shufsets){<br />
shufsets[shufset].inner.sort(function() {return 0.5 - Math.random()})<br />
for (var i=0; i<shufsets[shufset].member.length; i++){<br />
shufsets[shufset].member[i].innerHTML=shufsets[shufset].inner[i]<br />
shufsets[shufset].member[i].style.display="block"<br />
}<br />
}<br />
<br />
}<br />
<br />
addOnloadHook(dshuf);<br />
<br />
/*************<br />
*** AJAX transclusion table <http://meta.wikimedia.org/wiki/User:Pathoschild/Scripts/AJAX_transclusion_table><br />
*** by [[m:user:Pathoschild]]<br />
*************/<br />
function attLoader() {<br />
if(getElementsByClassName(document.getElementsByTagName('body')[0],'table','attable').length) {<br />
document.write('<script type="text/javascript" src="'<br />
+ 'http://meta.wikimedia.org/w/index.php?title=User:Pathoschild/Scripts/AJAX_transclusion_table.js' <br />
+ '&action=raw&ctype=text/javascript&dontcountme=s"></script>');<br />
}<br />
}<br />
addOnloadHook(attLoader);<br />
<br />
/** JSconfig ************<br />
* Global configuration options to enable/disable and configure<br />
* specific script features from [[MediaWiki:Common.js]] and<br />
* [[MediaWiki:Monobook.js]]<br />
* This framework adds config options (saved as cookies) to [[Special:Preferences]]<br />
* For a more permanent change you can override the default settings in your <br />
* [[Special:Mypage/monobook.js]]<br />
* for Example: JSconfig.keys[loadAutoInformationTemplate] = false;<br />
*<br />
* Maintainer: [[User:Dschwen]]<br />
*/<br />
<br />
var JSconfig =<br />
{<br />
prefix : 'jsconfig_',<br />
keys : {},<br />
meta : {},<br />
<br />
//<br />
// Register a new configuration item<br />
// * name : String, internal name<br />
// * default_value : String or Boolean (type determines configuration widget)<br />
// * description : String, text appearing next to the widget in the preferences<br />
// * prefpage : Integer (optional), section in the preferences to insert the widget:<br />
// 0 : User profile<br />
// 1 : Skin<br />
// 2 : Math<br />
// 3 : Files<br />
// 4 : Date and time<br />
// 5 : Editing<br />
// 6 : Recent changes<br />
// 7 : Watchlist<br />
// 8 : Search<br />
// 9 : Misc<br />
//<br />
// Access keys through JSconfig.keys[name]<br />
//<br />
registerKey : function( name, default_value, description, prefpage )<br />
{<br />
if( typeof(JSconfig.keys[name]) == 'undefined' ) <br />
JSconfig.keys[name] = default_value;<br />
else {<br />
<br />
// all cookies are read as strings, <br />
// convert to the type of the default value<br />
switch( typeof(default_value) )<br />
{<br />
case 'boolean' : JSconfig.keys[name] = ( JSconfig.keys[name] == 'true' ); break;<br />
case 'number' : JSconfig.keys[name] = JSconfig.keys[name]/1; break;<br />
}<br />
<br />
}<br />
<br />
JSconfig.meta[name] = { 'description' : description, 'page' : prefpage || 0, 'default_value' : default_value };<br />
},<br />
<br />
readCookies : function()<br />
{<br />
var cookies = document.cookie.split("; ");<br />
var p =JSconfig.prefix.length;<br />
var i;<br />
<br />
for( var key in cookies )<br />
{<br />
if( cookies[key].substring(0,p) == JSconfig.prefix )<br />
{<br />
i = cookies[key].indexOf('=');<br />
//alert( cookies[key] + ',' + key + ',' + cookies[key].substring(p,i) );<br />
JSconfig.keys[cookies[key].substring(p,i)] = cookies[key].substring(i+1);<br />
}<br />
}<br />
},<br />
<br />
writeCookies : function()<br />
{<br />
for( var key in JSconfig.keys )<br />
document.cookie = JSconfig.prefix + key + '=' + JSconfig.keys[key] + '; path=/; expires=Thu, 2 Aug 2009 10:10:10 UTC';<br />
},<br />
<br />
evaluateForm : function()<br />
{<br />
var w_ctrl,wt;<br />
//alert('about to save JSconfig');<br />
for( var key in JSconfig.meta ) {<br />
w_ctrl = document.getElementById( JSconfig.prefix + key )<br />
if( w_ctrl ) <br />
{<br />
wt = typeof( JSconfig.meta[key].default_value );<br />
switch( wt ) {<br />
case 'boolean' : JSconfig.keys[key] = w_ctrl.checked; break;<br />
case 'string' : JSconfig.keys[key] = w_ctrl.value; break;<br />
}<br />
}<br />
}<br />
<br />
JSconfig.writeCookies();<br />
return true;<br />
},<br />
<br />
setUpForm : function()<br />
{ <br />
var prefChild = document.getElementById('preferences');<br />
if( !prefChild ) return;<br />
prefChild = prefChild.childNodes;<br />
<br />
//<br />
// make a list of all preferences sections<br />
//<br />
var tabs = new Array;<br />
var len = prefChild.length;<br />
for( var key = 0; key < len; key++ ) {<br />
if( prefChild[key].tagName &&<br />
prefChild[key].tagName.toLowerCase() == 'fieldset' ) <br />
tabs.push(prefChild[key]);<br />
}<br />
<br />
//<br />
// Create Widgets for all registered config keys<br />
//<br />
var w_div, w_label, w_ctrl, wt;<br />
for( var key in JSconfig.meta ) {<br />
w_div = document.createElement( 'DIV' );<br />
<br />
w_label = document.createElement( 'LABEL' );<br />
w_label.appendChild( document.createTextNode( JSconfig.meta[key].description ) )<br />
w_label.htmlFor = JSconfig.prefix + key;<br />
<br />
wt = typeof( JSconfig.meta[key].default_value );<br />
<br />
w_ctrl = document.createElement( 'INPUT' );<br />
w_ctrl.id = JSconfig.prefix + key;<br />
<br />
// before insertion into the DOM tree<br />
switch( wt ) {<br />
case 'boolean' : w_ctrl.type = 'checkbox'; break;<br />
case 'string' : w_ctrl.type = 'text'; break;<br />
}<br />
<br />
w_div.appendChild( w_label );<br />
w_div.appendChild( w_ctrl );<br />
tabs[JSconfig.meta[key].page].appendChild( w_div );<br />
<br />
// after insertion into the DOM tree<br />
switch( wt ) {<br />
case 'boolean' : w_ctrl.defaultChecked = w_ctrl.checked = JSconfig.keys[key]; break;<br />
case 'string' : w_ctrl.defaultValue = w_ctrl.value = JSconfig.keys[key]; break;<br />
}<br />
<br />
}<br />
addHandler(document.getElementById('preferences').parentNode, 'submit', JSconfig.evaluateForm );<br />
}<br />
}<br />
<br />
JSconfig.readCookies();<br />
addOnloadHook(JSconfig.setUpForm);<br />
<br />
/*</source>*/</div>Danimohttp://techbase.kde.org/MediaWiki:GooglesearchheaderMediaWiki:Googlesearchheader2009-05-06T19:13:11Z<p>Danimo: Created page with '== Try Google Search: =='</p>
<hr />
<div>== Try Google Search: ==</div>Danimohttp://techbase.kde.org/KDE_TechBase:CopyrightsKDE TechBase:Copyrights2009-05-05T21:37:49Z<p>Danimo: </p>
<hr />
<div>If not stated explicitly otherwise on the respective page, the contents of this site is '''dual licensed''' under the [http://www.gnu.org/licenses/fdl.txt GNU Free Documentation License 1.2] and the [http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike License].<br />
<br />
== GNU Free Documentation License ==<br />
<br />
<pre><br />
GNU Free Documentation License<br />
Version 1.2, November 2002<br />
<br />
<br />
Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.<br />
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA<br />
Everyone is permitted to copy and distribute verbatim copies<br />
of this license document, but changing it is not allowed.<br />
<br />
<br />
0. PREAMBLE<br />
<br />
The purpose of this License is to make a manual, textbook, or other<br />
functional and useful document "free" in the sense of freedom: to<br />
assure everyone the effective freedom to copy and redistribute it,<br />
with or without modifying it, either commercially or noncommercially.<br />
Secondarily, this License preserves for the author and publisher a way<br />
to get credit for their work, while not being considered responsible<br />
for modifications made by others.<br />
<br />
This License is a kind of "copyleft", which means that derivative<br />
works of the document must themselves be free in the same sense. It<br />
complements the GNU General Public License, which is a copyleft<br />
license designed for free software.<br />
<br />
We have designed this License in order to use it for manuals for free<br />
software, because free software needs free documentation: a free<br />
program should come with manuals providing the same freedoms that the<br />
software does. But this License is not limited to software manuals;<br />
it can be used for any textual work, regardless of subject matter or<br />
whether it is published as a printed book. We recommend this License<br />
principally for works whose purpose is instruction or reference.<br />
<br />
<br />
1. APPLICABILITY AND DEFINITIONS<br />
<br />
This License applies to any manual or other work, in any medium, that<br />
contains a notice placed by the copyright holder saying it can be<br />
distributed under the terms of this License. Such a notice grants a<br />
world-wide, royalty-free license, unlimited in duration, to use that<br />
work under the conditions stated herein. The "Document", below,<br />
refers to any such manual or work. Any member of the public is a<br />
licensee, and is addressed as "you". You accept the license if you<br />
copy, modify or distribute the work in a way requiring permission<br />
under copyright law.<br />
<br />
A "Modified Version" of the Document means any work containing the<br />
Document or a portion of it, either copied verbatim, or with<br />
modifications and/or translated into another language.<br />
<br />
A "Secondary Section" is a named appendix or a front-matter section of<br />
the Document that deals exclusively with the relationship of the<br />
publishers or authors of the Document to the Document's overall subject<br />
(or to related matters) and contains nothing that could fall directly<br />
within that overall subject. (Thus, if the Document is in part a<br />
textbook of mathematics, a Secondary Section may not explain any<br />
mathematics.) The relationship could be a matter of historical<br />
connection with the subject or with related matters, or of legal,<br />
commercial, philosophical, ethical or political position regarding<br />
them.<br />
<br />
The "Invariant Sections" are certain Secondary Sections whose titles<br />
are designated, as being those of Invariant Sections, in the notice<br />
that says that the Document is released under this License. If a<br />
section does not fit the above definition of Secondary then it is not<br />
allowed to be designated as Invariant. The Document may contain zero<br />
Invariant Sections. If the Document does not identify any Invariant<br />
Sections then there are none.<br />
<br />
The "Cover Texts" are certain short passages of text that are listed,<br />
as Front-Cover Texts or Back-Cover Texts, in the notice that says that<br />
the Document is released under this License. A Front-Cover Text may<br />
be at most 5 words, and a Back-Cover Text may be at most 25 words.<br />
<br />
A "Transparent" copy of the Document means a machine-readable copy,<br />
represented in a format whose specification is available to the<br />
general public, that is suitable for revising the document<br />
straightforwardly with generic text editors or (for images composed of<br />
pixels) generic paint programs or (for drawings) some widely available<br />
drawing editor, and that is suitable for input to text formatters or<br />
for automatic translation to a variety of formats suitable for input<br />
to text formatters. A copy made in an otherwise Transparent file<br />
format whose markup, or absence of markup, has been arranged to thwart<br />
or discourage subsequent modification by readers is not Transparent.<br />
An image format is not Transparent if used for any substantial amount<br />
of text. A copy that is not "Transparent" is called "Opaque".<br />
<br />
Examples of suitable formats for Transparent copies include plain<br />
ASCII without markup, Texinfo input format, LaTeX input format, SGML<br />
or XML using a publicly available DTD, and standard-conforming simple<br />
HTML, PostScript or PDF designed for human modification. Examples of<br />
transparent image formats include PNG, XCF and JPG. Opaque formats<br />
include proprietary formats that can be read and edited only by<br />
proprietary word processors, SGML or XML for which the DTD and/or<br />
processing tools are not generally available, and the<br />
machine-generated HTML, PostScript or PDF produced by some word<br />
processors for output purposes only.<br />
<br />
The "Title Page" means, for a printed book, the title page itself,<br />
plus such following pages as are needed to hold, legibly, the material<br />
this License requires to appear in the title page. For works in<br />
formats which do not have any title page as such, "Title Page" means<br />
the text near the most prominent appearance of the work's title,<br />
preceding the beginning of the body of the text.<br />
<br />
A section "Entitled XYZ" means a named subunit of the Document whose<br />
title either is precisely XYZ or contains XYZ in parentheses following<br />
text that translates XYZ in another language. (Here XYZ stands for a<br />
specific section name mentioned below, such as "Acknowledgements",<br />
"Dedications", "Endorsements", or "History".) To "Preserve the Title"<br />
of such a section when you modify the Document means that it remains a<br />
section "Entitled XYZ" according to this definition.<br />
<br />
The Document may include Warranty Disclaimers next to the notice which<br />
states that this License applies to the Document. These Warranty<br />
Disclaimers are considered to be included by reference in this<br />
License, but only as regards disclaiming warranties: any other<br />
implication that these Warranty Disclaimers may have is void and has<br />
no effect on the meaning of this License.<br />
<br />
<br />
2. VERBATIM COPYING<br />
<br />
You may copy and distribute the Document in any medium, either<br />
commercially or noncommercially, provided that this License, the<br />
copyright notices, and the license notice saying this License applies<br />
to the Document are reproduced in all copies, and that you add no other<br />
conditions whatsoever to those of this License. You may not use<br />
technical measures to obstruct or control the reading or further<br />
copying of the copies you make or distribute. However, you may accept<br />
compensation in exchange for copies. If you distribute a large enough<br />
number of copies you must also follow the conditions in section 3.<br />
<br />
You may also lend copies, under the same conditions stated above, and<br />
you may publicly display copies.<br />
<br />
<br />
3. COPYING IN QUANTITY<br />
<br />
If you publish printed copies (or copies in media that commonly have<br />
printed covers) of the Document, numbering more than 100, and the<br />
Document's license notice requires Cover Texts, you must enclose the<br />
copies in covers that carry, clearly and legibly, all these Cover<br />
Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on<br />
the back cover. Both covers must also clearly and legibly identify<br />
you as the publisher of these copies. The front cover must present<br />
the full title with all words of the title equally prominent and<br />
visible. You may add other material on the covers in addition.<br />
Copying with changes limited to the covers, as long as they preserve<br />
the title of the Document and satisfy these conditions, can be treated<br />
as verbatim copying in other respects.<br />
<br />
If the required texts for either cover are too voluminous to fit<br />
legibly, you should put the first ones listed (as many as fit<br />
reasonably) on the actual cover, and continue the rest onto adjacent<br />
pages.<br />
<br />
If you publish or distribute Opaque copies of the Document numbering<br />
more than 100, you must either include a machine-readable Transparent<br />
copy along with each Opaque copy, or state in or with each Opaque copy<br />
a computer-network location from which the general network-using<br />
public has access to download using public-standard network protocols<br />
a complete Transparent copy of the Document, free of added material.<br />
If you use the latter option, you must take reasonably prudent steps,<br />
when you begin distribution of Opaque copies in quantity, to ensure<br />
that this Transparent copy will remain thus accessible at the stated<br />
location until at least one year after the last time you distribute an<br />
Opaque copy (directly or through your agents or retailers) of that<br />
edition to the public.<br />
<br />
It is requested, but not required, that you contact the authors of the<br />
Document well before redistributing any large number of copies, to give<br />
them a chance to provide you with an updated version of the Document.<br />
<br />
<br />
4. MODIFICATIONS<br />
<br />
You may copy and distribute a Modified Version of the Document under<br />
the conditions of sections 2 and 3 above, provided that you release<br />
the Modified Version under precisely this License, with the Modified<br />
Version filling the role of the Document, thus licensing distribution<br />
and modification of the Modified Version to whoever possesses a copy<br />
of it. In addition, you must do these things in the Modified Version:<br />
<br />
A. Use in the Title Page (and on the covers, if any) a title distinct<br />
from that of the Document, and from those of previous versions<br />
(which should, if there were any, be listed in the History section<br />
of the Document). You may use the same title as a previous version<br />
if the original publisher of that version gives permission.<br />
B. List on the Title Page, as authors, one or more persons or entities<br />
responsible for authorship of the modifications in the Modified<br />
Version, together with at least five of the principal authors of the<br />
Document (all of its principal authors, if it has fewer than five),<br />
unless they release you from this requirement.<br />
C. State on the Title page the name of the publisher of the<br />
Modified Version, as the publisher.<br />
D. Preserve all the copyright notices of the Document.<br />
E. Add an appropriate copyright notice for your modifications<br />
adjacent to the other copyright notices.<br />
F. Include, immediately after the copyright notices, a license notice<br />
giving the public permission to use the Modified Version under the<br />
terms of this License, in the form shown in the Addendum below.<br />
G. Preserve in that license notice the full lists of Invariant Sections<br />
and required Cover Texts given in the Document's license notice.<br />
H. Include an unaltered copy of this License.<br />
I. Preserve the section Entitled "History", Preserve its Title, and add<br />
to it an item stating at least the title, year, new authors, and<br />
publisher of the Modified Version as given on the Title Page. If<br />
there is no section Entitled "History" in the Document, create one<br />
stating the title, year, authors, and publisher of the Document as<br />
given on its Title Page, then add an item describing the Modified<br />
Version as stated in the previous sentence.<br />
J. Preserve the network location, if any, given in the Document for<br />
public access to a Transparent copy of the Document, and likewise<br />
the network locations given in the Document for previous versions<br />
it was based on. These may be placed in the "History" section.<br />
You may omit a network location for a work that was published at<br />
least four years before the Document itself, or if the original<br />
publisher of the version it refers to gives permission.<br />
K. For any section Entitled "Acknowledgements" or "Dedications",<br />
Preserve the Title of the section, and preserve in the section all<br />
the substance and tone of each of the contributor acknowledgements<br />
and/or dedications given therein.<br />
L. Preserve all the Invariant Sections of the Document,<br />
unaltered in their text and in their titles. Section numbers<br />
or the equivalent are not considered part of the section titles.<br />
M. Delete any section Entitled "Endorsements". Such a section<br />
may not be included in the Modified Version.<br />
N. Do not retitle any existing section to be Entitled "Endorsements"<br />
or to conflict in title with any Invariant Section.<br />
O. Preserve any Warranty Disclaimers.<br />
<br />
If the Modified Version includes new front-matter sections or<br />
appendices that qualify as Secondary Sections and contain no material<br />
copied from the Document, you may at your option designate some or all<br />
of these sections as invariant. To do this, add their titles to the<br />
list of Invariant Sections in the Modified Version's license notice.<br />
These titles must be distinct from any other section titles.<br />
<br />
You may add a section Entitled "Endorsements", provided it contains<br />
nothing but endorsements of your Modified Version by various<br />
parties--for example, statements of peer review or that the text has<br />
been approved by an organization as the authoritative definition of a<br />
standard.<br />
<br />
You may add a passage of up to five words as a Front-Cover Text, and a<br />
passage of up to 25 words as a Back-Cover Text, to the end of the list<br />
of Cover Texts in the Modified Version. Only one passage of<br />
Front-Cover Text and one of Back-Cover Text may be added by (or<br />
through arrangements made by) any one entity. If the Document already<br />
includes a cover text for the same cover, previously added by you or<br />
by arrangement made by the same entity you are acting on behalf of,<br />
you may not add another; but you may replace the old one, on explicit<br />
permission from the previous publisher that added the old one.<br />
<br />
The author(s) and publisher(s) of the Document do not by this License<br />
give permission to use their names for publicity for or to assert or<br />
imply endorsement of any Modified Version.<br />
<br />
<br />
5. COMBINING DOCUMENTS<br />
<br />
You may combine the Document with other documents released under this<br />
License, under the terms defined in section 4 above for modified<br />
versions, provided that you include in the combination all of the<br />
Invariant Sections of all of the original documents, unmodified, and<br />
list them all as Invariant Sections of your combined work in its<br />
license notice, and that you preserve all their Warranty Disclaimers.<br />
<br />
The combined work need only contain one copy of this License, and<br />
multiple identical Invariant Sections may be replaced with a single<br />
copy. If there are multiple Invariant Sections with the same name but<br />
different contents, make the title of each such section unique by<br />
adding at the end of it, in parentheses, the name of the original<br />
author or publisher of that section if known, or else a unique number.<br />
Make the same adjustment to the section titles in the list of<br />
Invariant Sections in the license notice of the combined work.<br />
<br />
In the combination, you must combine any sections Entitled "History"<br />
in the various original documents, forming one section Entitled<br />
"History"; likewise combine any sections Entitled "Acknowledgements",<br />
and any sections Entitled "Dedications". You must delete all sections<br />
Entitled "Endorsements".<br />
<br />
<br />
6. COLLECTIONS OF DOCUMENTS<br />
<br />
You may make a collection consisting of the Document and other documents<br />
released under this License, and replace the individual copies of this<br />
License in the various documents with a single copy that is included in<br />
the collection, provided that you follow the rules of this License for<br />
verbatim copying of each of the documents in all other respects.<br />
<br />
You may extract a single document from such a collection, and distribute<br />
it individually under this License, provided you insert a copy of this<br />
License into the extracted document, and follow this License in all<br />
other respects regarding verbatim copying of that document.<br />
<br />
<br />
7. AGGREGATION WITH INDEPENDENT WORKS<br />
<br />
A compilation of the Document or its derivatives with other separate<br />
and independent documents or works, in or on a volume of a storage or<br />
distribution medium, is called an "aggregate" if the copyright<br />
resulting from the compilation is not used to limit the legal rights<br />
of the compilation's users beyond what the individual works permit.<br />
When the Document is included in an aggregate, this License does not<br />
apply to the other works in the aggregate which are not themselves<br />
derivative works of the Document.<br />
<br />
If the Cover Text requirement of section 3 is applicable to these<br />
copies of the Document, then if the Document is less than one half of<br />
the entire aggregate, the Document's Cover Texts may be placed on<br />
covers that bracket the Document within the aggregate, or the<br />
electronic equivalent of covers if the Document is in electronic form.<br />
Otherwise they must appear on printed covers that bracket the whole<br />
aggregate.<br />
<br />
<br />
8. TRANSLATION<br />
<br />
Translation is considered a kind of modification, so you may<br />
distribute translations of the Document under the terms of section 4.<br />
Replacing Invariant Sections with translations requires special<br />
permission from their copyright holders, but you may include<br />
translations of some or all Invariant Sections in addition to the<br />
original versions of these Invariant Sections. You may include a<br />
translation of this License, and all the license notices in the<br />
Document, and any Warranty Disclaimers, provided that you also include<br />
the original English version of this License and the original versions<br />
of those notices and disclaimers. In case of a disagreement between<br />
the translation and the original version of this License or a notice<br />
or disclaimer, the original version will prevail.<br />
<br />
If a section in the Document is Entitled "Acknowledgements",<br />
"Dedications", or "History", the requirement (section 4) to Preserve<br />
its Title (section 1) will typically require changing the actual<br />
title.<br />
<br />
<br />
9. TERMINATION<br />
<br />
You may not copy, modify, sublicense, or distribute the Document except<br />
as expressly provided for under this License. Any other attempt to<br />
copy, modify, sublicense or distribute the Document is void, and will<br />
automatically terminate your rights under this License. However,<br />
parties who have received copies, or rights, from you under this<br />
License will not have their licenses terminated so long as such<br />
parties remain in full compliance.<br />
<br />
<br />
10. FUTURE REVISIONS OF THIS LICENSE<br />
<br />
The Free Software Foundation may publish new, revised versions<br />
of the GNU Free Documentation License from time to time. Such new<br />
versions will be similar in spirit to the present version, but may<br />
differ in detail to address new problems or concerns. See<br />
http://www.gnu.org/copyleft/.<br />
<br />
Each version of the License is given a distinguishing version number.<br />
If the Document specifies that a particular numbered version of this<br />
License "or any later version" applies to it, you have the option of<br />
following the terms and conditions either of that specified version or<br />
of any later version that has been published (not as a draft) by the<br />
Free Software Foundation. If the Document does not specify a version<br />
number of this License, you may choose any version ever published (not<br />
as a draft) by the Free Software Foundation.<br />
<br />
<br />
ADDENDUM: How to use this License for your documents<br />
<br />
To use this License in a document you have written, include a copy of<br />
the License in the document and put the following copyright and<br />
license notices just after the title page:<br />
<br />
Copyright (c) YEAR YOUR NAME.<br />
Permission is granted to copy, distribute and/or modify this document<br />
under the terms of the GNU Free Documentation License, Version 1.2<br />
or any later version published by the Free Software Foundation;<br />
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.<br />
A copy of the license is included in the section entitled "GNU<br />
Free Documentation License".<br />
<br />
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,<br />
replace the "with...Texts." line with this:<br />
<br />
with the Invariant Sections being LIST THEIR TITLES, with the<br />
Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.<br />
<br />
If you have Invariant Sections without Cover Texts, or some other<br />
combination of the three, merge those two alternatives to suit the<br />
situation.<br />
<br />
If your document contains nontrivial examples of program code, we<br />
recommend releasing these examples in parallel under your choice of<br />
free software license, such as the GNU General Public License,<br />
to permit their use in free software.<br />
<br />
</pre></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2009-01-24T19:00:18Z<p>Danimo: Reverted edits by Danimo (Talk) to last version by Dhaumann</p>
<hr />
<div>|- valign=top style="background-color: {{{2|white}}};"<br />
| style="text-align:center; vertical-align:middle; background-color: {{{1|white}}}; width:10px;" | {{{3|status missing}}}<br />
| style="width:10px; vertical-align:middle;" | {{{4|project missing}}}<br />
| style="vertical-align:middle; "| {{{5|description missing}}}<br />
|style="width:10px; vertical-align:middle;" | [mailto:{{{6}}} {{{7|email missing}}} &lt;{{{6}}}&gt;]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2009-01-24T18:59:27Z<p>Danimo: </p>
<hr />
<div>|- valign=top style="background-color: {{{2|white}}};"<br />
| style="text-align:center; vertical-align:middle; background-color: {{{1|white}}}; width:10px;" | {{{3|status missing}}}<br />
| style="width:10px; vertical-align:middle;" | {{{4|project missing}}}<br />
| style="vertical-align:middle; "| {{{5|description missing}}}<br />
|style="width:10px; vertical-align:middle;" | <mail address='{{{6}}}'>{{{7|email missing}}} &lt;{{{6}}}&gt;</mail><br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/StatsStats2008-10-21T16:20:35Z<p>Danimo: </p>
<hr />
<div>== Top 10 contributors of the last week ==<br />
<center>{{Special:ContributionScores/10/7}}</center><br />
== Top 10 Articles and Discussions ==<br />
<br />
{{Box|Most Popular Articles|<TopTenPages offset=1/>|70%|left}}<br />
<br clear="both" /><br />
{{Box|Most Discussed Articles|<TopTenPages namespace="talk"/>|70%|left}}<br />
<br clear="both" /></div>Danimohttp://techbase.kde.org/StatsStats2008-10-21T16:20:18Z<p>Danimo: </p>
<hr />
<div>== Top 10 contributors of the last week ==<br />
<center><br />
{{Special:ContributionScores/10/7}}<br />
</center><br />
== Top 10 Articles and Discussions ==<br />
<br />
{{Box|Most Popular Articles|<TopTenPages offset=1/>|70%|left}}<br />
<br clear="both" /><br />
{{Box|Most Discussed Articles|<TopTenPages namespace="talk"/>|70%|left}}<br />
<br clear="both" /></div>Danimohttp://techbase.kde.org/StatsStats2008-10-21T16:19:49Z<p>Danimo: Stats page from userbase (required some extensions)</p>
<hr />
<div>== Top 10 contributors of the last week ==<br />
<br />
{{Special:ContributionScores/10/7}}<br />
<br />
== Top 10 Articles and Discussions ==<br />
<br />
{{Box|Most Popular Articles|<TopTenPages offset=1/>|70%|left}}<br />
<br clear="both" /><br />
{{Box|Most Discussed Articles|<TopTenPages namespace="talk"/>|70%|left}}<br />
<br clear="both" /></div>Danimohttp://techbase.kde.org/User_talk:Mark_ZieglerUser talk:Mark Ziegler2008-05-10T10:44:38Z<p>Danimo: </p>
<hr />
<div>Hi Mark, please use ((/Link/To/SubPage|Description)) (with "[" instead of "(") to link inside of TechBase. The advantage of using internal links is that we can use them to trace links between pages. --[[User:Danimo|Danimo]] 12:14, 10 May 2008 (CEST)<br />
<br />
:You mean "[" instead of "(" or "(" instead of "[". Can you give an example? -- Mark<br />
<br />
::Sure: [[/Development/Books|Book section]] (You need the | in additionn as a seperator, since wiki titles may contain spaces) --[[User:Danimo|Danimo]] 12:41, 10 May 2008 (CEST)<br />
<br />
:: oh, and you can sign with --&#126;&#126;&#126;&#126;, it will be converted on submit and also show up correctly in the preview.</div>Danimohttp://techbase.kde.org/User_talk:Mark_ZieglerUser talk:Mark Ziegler2008-05-10T10:41:54Z<p>Danimo: </p>
<hr />
<div>Hi Mark, please use ((/Link/To/SubPage|Description)) (with "[" instead of "(") to link inside of TechBase. The advantage of using internal links is that we can use them to trace links between pages. --[[User:Danimo|Danimo]] 12:14, 10 May 2008 (CEST)<br />
<br />
:You mean "[" instead of "(" or "(" instead of "[".<br />
Can you give an example? <br />
Mark<br />
<br />
::Sure: [[/Development/Books|Book section]] (You need the | in additionn as a seperator, since wiki titles may contain spaces) --[[User:Danimo|Danimo]] 12:41, 10 May 2008 (CEST)</div>Danimohttp://techbase.kde.org/User_talk:Mark_ZieglerUser talk:Mark Ziegler2008-05-10T10:14:43Z<p>Danimo: New page: Hi Mark, please use ((/Link/To/SubPage Description)) (with "[" instead of "(") to link inside of TechBase. The advantage of using internal links is that we can use them to trace links betw...</p>
<hr />
<div>Hi Mark, please use ((/Link/To/SubPage Description)) (with "[" instead of "(") to link inside of TechBase. The advantage of using internal links is that we can use them to trace links between pages. --[[User:Danimo|Danimo]] 12:14, 10 May 2008 (CEST)</div>Danimohttp://techbase.kde.org/User_talk:DanimoUser talk:Danimo2008-04-20T15:55:28Z<p>Danimo: </p>
<hr />
<div>==CAPTCHAs that won't go away==<br />
Aseigo [[Talk:Main_Page#Something_wrong_with_the_CAPTCHAs|suggested]] that I ask you about this. Everytime I make an edit, it claims that I am adding a URL, and wants me to do some math. Is it even supposed to do this to registered users? In any case, ''most'' times I am not adding a url at all, and I tire of the systems inordinate appetite for elementary arithmetic. Can this be fixed? Thanks. --[[User:Axiom|Axiom]] 20:27, 28 March 2007 (CEST)<br />
<br />
== <nowiki>{{file}}</nowiki> ==<br />
<br />
As you asked me, I removed all the occurrences of <nowiki>{{file}}</nowiki> with <nowiki>{{path}}</nowiki>, and removed the obsolete template <nowiki>{{file}}</nowiki>. -- [[user:Pino|pino]] 02:16, 29 May 2007 (CEST)<br />
<br />
:There is also a template called <nowiki>{{module}}</nowiki> for KDE modules (kdelibs, kdebase), etc. I initially used path here, too, and thought that's enough. It's not widely used, only by 2 articles. Maybe we should replace it by path again? What do you think? --[[User:Dhaumann|Dhaumann]] 09:14, 29 May 2007 (CEST)<br />
<br />
::I agree. --[[User:Danimo|Danimo]] 09:28, 29 May 2007 (CEST)<br />
<br />
::Or maybe link it to the module page in the apidocs (e.g [http://api.kde.org/4.0-api/kdelibs-apidocs/ kdelibs])? --[[User:Milliams|milliams]] 14:47, 29 May 2007 (CEST)<br />
<br />
:::Good idea, <nowiki>{{kdelibs}}, {{kdebase}}</nowiki> etc... +1 from my side :) --[[User:Dhaumann|Dhaumann]] 15:11, 29 May 2007 (CEST)<br />
<br />
::::Sounds good. Or how about <nowiki>{{module|foo}}</nowiki> linking to http://api.kde.org/4.0-api/foo-apidocs/? I don't know how flexible this method is though? --[[User:Milliams|milliams]] 19:41, 29 May 2007 (CEST)<br />
<br />
:::::+1 on [[User:Milliams|milliams]]' idea --[[user:Pino|pino]] 21:35, 29 May 2007 (CEST)<br />
<br />
<br />
==Assistance needed for new contributor to Techbase==<br />
Hi. My name is Thor, I am a new contributor to KDE and I am looking to provide some help with regard to one of the KDE Games, KTuberling (The Potato dude). I am a Polyglot, and work in many different languages, and I have noticed on issues of KTuberling that even with correct software in place, certain speech selections do not function (Notably; Serbian and Danish). I have been working on these for a while and would like to obtain source code for the Tuberling to try and correct the error. Could you tell me please how I find out who is working on what, and what they are doing to it? Thanks and Regards. [[User:ThunderGod|ThunderGod]] 15:40, 30 December 2007 (CET)<br />
:The best place to find assistance with this is by visiting the #kdegames or #kde-edu channels on irc.freenode.org or by sending an joining the KDE Games mailing list at [https://mail.kde.org/mailman/listinfo/kde-games-devel https://mail.kde.org/mailman/listinfo/kde-games-devel]. I believe tsdgeos (Albert Astals Cid) is the best person to speak to. --[[User:Milliams|milliams]] 17:13, 30 December 2007 (CET)<br />
<br />
== More readable URLs ==<br />
<br />
At the moment all links on this site are in the form [http://techbase.kde.org/index.php?title=Development/Tutorials http://techbase.kde.org/index.php?title=Development/Tutorials]. I think it would make the site much more readable to convert these links into something like [http://techbase.kde.org/Development/Tutorials http://techbase.kde.org/Development/Tutorials]. Now, as you can see, if you click on that link it does indeed work and takes you to the same page (so you've obviously got mod_rewrite working correctly) so the problem is that mediawiki itself isn't formatting it's links to take advantage of this. I think you basically need to do step 2 from [http://www.mediawiki.org/wiki/Manual:Short_URL#Setup_steps here]. --[[User:Milliams|milliams]] 14:53, 18 April 2008 (CEST)<br />
<br />
== Remove my account ==<br />
<br />
Please remove my account; i'd like to choose another username. Thank you. [[User:Krf|KRF]]<br />
<br />
:Mediawiki has no concept of user account deletion, since that would mess up the history. Just create a new user and add redirects from your current user accounts user page. --[[User:Danimo|Danimo]] 17:55, 20 April 2008 (CEST)</div>Danimohttp://techbase.kde.org/User:DanimoUser:Danimo2008-04-06T21:58:41Z<p>Danimo: </p>
<hr />
<div>== Subpages ==<br />
<br />
{{List_subpages}}<br />
<br />
== TODO ==<br />
<br />
* Beautify Subpage titles<br />
<br />
<br />
== Bugs ==<br />
sorry for reporting a bug here; but this seems like as good a place as any :)<br />
When using <nowiki><code cpp></nowiki> tags I noted a bug. Specifically when you use the colon (or other means) to indent it. [[User:Zander|Zander]] 20:39, 9 April 2007 (CEST)<br />
Example code:<br />
<br />
:<code cpp><br />
#include <iostream><br />
#include <QtCore/QDate><br />
#include <zlib.h><br />
</code><br />
<br />
== New CMS for the dot ==<br />
<br />
See [[/Dot TLC]]</div>Danimohttp://techbase.kde.org/User:DanimoUser:Danimo2008-04-06T21:58:20Z<p>Danimo: </p>
<hr />
<div>== Subpages ==<br />
<br />
{{List_subpages}}<br />
<br />
== TODO ==<br />
<br />
* Beautify Subpage titles<br />
<br />
<br />
== Bugs ==<br />
sorry for reporting a bug here; but this seems like as good a place as any :)<br />
When using <nowiki><code cpp></nowiki> tags I noted a bug. Specifically when you use the colon (or other means) to indent it. [[User:Zander|Zander]] 20:39, 9 April 2007 (CEST)<br />
Example code:<br />
<br />
:<code cpp><br />
#include <iostream><br />
#include <QtCore/QDate><br />
#include <zlib.h><br />
</code><br />
<br />
== New CMS for the dot ==<br />
<br />
See [/Dot TLC]</div>Danimohttp://techbase.kde.org/User:DanimoUser:Danimo2008-04-06T21:57:40Z<p>Danimo: </p>
<hr />
<div>== Subpages ==<br />
<br />
{{List_subpages}}<br />
<br />
== TODO ==<br />
<br />
* Beautify Subpage titles<br />
<br />
<br />
== Bugs ==<br />
sorry for reporting a bug here; but this seems like as good a place as any :)<br />
When using <nowiki><code cpp></nowiki> tags I noted a bug. Specifically when you use the colon (or other means) to indent it. [[User:Zander|Zander]] 20:39, 9 April 2007 (CEST)<br />
Example code:<br />
<br />
:<code cpp><br />
#include <iostream><br />
#include <QtCore/QDate><br />
#include <zlib.h><br />
</code><br />
<br />
== New CMS for the dot ==</div>Danimohttp://techbase.kde.org/Template:I18n/Language_Navigation_BarTemplate:I18n/Language Navigation Bar2008-03-04T06:53:37Z<p>Danimo: Please don't add new languages if there isn't at least one page (preferably the main page) translated into it</p>
<hr />
<div><noinclude><br />
{{Template:I18n/Language Navigation Bar|Template:I18n/Language_Navigation_Bar}}<br />
== How to use ==<br />
<br />
This template needs to be included in all translations of one page.<br />
Let's assume we have page called "Foo". The translations are called<br />
Foo (de), Foo (fr), etc. <br />
<br />
In all translations you _must_ insert the following line:<br />
<br />
<nowiki>{{Template:I18n/Language_Navigation_Bar|Foo}}</nowiki><br />
<br />
This will create a correctly linked bar that allows to switch between all translations of a site. If you want to add a new translation language, add<br />
it here and it will appear on all sites. Untranslated versions will appear<br />
red as usual.<br />
</noinclude><br />
<div style="margin:auto;font-size:83.3%;text-align:left"><br />
<b>Languages:</b><br />
<span lang="en">[[{{{1}}}|English]]</span> |<br />
<span lanf="da">[[{{{1}}}_(da)|Dansk]]</span> |<br />
<span lang="de">[[{{{1}}}_(de)|Deutsch]]</span> |<br />
<span lang="fr">[[{{{1}}}_(fr)|Français]]</span> |<br />
<span lang="it">[[{{{1}}}_(it)|Italiano]]</span> |<br />
<span lang="ru">[[{{{1}}}_(ru)|Русский]]</span> |<br />
<span lang="sl">[[{{{1}}}_(sl)|Slovenščina]]</span> |<br />
<span lang="fi">[[{{{1}}}_(fi)|Suomi]]</span> |<br />
<span lang="zh_CN">[[{{{1}}}_(zh_CN)|简体中文]]</span> |<br />
<span lang="gl">[[{{{1}}}_(gl)|Galego]]</span> |<br />
<span lang="es">[[{{{1}}}_(es)|Español]]</span> |<br />
<span lang="eo">[[{{{1}}}_(eo)|Esperanto]]</span> |<br />
<span lang="se">[[{{{1}}}_(se)|Svenska]]</span> |<br />
<span lang="ko">[[{{{1}}}_(ko)|한국어]]</span> |<br />
<span lang="ro">[[{{{1}}}_(ro)|Romanian]]</span> |<br />
<span lang="pt_BR">[[{{{1}}}_(pt_BR)|Brazilian Portuguese]]</span> | <br />
<span lang="sl">[[{{{1}}}_(cs)|Česky]]</span> |<br />
<span lang="ar">[[{{{1}}}_(ar)|عربي]]</span> |<br />
<span lang="fa">[[{{{1}}}_(fa)|فارسی]]</span><br />
</div></div>Danimohttp://techbase.kde.org/ContributeContribute2008-02-19T11:44:33Z<p>Danimo: </p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Contribute}}<br />
This page intends to give an overview of the different aspects of KDE development in particular for programming related issues. '''The KDE project welcomes anyone willing to help'''.<br />
<br />
{{note|There are a lot of ways to get involved in KDE development, which can be summed up in several categories:<br />
:''Documentation, Translation, Development, Usability, Accessibility, Artwork, Promotion<br />
'''Especially for tasks other than development (writing code) KDE's pages about [http://kde.org/getinvolved/ how to get involved] give a good overview.'''<br />
}}<br />
<br />
== News and Mail Sources ==<br />
The general direction of the KDE project is determined by those who do the work - there is no single high level plan for what KDE will look like in the future.<br />
<br />
If you want to find out what is currently happening, then there are a number of sources you might like to consider:<br />
; [http://www.kde.org/mailinglists/ Mailing Lists]<br />
: Probably the best way to find out what's going on in KDE development. Archives are available [http://lists.kde.org here]<br />
<br />
; [http://commitfilter.kde.org/ CommitFilter]<br />
: Receive notification of [http://en.wikipedia.org/wiki/Subversion SVN] commits in areas that interest you.<br />
<br />
; [http://commit-digest.org/ KDE Commit-Digest]<br />
: Weekly summary of SVN commits.<br />
<br />
; [http://dot.kde.org/ The Dot]<br />
: The KDE news site.<br />
<br />
== Getting Started with Coding ==<br />
Getting started at ''coding'' in KDE is a matter of finding something to fix, and fixing it. You may want to consult the module overview to help find what you are looking for; once you have fixed something, you will want to send in a patch. If you do that a few times, you may want to apply for an SVN account so you can fix things directly.<br />
* [[Contribute/List of KDE Modules|Module overview]]<br />
* [[Contribute/Send Patches|Sending patches]]<br />
* [[Contribute/Get a SVN Account|Applying for a KDE SVN Account]]<br />
* [[Contribute/First Steps with your KDE SVN Account|First steps with your new SVN account]]<br />
<br />
At the moment, there are two choices for development within KDE - you can work on KDE3, or KDE4. KDE3 is a good choice for bug fixing, however the main development work effort (and all new features) is on KDE4. This document mainly focuses on work in support of KDE4.<br />
<br />
=== C++ ===<br />
KDE is mostly written in C++. If you are not familiar with C++, you should do at least some work on it. There are a number of good books on C++ - an excellent source is [http://mindview.net/Books/TICPP/ThinkingInCPP2e.html Bruce Eckel's "Thinking in C++"], which is available both as a free download and as a printed document. It isn't essential to understand everything before you start in KDE, but you do need to understand basic syntax and operations.<br />
<br />
=== Qt ===<br />
To become proficient with KDE coding, you should understand the Qt toolkit. If you are not familiar with Qt, you should work through the tutorials included with Qt ([http://doc.trolltech.com/latest/examples.html Qt4 version], [http://doc.trolltech.com/3.3/tutorial.html Qt3 version]).<br />
<br />
If you are more into multimedia and videos for a start you might want to spend two amazing minutes on watching [http://www.trolltech.com/trolltech/products/qt/learnmore/video/demos/browser Building a Simple Help Documentation Browser with Qt4 Designer]. If that got your attention you might also want to watch the video introduction [http://www.trolltechvideo.com/video/day1/room_a/a_1_1/video.html Hello Qt] by Mark Summerfield which is part of the [http://www.trolltech.com/company/newsroom/events/allevents/devdays2006/videolinks Trolltech Developer Days 2006 presentations].<br />
<br />
If you need a gentler introduction to Qt, or would just like an alternative view, then you may wish to look at the [http://qt4.digitalfanatics.org/tiqt/ The Independent Qt Tutorial] (Currently offline due to book contract).<br />
<br />
If you prefer to learn Qt by reading a traditional book, take a look at Trolltechs [http://trolltech.com/developer/documentation/books book page]. More suggestions on becoming familiar with Qt4 are [http://doc.trolltech.com/latest/how-to-learn-qt.html available here as well]. <br />
<br />
=== KDE ===<br />
A range of information on KDE techniques is available in the [[Development/Tutorials|tutorial section]]. Note that some of these tutorials still target KDE3, though they should be at least partly applicable.<br />
<br />
You will also find useful information on KDE coding in the [[Development/FAQs|FAQs]] section. This information may also be somewhat dated for KDE4, however much of it is broadly applicable, even outside KDE.<br />
<br />
You can also read [[Development/Further Information#Books|KDE coding books]].<br />
<br />
Last, but by no means least, KDE comes with extensive class (Application Programmer Interface) documentation. This is available in the<br />
[[Development/Tutorials/API Documentation|KDE API Reference Manuals]] section, which also contains a number of useful links on how to write or update the class documentation. You can also generate these on your own machine, or refer to a more up-to-date online version at [http://www.englishbreakfastnetwork.org/apidocs/apidox-kde-4.0/kdelibs-apidocs/ The English Breakfast Network].<br />
<br />
A more detailed description of the steps above is available in our [http://quality.kde.org/develop/howto/howtohack.php Programming Guide].<br />
<br />
== Getting Involved in Bug Hunting and Application Quality ==<br />
<br />
There is a large number of applications within KDE, and not all of them have a maintainer dedicated to managing bugs and generally helping out with all the issues associated with turning some working code into a polished application.<br />
<br />
If you are interested in helping out with KDE, but don't know where to start, visit [http://www.kde.org/getinvolved/ Contribute Website] for more information. Note that you do not need any programming skills to become involved. In particular develpers regurarly publish so-called [[/Junior Jobs|Junior Jobs]] to encourage new contributions.<br />
<br />
Of course, you can become involved in bug hunting without being part of the KDE Quality Team - just create yourself an account on the KDE [http://bugs.kde.org bug tracking system], and start searching / sorting through the bugs. Again, you don't have to have programming skills - it helps the programmers enormously just to have a procedure that allows a bug to be consistently reproduced.<br />
<br />
The [[Contribute/Bugsquad|Bugsquad]] tries to keep track of bugs in KDE software and make sure that valid bugs are noticed by developers. You do not need any programming knowledge to be in the Bugsquad; in fact it is a great way to return something to the KDE community if you cannot program.<br />
<br />
== Historical Sources ==<br />
<br />
; [http://www.kerneltraffic.org/kde/archives.html KDE Traffic]<br />
: Summary of the development mailing lists. KDE Traffic ran for 76 issues, from 10 March 2001 until 16 April 2004. The KDE Commit-Digest (described above) is its logical successor.</div>Danimohttp://techbase.kde.org/Schedules/KDE4/4.1_Feature_PlanSchedules/KDE4/4.1 Feature Plan2008-01-30T17:38:52Z<p>Danimo: </p>
<hr />
<div>__NOTOC__<br />
<br />
= Instructions =<br />
<br />
Deadline for adding entries here for the 4.1 release is '''31 March 2008'''.<br><br />
Entries added after that date will be scheduled for the 4.2 release.<br />
<br />
todo => not started yet<br><br />
in-progress => started, but not completed yet<br><br />
done => completed<br />
<br />
= kdelibs =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
{{FeatureTodo|kdeui|Goya, a framework for inserting controls into itemviews in a really easy and fast way|ereslibre@kde.org|Rafael Fernández López}}<br />
|}<br />
<br />
= kdepimlibs =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
{{FeatureTodo|Akonadi|Move the Akonadi development library from kdepim.|vkrause@kde.org|Volker Krause}}<br />
|}<br />
<br />
= kdebase-apps =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
= kdebase-workspace =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
= kdebase-runtime =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
= kdeaccessibility =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
= kdeadmin =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
{{FeatureInProgress|KSystemLog|KSystemLog, a Log Viewer Tool. Move from kde-apps|nicolas.ternisien@gmail.com}}<br />
|}<br />
<br />
= kdeartwork =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
= kdebindings =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
= kdeedu =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
= kdegames =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
= kdegraphics =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
{{FeatureDone|Dragon Player|A simple Phonon-based videoplayer application|ian.monroe@gmail.com}}<br />
|}<br />
<br />
= kdemultimedia =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
= kdenetwork =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
= kdepim =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
{{FeatureTodo|[http://decibel.kde.org Decibel]|Decibel, a framework for real time communication services. Move from playground/pim|info@basyskom.de|Tobias Hunger}}<br />
{{FeatureTodo|[http://kblogger.pwsp.net KBlogger]|KBlogger, a blogging application| christian_weilbach@.web.de|Christian Weilbach}}<br />
{{FeatureTodo|KMail|HTML Signatures|yez@familieschepers.nl|Edwin Schepers}}<br />
{{FeatureDone|KonsoleKalendar|Support "file" and "localdir" resources|winter@kde.org|Allen Winter}}<br />
|}<br />
<br />
= kdesdk =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
{{FeatureDone|Lokalize|Move this application (formerly known as Kaider) from extragear|shafff@ukr.net}}<br />
|}<br />
<br />
= kdetoys =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
= kdeutils =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
{{FeatureTodo|Okteta|bytelevel editor (successor to KHexEdit). Move from playground/utils.|kossebau@kde.org|Friedrich W. H. Kossebau}}<br />
|}<br />
<br />
= kdevelop =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
= kdevplatform =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
= kdewebdev =<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width: 100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status !! Project !! Description !! Contact<br />
|}</div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-30T15:01:53Z<p>Danimo: grml</p>
<hr />
<div>|- valign=top<br />
|style="background-color: {{{1|white}}};"|{{{2|status missing}}}||{{{3|project issing}}}||{{{4|description missing}}}||[mailto:{{{5}}} {{{6|email missing}}} &lt;{{{5}}}&gt;]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-30T14:54:58Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|style="background-color: {{{1|white}}};"|{{{2|status missing}}}||{{{3|project issing}}}||{{{4|description missing}}}||[mailto:{{{5}}} {{{6|email missing}}} {{{5}}}&gt;]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-30T14:51:36Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|style="background-color: {{{1|white}}};"|{{{2|status missing}}}||{{{3|project issing}}}||{{{4|description missing}}}||[mailto:{{{5}}} {{{6|email missing}}}&nbsp;&lt;{{{5}}}&gt;]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-30T14:50:48Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|style="background-color: {{{1|white}}};"|{{{2|status missing}}}||{{{3|project issing}}}||{{{4|description missing}}}||[mailto:{{{5}}} {{{6|&lt;{{{5}}}&gt;}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-30T14:49:46Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|style="background-color: {{{1|white}}};"|{{{2|status missing}}}||{{{3|project issing}}}||{{{4|description missing}}}||[mailto:{{{5}}} {{{6|&lt;{{{5}}}&gt;]}}} <br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-30T14:47:15Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|style="background-color: {{{1|white}}};"|{{{2|status missing}}}||{{{3|project issing}}}||{{{4|description missing}}}||[mailto:{{{5}}} {{{6|email missing}}} &lt;{{{5}}}&gt;]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-30T14:46:38Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|style="background-color: {{{1|white}}};"|{{{2|status missing}}}||{{{3|project issing}}}||{{{4|description missing}}}||[mailto:{{{5}}} {{{6|email missing}}} &lt;{{{5}}}&gt;>]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-30T14:45:36Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|style="background-color: {{{1|white}}};"|{{{2|status missing}}}||{{{3|project issing}}}||{{{4|description missing}}}||[mailto:{{{5}}} {{{6|{{{5}}} }}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-30T14:44:39Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|style="background-color: {{{1|white}}};"|{{{2|status missing}}}||{{{3|project issing}}}||{{{4|description missing}}}||[mailto:{{{5}}} {{{6|<{{{5|email missing}}}>}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-30T14:44:10Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|style="background-color: {{{1|white}}};"|{{{2|status missing}}}||{{{3|project issing}}}||{{{4|description missing}}}||[mailto:{{{5}}} {{{6|}}} <{{{5|email missing}}}>]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Schedules/KDE4/4.1_Feature_PlanSchedules/KDE4/4.1 Feature Plan2008-01-30T14:43:11Z<p>Danimo: </p>
<hr />
<div>= KDE4.1 Feature Plan =<br />
<br />
== Instructions ==<br />
<br />
Deadline for adding entries here for the 4.1 release is '''31 March 2008'''.<br><br />
Entries added after that date will be scheduled for the 4.2 release.<br />
<br />
todo => not started yet<br><br />
in-progress => started, but not completed yet<br><br />
done => completed<br />
<br />
=== kdelibs ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
{{FeatureTodo|kdeui|Goya, a framework for inserting controls into itemviews in a really easy and fast way|ereslibre@kde.org}}<br />
|}<br />
<br />
=== kdepimlibs ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
{{FeatureTodo|Akonadi|Move the Akonadi development library from kdepim.|vkrause@kde.org|Volker Krause}}<br />
|}<br />
<br />
=== kdebase-apps ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
=== kdebase-workspace ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
=== kdebase-runtime ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
=== kdeaccessibility ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
=== kdeadmin ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
{{FeatureInProgress|KSystemLog|KSystemLog, a Log Viewer Tool. Move from kde-apps|nicolas.ternisien@gmail.com}}<br />
|}<br />
<br />
=== kdeartwork ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
=== kdebindings ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
=== kdeedu ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
=== kdegames ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
=== kdegraphics ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
{{FeatureDone|Dragon Player|A simple Phonon-based videoplayer application|ian.monroe@gmail.com}}<br />
<br />
|}<br />
<br />
=== kdemultimedia ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
=== kdenetwork ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
=== kdepim ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
{{FeatureTodo|[http://decibel.kde.org Decibel]|Decibel, a framework for real time communication services. Move from playground/pim (Tobias Hunger)|info@basyskom.de}}<br />
{{FeatureTodo|[http://kblogger.pwsp.net KBlogger]|KBlogger, a blogging application (Christian Weilbach)| christian_weilbach@.web.de}}<br />
{{FeatureTodo|KMail|HTML Signatures (Edwin Schepers)|yez@familieschepers.nl}}<br />
{{FeatureDone|KonsoleKalendar|Support "file" and "localdir" resources (Allen Winter)|winter@kde.org}}<br />
|}<br />
<br />
=== kdesdk ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
{{FeatureDone|Lokalize|Move this application (formerly known as Kaider) from extragear|shafff@ukr.net}}<br />
<br />
|}<br />
<br />
=== kdetoys ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
=== kdeutils ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
{{FeatureTodo|Okteta, bytelevel editor (successor to KHexEdit)|Move from playground/utils (Friedrich W. H. Kossebau)|kossebau@kde.org}}<br />
|}<br />
<br />
=== kdevelop ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
=== kdevplatform ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|}<br />
<br />
=== kdewebdev ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|}</div>Danimohttp://techbase.kde.org/Template:FeatureInProgressTemplate:FeatureInProgress2008-01-30T14:42:16Z<p>Danimo: </p>
<hr />
<div>{{feature|yellow|in-progress|{{{1}}}|{{{2}}}|{{{3}}}|{{{4|}}}}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTodoTemplate:FeatureTodo2008-01-30T14:41:37Z<p>Danimo: </p>
<hr />
<div>{{feature|red|todo|{{{1}}}|{{{2}}}|{{{3}}}|{{{4|}}}}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-30T14:41:02Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|style="background-color: {{{1|white}}};"|{{{2|status missing}}}||{{{3|project issing}}}||{{{4|description missing}}}||[mailto:{{{5}}} {{{6|}}} {{{5|email missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureDoneTemplate:FeatureDone2008-01-30T14:40:50Z<p>Danimo: </p>
<hr />
<div>{{feature|green|Done|{{{1}}}|{{{2}}}|{{{3}}}|{{{4|}}}}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureDoneTemplate:FeatureDone2008-01-30T14:40:27Z<p>Danimo: </p>
<hr />
<div>{{feature|green|Done|{{{1}}}|{{{2}}}|{{{3}}}|{{{3}}}}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-30T14:37:40Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|style="background-color: {{{5|white}}};"|{{{1|status missing}}}||{{{2|project issing}}}||{{{3|description missing}}}||[mailto:{{{4}}} {{{6|}}} {{{4|email missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-30T14:36:30Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|style="background-color: {{{5|white}}};"|{{{1|status missing}}}||{{{2|project issing}}}||{{{3|description missing}}}||[mailto:{{{4}}} {{{5|}}} {{{4|email missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTodoTemplate:FeatureTodo2008-01-29T23:21:30Z<p>Danimo: </p>
<hr />
<div>{{feature|todo|{{{1}}}|{{{2}}}|{{{3}}}|red}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureInProgressTemplate:FeatureInProgress2008-01-29T23:20:52Z<p>Danimo: </p>
<hr />
<div>{{feature|in-progress|{{{1}}}|{{{2}}}|{{{3}}}|yellow}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureDoneTemplate:FeatureDone2008-01-29T23:20:29Z<p>Danimo: </p>
<hr />
<div>{{feature|Done|{{{1}}}|{{{2}}}|{{{3}}}|green}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/MediaWiki:Common.jsMediaWiki:Common.js2008-01-29T23:18:16Z<p>Danimo: New page: /* Any JavaScript here will be loaded for all users on every page load. */ /*<source lang="javascript">*/ //Overrides the function with the same name in http://svn.wikimedia.org/viewvc/me...</p>
<hr />
<div>/* Any JavaScript here will be loaded for all users on every page load. */<br />
<br />
/*<source lang="javascript">*/<br />
//Overrides the function with the same name in http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/skins/common/wikibits.js<br />
//Fixes a bug: for the sorting order, takes the whole number, not the number before the second comma. <br />
//Also, removes spaces. See [[Help:Sorting]].<br />
function ts_parseFloat(num) {<br />
if (!num) return 0;<br />
num = removeSpaces(num);<br />
num = parseFloat(num.replace(/,/g, ""));<br />
return (isNaN(num) ? 0 : num);<br />
}<br />
<br />
//Keep spaces in "currency" mode, to sort a range "70 to 80" at 70, not 7080<br />
function ts_parseFloat_ks(num) {<br />
if (!num) return 0;<br />
num = parseFloat(num.replace(/,/g, ""));<br />
return (isNaN(num) ? 0 : num);<br />
}<br />
<br />
//Auxiliary function for function ts_resortTable(lnk)<br />
function removeSpaces(string) {<br />
var tstring = "";<br />
string = '' + string;<br />
splitstring = string.split(" ");<br />
for(i = 0; i < splitstring.length; i++)<br />
tstring += splitstring[i];<br />
return tstring;<br />
}<br />
<br />
//Overrides the function with the same name in http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/skins/common/wikibits.js<br />
//Changes the criteria for various sorting modes, see [[Help:Sorting]].<br />
//For easy maintenance the difference with wikibits.js is kept limited to a few lines.<br />
function ts_resortTable(lnk) {<br />
// get the span<br />
var span = lnk.getElementsByTagName('span')[0];<br />
<br />
var td = lnk.parentNode;<br />
var tr = td.parentNode;<br />
var column = td.cellIndex;<br />
<br />
var table = tr.parentNode;<br />
while (table && !(table.tagName && table.tagName.toLowerCase() == 'table'))<br />
table = table.parentNode;<br />
if (!table) return;<br />
<br />
// Work out a type for the column<br />
if (table.rows.length <= 1) return;<br />
<br />
// Skip the first row if that's where the headings are<br />
var rowStart = (table.tHead && table.tHead.rows.length > 0 ? 0 : 1);<br />
<br />
var itm = "";<br />
for (var i = rowStart; i < table.rows.length; i++) {<br />
if (table.rows[i].cells.length > column) {<br />
itm = ts_getInnerText(table.rows[i].cells[column]);<br />
itm = itm.replace(/^[\s\xa0]+/, "").replace(/[\s\xa0]+$/, "");<br />
if (itm != "") break;<br />
}<br />
}<br />
<br />
sortfn = ts_sort_caseinsensitive;<br />
itmns = removeSpaces(itm);<br />
if (itmns.match(/^[\d\.\,\-\+]+\%?$/)) sortfn = ts_sort_numeric;<br />
if (itmns.match(/^[\d\.\,\-\+]+[eE][\d\-\+]+\%?$/)) sortfn = ts_sort_numeric;<br />
if (itmns.match(/^[\d\.\,\-\+]+e[\d\-\+]+\u00d710[\d\-\+]+\%?$/)) sortfn = ts_sort_numeric;<br />
if (itm.match(/^\d\d[\/. -][a-zA-Z]{3}[\/. -]\d\d\d\d$/))<br />
sortfn = ts_sort_date;<br />
if (itm.match(/^\d\d[\/.-]\d\d[\/.-]\d\d\d\d$/))<br />
sortfn = ts_sort_date;<br />
if (itm.match(/^\d\d[\/.-]\d\d[\/.-]\d\d$/))<br />
sortfn = ts_sort_date;<br />
if (itm.match(/^[\u00a3$\u20ac\u00a5]/)) // pound dollar euro yen<br />
sortfn = ts_sort_currency;<br />
if (itm.match(/sm=c$/)) sortfn = ts_sort_currency;<br />
if (itm.match(/sm=d$/)) sortfn = ts_sort_date;<br />
if (itm.match(/sm=n$/)) sortfn = ts_sort_numeric;<br />
<br />
var reverse = (span.getAttribute("sortdir") == 'down');<br />
<br />
var newRows = new Array();<br />
for (var j = rowStart; j < table.rows.length; j++) {<br />
var row = table.rows[j];<br />
var keyText = ts_getInnerText(row.cells[column]);<br />
var oldIndex = (reverse ? -j : j);<br />
<br />
newRows[newRows.length] = new Array(row, keyText, oldIndex);<br />
}<br />
<br />
newRows.sort(sortfn);<br />
<br />
var arrowHTML;<br />
if (reverse) {<br />
arrowHTML = '<img src="'+ ts_image_path + ts_image_down + '" alt="&darr;"/>';<br />
newRows.reverse();<br />
span.setAttribute('sortdir','up');<br />
} else {<br />
arrowHTML = '<img src="'+ ts_image_path + ts_image_up + '" alt="&uarr;"/>';<br />
span.setAttribute('sortdir','down');<br />
}<br />
<br />
// We appendChild rows that already exist to the tbody, so it moves them rather than creating new ones<br />
// don't do sortbottom rows<br />
for (var i = 0; i < newRows.length; i++) {<br />
if ((" "+newRows[i][0].className+" ").indexOf(" sortbottom ") == -1)<br />
table.tBodies[0].appendChild(newRows[i][0]);<br />
}<br />
// do sortbottom rows only<br />
for (var i = 0; i < newRows.length; i++) {<br />
if ((" "+newRows[i][0].className+" ").indexOf(" sortbottom ") != -1)<br />
table.tBodies[0].appendChild(newRows[i][0]);<br />
}<br />
<br />
// Delete any other arrows there may be showing<br />
var spans = getElementsByClassName(tr, "span", "sortarrow");<br />
for (var i = 0; i < spans.length; i++) {<br />
spans[i].innerHTML = '<img src="'+ ts_image_path + ts_image_none + '" alt="&darr;"/>';<br />
}<br />
span.innerHTML = arrowHTML;<br />
<br />
ts_alternate(table); <br />
}<br />
<br />
function ts_dateToSortKey(date) { <br />
// y2k notes: two digit years less than 50 are treated as 20XX, greater than 50 are treated as 19XX<br />
if (date.length > 10) {<br />
switch (date.substr(3,3).toLowerCase()) {<br />
case "jan": var month = "01"; break;<br />
case "feb": var month = "02"; break;<br />
case "mar": var month = "03"; break;<br />
case "apr": var month = "04"; break;<br />
case "may": var month = "05"; break;<br />
case "jun": var month = "06"; break;<br />
case "jul": var month = "07"; break;<br />
case "aug": var month = "08"; break;<br />
case "sep": var month = "09"; break;<br />
case "oct": var month = "10"; break;<br />
case "nov": var month = "11"; break;<br />
case "dec": var month = "12"; break;<br />
// default: var month = "00";<br />
}<br />
return date.substr(7,4)+month+date.substr(0,2);<br />
} else if (date.length == 10) {<br />
return date.substr(6,4)+date.substr(3,2)+date.substr(0,2);<br />
} else if (date.length == 8) {<br />
yr = date.substr(6,2);<br />
if (parseInt(yr) < 50) { <br />
yr = '20'+yr; <br />
} else { <br />
yr = '19'+yr; <br />
}<br />
return yr+date.substr(3,2)+date.substr(0,2);<br />
}<br />
return "00000000";<br />
}<br />
<br />
function ts_sort_currency(a,b) {<br />
var aa = ts_parseFloat_ks(a[1].replace(/[\u00a3$\u20ac\u00a5a-zA-Z]/g,''));<br />
var bb = ts_parseFloat_ks(b[1].replace(/[\u00a3$\u20ac\u00a5a-zA-Z]/g,''));<br />
return (aa != bb ? aa - bb : a[2] - b[2]);<br />
}<br />
<br />
/** Collapsible tables *********************************************************<br />
*<br />
* Description: Allows tables to be collapsed, showing only the header. See<br />
* [[Wikipedia:NavFrame]].<br />
* Maintainer on Wikipedia: [[User:R. Koot]]<br />
*/<br />
<br />
var autoCollapse = 2;<br />
var collapseCaption = "hide";<br />
var expandCaption = "show";<br />
<br />
function hasClass( element, className ) {<br />
var Classes = element.className.split( " " );<br />
for ( var i = 0; i < Classes.length; i++ ) {<br />
if ( Classes[i] == className ) {<br />
return ( true );<br />
}<br />
}<br />
return ( false );<br />
}<br />
<br />
function collapseTable( tableIndex )<br />
{<br />
var Button = document.getElementById( "collapseButton" + tableIndex );<br />
var Table = document.getElementById( "collapsibleTable" + tableIndex );<br />
<br />
if ( !Table || !Button ) {<br />
return false;<br />
}<br />
<br />
var Rows = Table.getElementsByTagName( "tr" ); <br />
<br />
if ( Button.firstChild.data == collapseCaption ) {<br />
for ( var i = 1; i < Rows.length; i++ ) {<br />
Rows[i].style.display = "none";<br />
}<br />
Button.firstChild.data = expandCaption;<br />
} else {<br />
for ( var i = 1; i < Rows.length; i++ ) {<br />
Rows[i].style.display = Rows[0].style.display;<br />
}<br />
Button.firstChild.data = collapseCaption;<br />
}<br />
}<br />
<br />
function createCollapseButtons()<br />
{<br />
var tableIndex = 0;<br />
var NavigationBoxes = new Object();<br />
var Tables = document.getElementsByTagName( "table" );<br />
<br />
for ( var i = 0; i < Tables.length; i++ ) {<br />
if ( hasClass( Tables[i], "collapsible" ) ) {<br />
NavigationBoxes[ tableIndex ] = Tables[i];<br />
Tables[i].setAttribute( "id", "collapsibleTable" + tableIndex );<br />
<br />
var Button = document.createElement( "span" );<br />
var ButtonLink = document.createElement( "a" );<br />
var ButtonText = document.createTextNode( collapseCaption );<br />
<br />
Button.style.styleFloat = "right";<br />
Button.style.cssFloat = "right";<br />
Button.style.fontWeight = "normal";<br />
Button.style.textAlign = "right";<br />
Button.style.width = "6em";<br />
<br />
ButtonLink.setAttribute( "id", "collapseButton" + tableIndex );<br />
ButtonLink.setAttribute( "href", "javascript:collapseTable(" + tableIndex + ");" );<br />
ButtonLink.appendChild( ButtonText );<br />
<br />
Button.appendChild( document.createTextNode( "[" ) );<br />
Button.appendChild( ButtonLink );<br />
Button.appendChild( document.createTextNode( "]" ) );<br />
<br />
var Header = Tables[i].getElementsByTagName( "tr" )[0].getElementsByTagName( "th" )[0];<br />
/* only add button and increment count if there is a header row to work with */<br />
if (Header) {<br />
Header.insertBefore( Button, Header.childNodes[0] );<br />
tableIndex++;<br />
}<br />
}<br />
}<br />
<br />
for ( var i = 0; i < tableIndex; i++ ) {<br />
if ( hasClass( NavigationBoxes[i], "collapsed" ) || ( tableIndex >= autoCollapse && hasClass( NavigationBoxes[i], "autocollapse" ) ) ) {<br />
collapseTable( i );<br />
}<br />
}<br />
}<br />
<br />
addOnloadHook( createCollapseButtons );<br />
<br />
//Shuffle for election candidates<br />
function dshuf(){<br />
var shufsets=new Object()<br />
var rx=new RegExp('dshuf'+'\\s+(dshufset\\d+)', 'i') <br />
var divs=document.getElementsByTagName("div")<br />
for (var i=0; i<divs.length; i++){<br />
if (rx.test(divs[i].className)){<br />
if (typeof shufsets[RegExp.$1]=="undefined"){ <br />
shufsets[RegExp.$1]=new Object() <br />
shufsets[RegExp.$1].inner=[] <br />
shufsets[RegExp.$1].member=[]<br />
}<br />
shufsets[RegExp.$1].inner.push(divs[i].innerHTML) <br />
shufsets[RegExp.$1].member.push(divs[i]) <br />
}<br />
}<br />
for (shufset in shufsets){<br />
shufsets[shufset].inner.sort(function() {return 0.5 - Math.random()})<br />
for (var i=0; i<shufsets[shufset].member.length; i++){<br />
shufsets[shufset].member[i].innerHTML=shufsets[shufset].inner[i]<br />
shufsets[shufset].member[i].style.display="block"<br />
}<br />
}<br />
<br />
}<br />
<br />
addOnloadHook(dshuf);<br />
<br />
/*************<br />
*** AJAX transclusion table <http://meta.wikimedia.org/wiki/User:Pathoschild/Scripts/AJAX_transclusion_table><br />
*** by [[m:user:Pathoschild]]<br />
*************/<br />
function attLoader() {<br />
if(getElementsByClassName(document.getElementsByTagName('body')[0],'table','attable').length) {<br />
document.write('<script type="text/javascript" src="'<br />
+ 'http://meta.wikimedia.org/w/index.php?title=User:Pathoschild/Scripts/AJAX_transclusion_table.js' <br />
+ '&action=raw&ctype=text/javascript&dontcountme=s"></script>');<br />
}<br />
}<br />
addOnloadHook(attLoader);<br />
<br />
/** JSconfig ************<br />
* Global configuration options to enable/disable and configure<br />
* specific script features from [[MediaWiki:Common.js]] and<br />
* [[MediaWiki:Monobook.js]]<br />
* This framework adds config options (saved as cookies) to [[Special:Preferences]]<br />
* For a more permanent change you can override the default settings in your <br />
* [[Special:Mypage/monobook.js]]<br />
* for Example: JSconfig.keys[loadAutoInformationTemplate] = false;<br />
*<br />
* Maintainer: [[User:Dschwen]]<br />
*/<br />
<br />
var JSconfig =<br />
{<br />
prefix : 'jsconfig_',<br />
keys : {},<br />
meta : {},<br />
<br />
//<br />
// Register a new configuration item<br />
// * name : String, internal name<br />
// * default_value : String or Boolean (type determines configuration widget)<br />
// * description : String, text appearing next to the widget in the preferences<br />
// * prefpage : Integer (optional), section in the preferences to insert the widget:<br />
// 0 : User profile<br />
// 1 : Skin<br />
// 2 : Math<br />
// 3 : Files<br />
// 4 : Date and time<br />
// 5 : Editing<br />
// 6 : Recent changes<br />
// 7 : Watchlist<br />
// 8 : Search<br />
// 9 : Misc<br />
//<br />
// Access keys through JSconfig.keys[name]<br />
//<br />
registerKey : function( name, default_value, description, prefpage )<br />
{<br />
if( typeof(JSconfig.keys[name]) == 'undefined' ) <br />
JSconfig.keys[name] = default_value;<br />
else {<br />
<br />
// all cookies are read as strings, <br />
// convert to the type of the default value<br />
switch( typeof(default_value) )<br />
{<br />
case 'boolean' : JSconfig.keys[name] = ( JSconfig.keys[name] == 'true' ); break;<br />
case 'number' : JSconfig.keys[name] = JSconfig.keys[name]/1; break;<br />
}<br />
<br />
}<br />
<br />
JSconfig.meta[name] = { 'description' : description, 'page' : prefpage || 0, 'default_value' : default_value };<br />
},<br />
<br />
readCookies : function()<br />
{<br />
var cookies = document.cookie.split("; ");<br />
var p =JSconfig.prefix.length;<br />
var i;<br />
<br />
for( var key in cookies )<br />
{<br />
if( cookies[key].substring(0,p) == JSconfig.prefix )<br />
{<br />
i = cookies[key].indexOf('=');<br />
//alert( cookies[key] + ',' + key + ',' + cookies[key].substring(p,i) );<br />
JSconfig.keys[cookies[key].substring(p,i)] = cookies[key].substring(i+1);<br />
}<br />
}<br />
},<br />
<br />
writeCookies : function()<br />
{<br />
for( var key in JSconfig.keys )<br />
document.cookie = JSconfig.prefix + key + '=' + JSconfig.keys[key] + '; path=/; expires=Thu, 2 Aug 2009 10:10:10 UTC';<br />
},<br />
<br />
evaluateForm : function()<br />
{<br />
var w_ctrl,wt;<br />
//alert('about to save JSconfig');<br />
for( var key in JSconfig.meta ) {<br />
w_ctrl = document.getElementById( JSconfig.prefix + key )<br />
if( w_ctrl ) <br />
{<br />
wt = typeof( JSconfig.meta[key].default_value );<br />
switch( wt ) {<br />
case 'boolean' : JSconfig.keys[key] = w_ctrl.checked; break;<br />
case 'string' : JSconfig.keys[key] = w_ctrl.value; break;<br />
}<br />
}<br />
}<br />
<br />
JSconfig.writeCookies();<br />
return true;<br />
},<br />
<br />
setUpForm : function()<br />
{ <br />
var prefChild = document.getElementById('preferences');<br />
if( !prefChild ) return;<br />
prefChild = prefChild.childNodes;<br />
<br />
//<br />
// make a list of all preferences sections<br />
//<br />
var tabs = new Array;<br />
var len = prefChild.length;<br />
for( var key = 0; key < len; key++ ) {<br />
if( prefChild[key].tagName &&<br />
prefChild[key].tagName.toLowerCase() == 'fieldset' ) <br />
tabs.push(prefChild[key]);<br />
}<br />
<br />
//<br />
// Create Widgets for all registered config keys<br />
//<br />
var w_div, w_label, w_ctrl, wt;<br />
for( var key in JSconfig.meta ) {<br />
w_div = document.createElement( 'DIV' );<br />
<br />
w_label = document.createElement( 'LABEL' );<br />
w_label.appendChild( document.createTextNode( JSconfig.meta[key].description ) )<br />
w_label.htmlFor = JSconfig.prefix + key;<br />
<br />
wt = typeof( JSconfig.meta[key].default_value );<br />
<br />
w_ctrl = document.createElement( 'INPUT' );<br />
w_ctrl.id = JSconfig.prefix + key;<br />
<br />
// before insertion into the DOM tree<br />
switch( wt ) {<br />
case 'boolean' : w_ctrl.type = 'checkbox'; break;<br />
case 'string' : w_ctrl.type = 'text'; break;<br />
}<br />
<br />
w_div.appendChild( w_label );<br />
w_div.appendChild( w_ctrl );<br />
tabs[JSconfig.meta[key].page].appendChild( w_div );<br />
<br />
// after insertion into the DOM tree<br />
switch( wt ) {<br />
case 'boolean' : w_ctrl.defaultChecked = w_ctrl.checked = JSconfig.keys[key]; break;<br />
case 'string' : w_ctrl.defaultValue = w_ctrl.value = JSconfig.keys[key]; break;<br />
}<br />
<br />
}<br />
addHandler(document.getElementById('preferences').parentNode, 'submit', JSconfig.evaluateForm );<br />
}<br />
}<br />
<br />
JSconfig.readCookies();<br />
addOnloadHook(JSconfig.setUpForm);<br />
<br />
/*</source>*/</div>Danimohttp://techbase.kde.org/Schedules/KDE4/4.1_Feature_PlanSchedules/KDE4/4.1 Feature Plan2008-01-29T23:13:50Z<p>Danimo: </p>
<hr />
<div>= KDE4.1 Feature Plan =<br />
<br />
== Instructions ==<br />
<br />
Deadline for adding entries here for the 4.1 release is xxx.<br><br />
Entries can be added after that date, but they may not be included with 4.1.<br />
<br />
todo => not started yet<br><br />
in-progress => started, but not completed yet<br><br />
done => completed<br />
<br />
=== kdebase-apps ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|- valign=top style="background-color: red;"<br />
| todo || fred || add foo to fred. foo will provide the ability to make fred do neat stuff, but only on Tuesday. For more info see [http://foo.org this link] || [mailto:john-doe@kde.org john doe@kde.org]<br />
|- valign=top style="background-color: yellow;"<br />
| in-progress || fred || add upside-down video support using the UDV library. || [mailto:john-doe@kde.org john doe@kde.org]<br />
|- valign=top style="background-color: yellow;"<br />
{{FeatureTodo|fred|fred needs this|wilma@kde.org}}<br />
{{FeatureInProgress|fred|fred needs this|wilma@kde.org}}<br />
{{FeatureDone|fred|fred needs this|wilma@kde.org}}<br />
|}</div>Danimohttp://techbase.kde.org/Template:FeatureDoneTemplate:FeatureDone2008-01-29T23:13:17Z<p>Danimo: </p>
<hr />
<div>{{feature|{{{1}}}|Done|{{{2}}}|{{{3}}}|green}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureInProgressTemplate:FeatureInProgress2008-01-29T23:12:39Z<p>Danimo: </p>
<hr />
<div>{{feature|{{{1}}}|in-progress|{{{2}}}|{{{3}}}|yellow}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTodoTemplate:FeatureTodo2008-01-29T23:12:21Z<p>Danimo: </p>
<hr />
<div>{{feature|{{{1}}}|todo|{{{2}}}|{{{3}}}|red}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTodoTemplate:FeatureTodo2008-01-29T23:11:53Z<p>Danimo: </p>
<hr />
<div>{{feature|{{{1}}}|todo}}}|{{{2}}}|{{{3}}}|red}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureInProgressTemplate:FeatureInProgress2008-01-29T23:11:17Z<p>Danimo: </p>
<hr />
<div>{{feature|{{{1}}}|in-progress}}}|{{{2}}}|{{{3}}}|yellow}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureInProgressTemplate:FeatureInProgress2008-01-29T23:10:04Z<p>Danimo: New page: {{feature|{{{1}}}|{{{2}}}|{{{3}}}|{{{4}}}|yellow}} <noinclude> Category:Template </noinclude></p>
<hr />
<div>{{feature|{{{1}}}|{{{2}}}|{{{3}}}|{{{4}}}|yellow}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureDoneTemplate:FeatureDone2008-01-29T23:09:44Z<p>Danimo: New page: {{feature|{{{1}}}|{{{2}}}|{{{3}}}|{{{4}}}|green}} <noinclude> Category:Template </noinclude></p>
<hr />
<div>{{feature|{{{1}}}|{{{2}}}|{{{3}}}|{{{4}}}|green}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Schedules/KDE4/4.1_Feature_PlanSchedules/KDE4/4.1 Feature Plan2008-01-29T23:09:02Z<p>Danimo: </p>
<hr />
<div>= KDE4.1 Feature Plan =<br />
<br />
== Instructions ==<br />
<br />
Deadline for adding entries here for the 4.1 release is xxx.<br><br />
Entries can be added after that date, but they may not be included with 4.1.<br />
<br />
todo => not started yet<br><br />
in-progress => started, but not completed yet<br><br />
done => completed<br />
<br />
=== kdebase-apps ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|- valign=top style="background-color: red;"<br />
| todo || fred || add foo to fred. foo will provide the ability to make fred do neat stuff, but only on Tuesday. For more info see [http://foo.org this link] || [mailto:john-doe@kde.org john doe@kde.org]<br />
|- valign=top style="background-color: yellow;"<br />
| in-progress || fred || add upside-down video support using the UDV library. || [mailto:john-doe@kde.org john doe@kde.org]<br />
|- valign=top style="background-color: yellow;"<br />
{{FeatureTodo|done|fred|fred needs this|wilma@kde.org}}<br />
|}</div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T23:08:43Z<p>Danimo: </p>
<hr />
<div>|- valign=top style="background-color: {{{5|white}}};"<br />
|{{{1|status missing}}}||{{{2|project issing}}}||{{{3|description missing}}}||[mailto:{{{4}}} {{{4|contact missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTodoTemplate:FeatureTodo2008-01-29T23:08:25Z<p>Danimo: </p>
<hr />
<div>{{feature|{{{1}}}|{{{2}}}|{{{3}}}|{{{4}}}|red}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T23:07:30Z<p>Danimo: </p>
<hr />
<div>|- valign=top style="background-color: {{{5|white}};"<br />
|{{{1|status missing}}}||{{{2|project issing}}}||{{{3|description missing}}}||[mailto:{{{4}}} {{{4|contact missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTodoTemplate:FeatureTodo2008-01-29T23:06:38Z<p>Danimo: </p>
<hr />
<div>{{feature|{{{1}}}|{{{2}}}|{{{3}}}|{{{3}}}|red}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTodoTemplate:FeatureTodo2008-01-29T23:05:59Z<p>Danimo: </p>
<hr />
<div>{{feature|{{{1}}}|{{{2}}}|{{{3}}}|{{{3}}}|red}}}<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T23:05:05Z<p>Danimo: </p>
<hr />
<div>|- valign=top style="background-color: {{{4|white}};"<br />
|{{{0|status missing}}}||{{{1|project issing}}}||{{{2|description missing}}}||[mailto:{{{3}}} {{{3|contact missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTodoTemplate:FeatureTodo2008-01-29T23:04:33Z<p>Danimo: New page: {{feature|{{{1}}}|{{{2}}}|{{{3}}}|{{{3}}}|red}}};" <noinclude> Category:Template </noinclude></p>
<hr />
<div>{{feature|{{{1}}}|{{{2}}}|{{{3}}}|{{{3}}}|red}}};"<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T23:02:41Z<p>Danimo: </p>
<hr />
<div>|- valign=top style="background-color: {{{color}}};"<br />
|{{{0|status missing}}}||{{{1|project issing}}}||{{{2|description missing}}}||[mailto:{{{3}}} {{{3|contact missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Schedules/KDE4/4.1_Feature_PlanSchedules/KDE4/4.1 Feature Plan2008-01-29T22:58:04Z<p>Danimo: </p>
<hr />
<div>= KDE4.1 Feature Plan =<br />
<br />
== Instructions ==<br />
<br />
Deadline for adding entries here for the 4.1 release is xxx.<br><br />
Entries can be added after that date, but they may not be included with 4.1.<br />
<br />
todo => not started yet<br><br />
in-progress => started, but not completed yet<br><br />
done => completed<br />
<br />
=== kdebase-apps ===<br />
{| class="wikitable sortable" border="1"<br />
|-<br />
! Status !! Project !! Description !! Contact<br />
|- valign=top style="background-color: red;"<br />
| todo || fred || add foo to fred. foo will provide the ability to make fred do neat stuff, but only on Tuesday. For more info see [http://foo.org this link] || [mailto:john-doe@kde.org john doe@kde.org]<br />
|- valign=top style="background-color: yellow;"<br />
| in-progress || fred || add upside-down video support using the UDV library. || [mailto:john-doe@kde.org john doe@kde.org]<br />
|- valign=top style="background-color: yellow;"<br />
{{feature|done|fred|fred needs this|wilma@kde.org}}<br />
|}</div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T22:57:15Z<p>Danimo: </p>
<hr />
<div>|- valign=top /*{{{0|pogress missing}}}*/<br />
|{{{1|status missing}}}||{{{2|project issing}}}||{{{3|description missing}}}||[mailto:{{{4}}} {{{4|contact missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T22:56:43Z<p>Danimo: </p>
<hr />
<div>|- valign=top /*{{{1|pogress missing}}}*/<br />
|{{{1|status missing}}}||{{{2|project issing}}}||{{{3|description missing}}}||[mailto:{{{4}}} {{{4|contact missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T22:54:13Z<p>Danimo: </p>
<hr />
<div>|- valign=top /*{{{1|pogress missing}}}*/<br />
|{{{0|status missing}}}||{{{2|project issing}}}||{{{3|description missing}}}||[mailto:{{{4}}} {{{4|contact missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T22:52:16Z<p>Danimo: </p>
<hr />
<div>|- valign=top /*{{{2|pogress missing}}}*/<br />
|{{{1|status missing}}}||{{{3|project issing}}}||{{{4|description missing}}}||[mailto:{{{5}}} {{{5|contact missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T22:51:37Z<p>Danimo: </p>
<hr />
<div>|- valign=top /*{{{2=progress|pogress missing}}}*/<br />
|{{{1=status|status missing}}}||{{{3=project|project issing}}}||{{{4=description|description missing}}}||[mailto:{{{5=contact}}} {{{5=contact|contact missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T22:46:17Z<p>Danimo: </p>
<hr />
<div>|- valign=top /*{{{2=progress|pogress missing}}}*/<br />
|{{{1=status|status missing}}}||{{{3=project|project missing}}}||{{{4=description|description missing}}}||[mailto:{{{5=contact}}} {{{5=contact|contact missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude><br />
<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T22:45:03Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|{{{1=status|status missing}}}{{{2=status|status missing}}}||{{{3=project|project missing}}}||{{{4=description|description missing}}}||[mailto:{{{5=contact}}} {{{5=contact|contact missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude><br />
<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T22:40:42Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|{{{1=status|status missing}}}||{{{2=project|project missing}}}||{{{3=description|description missing}}}||[mailto:{{{4=contact}}} {{{4=contact|contact missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T22:40:10Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|{{{0=status|status missing}}}||{{{1=project|project missing}}}||{{{2=description|description missing}}}||[mailto:{{{3=contact}}} {{{3=contact|contact missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T22:38:38Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|{{{1=status|status missing}}}||{{{2=project|project missing}}}||{{{3=description|description missing}}}||[mailto:{{{4=contact}}} {{{3=contact|contact missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T22:37:13Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
|{{{status|status missing}}}||{{{1=project|project missing}}}||{{{2=description|description missing}}}||[mailto:{{{3=contact}}} {{{3=contact|contact missing}}}]<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T22:28:13Z<p>Danimo: </p>
<hr />
<div>|- valign=top<br />
||{{{status|status missing}}}||{{{1=project|project missing}}}||{{{2=description|description missing}}}||[mailto:{{{3=contact}}} {{{3=contact|contact missing}}}]||<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T22:27:35Z<p>Danimo: </p>
<hr />
<div>||{{{status|status missing}}}||{{{1=project|project missing}}}||{{{2=description|description missing}}}||[mailto:{{{3=contact}}} {{{3=contact|contact missing}}}]||<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T22:27:09Z<p>Danimo: TechBase:Feature moved to Template:Feature: Upps</p>
<hr />
<div>|{{{status|status missing}}}|{{{1=project|project missing}}}|{{{2=description|description missing}}}|[mailto:{{{3=contact}}} {{{3=contact|contact missing}}}]|<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/TechBase:FeatureTechBase:Feature2008-01-29T22:27:09Z<p>Danimo: TechBase:Feature moved to Template:Feature: Upps</p>
<hr />
<div>#REDIRECT [[Template:Feature]]</div>Danimohttp://techbase.kde.org/Template:FeatureTemplate:Feature2008-01-29T22:17:56Z<p>Danimo: New Template for feature catalogue</p>
<hr />
<div>|{{{status|status missing}}}|{{{1=project|project missing}}}|{{{2=description|description missing}}}|[mailto:{{{3=contact}}} {{{3=contact|contact missing}}}]|<br />
<noinclude><br />
[[Category:Template]]<br />
</noinclude></div>Danimohttp://techbase.kde.org/User:Mschiff/Slashes_in_FilenamesUser:Mschiff/Slashes in Filenames2008-01-21T15:57:11Z<p>Danimo: /* The solution */</p>
<hr />
<div>This is about KDEs special feature of allowing slashes (/) in filenames.<br />
<br />
Date: 08/01/17<br />
<br />
=The problem=<br />
<br />
KDE allows filenames containing a slash (/).<br />
Technically it is not possible to have "/" in filenames because "/" is the filesystem path seperator.<br />
So KDE encodes filenames and saves the filename like in http URL encoding with "%2f" for every "/".<br />
<br />
I am convinced that this behavior is a bad idea and brings a lot of trouble. <br />
<br />
I will now try to explain why.<br />
<br />
* "/" is not an allowed character in filenames of UNIX filesystems<br />
* AFAICT there is no other known OS or Desktop Environment (DE) that allows this<br />
* "%2f" is a valid filename<br />
* Allowing "/" in filenames brings following problems:<br />
** its not possible to have files containing %2f in the name for whatever reason even if escaped to %%2f then it would not be possible to have a file called like %%2f and be presented like that if not escaped ad %%%2f ...and so on<br />
** KDE is not an isolated world. People using it want to communicate to other people and to share files with them.<br />
** Bad interoperability: sending files with "/" in it to other people will always end up as apparently broken filenames on other systems if its not KDE (Gnome, XFCE, CDE, Windows). This may damage KDE's reputation in a way that people may think that KDE produces broken file(name)s now and then.<br />
** konqueror lists files and has a location bar. It is possible to access files directly through that location bar. Now if there is a file called "foo/bar" (foo%2fbar on disk) and a directory called foo containing a file called bar: what will be selected if a user enters this in the location bar? what will the user expect to hit? Wouldnt that make eval things possible? The same applies to krunner or the file-dialog. Because of that encoded filenames have to be treated special in some places and produce an inconsistent user experience.<br />
<br />
* Krusader shows files as they are on disk (foo%2fbar)<br />
* ark shows files as they are in an archive (foo%2fbar)<br />
* users often use the console to manage files in a batch<br />
* KDE is not compatible with linux coreutils (cp,mv,...) if it decodes and encodes filenames in a way that it will confuse people by the fact that files shown by "ls" look differently than files shown by dolphin or konqueror although there are just plain us-ascii characters being used for the filenames.<br />
<br />
<br />
=The solution=<br />
<br />
=== Marcs solution ===<br />
<br />
I vote for just removing this feature to prevent all those problems described above and to solve the related bugreports.<br />
<br />
=== Davids solution ===<br />
I found a much better solution to allow '/' without all this escaping: using a unicode character that looks like a slash but that isn't '/': QChar(0x2044), also known as "FRACTION SLASH".Looks quite nice IMHO: http://web.davidfaure.fr/kde/slash.jpg<br />
<br />
Ah... of course there's one downside: if you name a file "http://www.kde.org" you can't copy paste that name into the webbrowser as a URL, since the slashes are not real slashes anymore. Oh well, corner case of the corner case..<br />
<br />
=Related bugreports=<br />
* https://bugs.kde.org/show_bug.cgi?id=51306<br />
* https://bugs.kde.org/show_bug.cgi?id=100516</div>Danimohttp://techbase.kde.org/Events/KDE4ReleaseParties/BonnEvents/KDE4ReleaseParties/Bonn2008-01-14T23:23:47Z<p>Danimo: Initial site layout</p>
<hr />
<div>== Participants ==<br />
* Daniel Molkentin<br />
* Peter Jung<br />
* Olaf Schmidt<br />
<br />
== Ideas ==<br />
<br />
Please feel free to add your ideas here!<br />
<br />
== ToDo ==<br />
<br />
* organize projector</div>Danimohttp://techbase.kde.org/Events/KDE4ReleasePartiesEvents/KDE4ReleaseParties2008-01-14T23:22:23Z<p>Danimo: /* Germany */</p>
<hr />
<div>= KDE 4 Release Parties =<br />
<br />
== Main Event in Mountain View ==<br />
<br />
January 17–19, 2008, on the Google Campus in Mountain View, California.<br />
<br />
[http://www.kde.org/kde-4.0-release-event/ More info on the main event.]<br />
<br />
== Other Events ==<br />
(World Map with Events)<br />
<br />
[http://maps.google.com/maps/ms?ie=UTF&msa=0&msid=103852430929072245482.0004436f32d21086c105d Release Events]<br />
<br />
(In lexicographical order)<br />
<br />
=== Australia ===<br />
<br />
==== Tasmania ====<br />
<br />
; Hobart :<br />
:Event: Coffeetime at Starbucks (there is only 1), Friday 11th January, 5:30pm<br />
:Contact: 'Sif Contact just turn up :D<br />
<br />
=== Brazil ===<br />
<br />
; Aracaju : Evento: KDE4 - Encontro dos usuários KDE de Sergipe<br />
:Localização: Shopping Jardins - Na nova praça de alimentação - Aracaju - SE - Brazil<br />
:Dia: 18/01<br />
:Quer ir, me contate: aragao.otavio@gmail.com<br />
<br />
=== Costa Rica ===<br />
<br />
; San Jose : Lanzamiento de KDE 4.0 por el grupo de usuarios de Linux de la Universidad Latina de Costa Rica, GCL.<br />
:Dia: 19/01/2008<br />
:contacto: panki@nativo.net<br />
<br />
=== Estonia ===<br />
<br />
; Tallinn :Üritus: Väike kohvi, väike õlu, väike snäkk, väike KDE.<br />
:Asukoht: Tallinn, [http://www.maurus.ee Mauruse Pubi] (Estonia Pst. 8).<br />
:Aeg: 18.01.2008, 18:00 EET<br />
:Kontakt: Suva ät linux punkt ee, viiskuusüksviisüheksaükskaheksaseitse.<br />
:Viide: [http://pingviin.org/viewtopic.php?p=27359 Teema pingviini foorumis]<br />
<br />
=== France ===<br />
<br />
; Toulouse : <br />
:Adresse : Centre Culturel Bellegarde, 17, rue Bellegarde à Toulouse<br />
:Dates : 25 janvier 20h (Discours d'A. Seigo retransmis en français, cocktail dînatoire) <br />
:26 janvier 9:00 - 18:00 (Présentations bibliothèques KDE4 et Qt, Solid, traductions, éducatif)<br />
:Contact : darktears31 AT gmail DOTcom<br />
:Website : http://www.toulibre.org/KDE4<br />
<br />
=== Germany ===<br />
<br />
; Berlin : <br />
:Event: Party at the KDAB Berlin office<br />
:Address: Adalbertstr. 7/8, Kreuzberg. U Kottbusser Tor. ([http://maps.google.de/maps?f=q&hl=en&time=&date=&ttype=&q=Adalbertstra%C3%9Fe+7,+Kreuzberg+10999+Berlin,+Berlin,+Berlin,+Germany&sll=51.124213,10.546875&sspn=14.085092,34.189453&ie=UTF8&cd=2&geocode=0,52.500538,13.418768&z=16&iwloc=addr&om=1 Google maps instructions])<br />
:Date: 18.1., 20.00<br />
:Please let us know if you're comming: kde4-release-party@kdab.net<br />
:Contact: till@kdab.net, ellen@reitmayr.net<br />
<br />
; Bonn :<br />
:Event: Party in Netzladen (http://www.netzladen.org)<br />
:Address: Wolfstr. 10<br />
:Arrival: http://www.netzladen.org/home/anfahrt<br />
:Date: 18.01., 19:00h<br />
:Contact: danimo (at) kde.org<br />
:Plannung: [[Events/KDE4ReleaseParties/Bonn]] (add yourself!)<br />
<br />
; Hamburg : <br />
:Event: Party in the rooms of freiheit.com (http://www.freiheit.com/)<br />
:Address: Straßenbahnring 22, Hoheluft-Ost<br />
:Date: 18.01., 19:00h<br />
:Contact: sven ( at) community-org.de<br />
<br />
; Stuttgart : <br />
:Event: Linux Day at the HdM Stuttgart (Stuttgart Media University) <br />
:[http://www.hdm-stuttgart.de/aktuell/terminkalender/view_terminfooter?terminid=event20071211101808 Announcement]<br />
:Live Stream: mms://stream.mi.hdm-stuttgart.de/linuxday_jan08<br />
:Contact: mail@bernhardrode.de<br />
:News, Chat and Live Coverage: http://www.linux-day.de<br />
<br />
=== India ===<br />
; Chennai :<br />
:Event: KDE 4 Release party at NRCFOSS, AU-KBC Research centre,MIT,chromepet .<br />
:Add your name in wiki http://nrcfosshelpline.in/code/wiki/kde4releaseparty<br />
:Date:20/01/2008<br />
:contact:pavithran.s@gmail.com<br />
<br />
=== Portugal ===<br />
<br />
; Aveiro : UA KDE4.0 festa de apresentação<br />
:Dia: 15/02<br />
:contacto: nuno@oxygen-icons.org</div>Danimohttp://techbase.kde.org/Events/KDE4ReleasePartiesEvents/KDE4ReleaseParties2008-01-14T19:34:14Z<p>Danimo: Party in Bonn</p>
<hr />
<div>= KDE 4 Release Parties =<br />
<br />
== Main Event in Mountain View ==<br />
<br />
January 17–19, 2008, on the Google Campus in Mountain View, California.<br />
<br />
[http://www.kde.org/kde-4.0-release-event/ More info on the main event.]<br />
<br />
== Other Events ==<br />
(World Map with Events)<br />
<br />
[http://maps.google.com/maps/ms?ie=UTF&msa=0&msid=103852430929072245482.0004436f32d21086c105d Release Events]<br />
<br />
(In lexicographical order)<br />
<br />
=== Australia ===<br />
<br />
==== Tasmania ====<br />
<br />
; Hobart :<br />
:Event: Coffeetime at Starbucks (there is only 1), Friday 11th January, 5:30pm<br />
:Contact: 'Sif Contact just turn up :D<br />
<br />
=== Brazil ===<br />
<br />
; Aracaju : Evento: KDE4 - Encontro dos usuários KDE de Sergipe<br />
:Localização: Shopping Jardins - Na nova praça de alimentação - Aracaju - SE - Brazil<br />
:Dia: 18/01<br />
:Quer ir, me contate: aragao.otavio@gmail.com<br />
<br />
=== Costa Rica ===<br />
<br />
; San Jose : Lanzamiento de KDE 4.0 por el grupo de usuarios de Linux de la Universidad Latina de Costa Rica, GCL.<br />
:Dia: 19/01/2008<br />
:contacto: panki@nativo.net<br />
<br />
=== Estonia ===<br />
<br />
; Tallinn :Üritus: Väike kohvi, väike õlu, väike snäkk, väike KDE.<br />
:Asukoht: Tallinn, [http://www.maurus.ee Mauruse Pubi] (Estonia Pst. 8).<br />
:Aeg: 18.01.2008, 18:00 EET<br />
:Kontakt: Suva ät linux punkt ee, viiskuusüksviisüheksaükskaheksaseitse.<br />
:Viide: [http://pingviin.org/viewtopic.php?p=27359 Teema pingviini foorumis]<br />
<br />
=== France ===<br />
<br />
; Toulouse : <br />
:Adresse : Centre Culturel Bellegarde, 17, rue Bellegarde à Toulouse<br />
:Dates : 25 janvier 20h (Discours d'A. Seigo retransmis en français, cocktail dînatoire) <br />
:26 janvier 9:00 - 18:00 (Présentations bibliothèques KDE4 et Qt, Solid, traductions, éducatif)<br />
:Contact : darktears31 AT gmail DOTcom<br />
:Website : http://www.toulibre.org/KDE4<br />
<br />
=== Germany ===<br />
<br />
; Berlin : <br />
:Event: Party at the KDAB Berlin office<br />
:Address: Adalbertstr. 7/8, Kreuzberg. U Kottbusser Tor. ([http://maps.google.de/maps?f=q&hl=en&time=&date=&ttype=&q=Adalbertstra%C3%9Fe+7,+Kreuzberg+10999+Berlin,+Berlin,+Berlin,+Germany&sll=51.124213,10.546875&sspn=14.085092,34.189453&ie=UTF8&cd=2&geocode=0,52.500538,13.418768&z=16&iwloc=addr&om=1 Google maps instructions])<br />
:Date: 18.1., 20.00<br />
:Please let us know if you're comming: kde4-release-party@kdab.net<br />
:Contact: till@kdab.net, ellen@reitmayr.net<br />
<br />
; Hamburg : <br />
:Event: Party in the rooms of freiheit.com (http://www.freiheit.com/)<br />
:Address: Straßenbahnring 22, Hoheluft-Ost<br />
:Date: 18.01., 19:00h<br />
:Contact: sven ( at) community-org.de<br />
<br />
; Stuttgart : <br />
:Event: Linux Day at the HdM Stuttgart (Stuttgart Media University) <br />
:[http://www.hdm-stuttgart.de/aktuell/terminkalender/view_terminfooter?terminid=event20071211101808 Announcement]<br />
:Live Stream: mms://stream.mi.hdm-stuttgart.de/linuxday_jan08<br />
:Contact: mail@bernhardrode.de<br />
:News, Chat and Live Coverage: http://www.linux-day.de<br />
<br />
; Bonn :<br />
:Event: Party in Netzladen (http://www.netzladen.org)<br />
:Address: Wolfstr. 10<br />
:Arrival: http://www.netzladen.org/home/anfahrt<br />
:Date: 18.01., 19:00h<br />
:Contact: danimo (at) kde.org<br />
<br />
=== India ===<br />
; Chennai :<br />
:Event: KDE 4 Release party at NRCFOSS, AU-KBC Research centre,MIT,chromepet .<br />
:Add your name in wiki http://nrcfosshelpline.in/code/wiki/kde4releaseparty<br />
:Date:20/01/2008<br />
:contact:pavithran.s@gmail.com<br />
<br />
=== Portugal ===<br />
<br />
; Aveiro : UA KDE4.0 festa de apresentação<br />
:Dia: 15/02<br />
:contacto: nuno@oxygen-icons.org</div>Danimohttp://techbase.kde.org/Development/Tutorials/CMake_(de)Development/Tutorials/CMake (de)2008-01-04T09:04:02Z<p>Danimo: Better translation</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Development/Tutorials/CMake}}<br />
<br />
{{TutorialBrowser (de)|<br />
<br />
series=Grundlagen|<br />
<br />
name=CMake|<br />
<br />
}}<br />
<br />
== Zusammenfassung ==<br />
CMake ist das Build-System, das KDE benutzt. Diese Anleitung beschreibt, wie man CMake benutzt und wie man die Projektdateien schreibt.<br />
<br />
== Einführung ==<br />
CMake liest Script Dateien ein und gibt Eingabedateien für das native Buildsystem der Platform auf der es läuft aus. Es kann GNU Makefiles, KDevelop Projekt Dateien, XCode Projekt Dateien und Visual Studio Projekt Dateien ausgeben. <br />
<br />
CMake ist freie Software, die unter einer BSD-artigen Lizenz veröffentlicht wird. Entwickelt wird es von [http://www.kitware.com Kitware Inc.]<br />
<br />
Hier einige Links, wo man etwas über CMake im Allgemeinen lernen kann (meist englisch):<br />
* [http://www.cmake.org/HTML/Documentation.html CMake Manual]<br />
* [http://www.cmake.org/Wiki/CMake CMake Wiki]<br />
* [http://www.cmake.org/Wiki/CMake_HowToDoPlatformChecks CMake System Checks ]<br />
* [http://www.cmake.org/Wiki/CMake_HowToFindInstalledSoftware Finding Optional Packages ]<br />
* [http://www.cmake.org/Wiki/HowToBuildKDE4Software KDE 4 Tutorial at the CMake Wiki ]<br />
* [http://www.cmake.org/Wiki/CMake_FAQ CMake FAQ]<br />
* [http://mail.kde.org/pipermail/kde-buildsystem/ The kde-buildsystem Mailing List Archive]<br />
<br />
Es gibt auch eine [http://www.cmake.org/mailman/listinfo/cmake CMake Mailing List].<br />
<br />
== Warum man CMake benutzen sollte ==<br />
CMake ist nach einer Entscheidung im März 2006 das offizielle Werkzeug von KDE 4, vorwiegend aus technischen Vorteilen gegenüber den älteren KDE Werkzeugen ''automake'' und ''unsermake'':<br />
<br />
* CMake wird unabhänging von KDE entwickelt und kann auch von anderen Projekten benutzt werden.<br />
* Die Übersetzungszeit verkürzt sich durch CMake, hauptsächlich weil ''libtool'' nicht mehr benutzt wird. <br />
* Die CMake-Dateien sind einfacher zu schreiben.<br />
<br />
== Wie man KDE mit Hilfe von CMake übersetzt==<br />
<br />
=== CMake herunterladen und installieren ===<br />
<br />
==== Linux, BSD und andere Unix Systeme ====<br />
Die neuste Version von CMake kann von [http://www.cmake.org/HTML/Download.html] heruntergeladen werden.<br />
<br />
Einmal heruntergeladen, muss es entpackt und übersetzt werden:<br />
<code><br />
$ mkdir cmake-build<br />
$ cd cmake-build<br />
$ ../bootstrap<br />
$ make<br />
$ make install<br />
</code><br />
<br />
Standardmäßig wird CMake in /usr/local installiert, daher muss /usr/local/bin in Pfad für ausführbare Dateien stehen. Um das Installationspräfix zu ändern (z.B. in /usr in debian), muss die '--prefix=PATH' Option zum bootstrap Kommando hinzugefügt werden.<br />
<br />
Möchte man die aktuelle Entwicklerversion von CMake benutzen, findet man [http://cmake.org/HTML/Download.html#cvs hier] eine Anleitung.<br />
<br />
==== Windows ====<br />
Neuste Version von CMake von [http://www.cmake.org/HTML/Download.html hier] herunterladen.<br />
<br />
Dann den Cmake-Installer aufrufen<br />
<br />
Standardmäßig wird CMake in C:\$(Program Files)\CMake 2.4 installiert.<br />
<br />
Möchte man die aktuelle Entwicklerversion von CMake benutzen, findet man [http://cmake.org/HTML/Download.html#cvs hier] eine Anleitung.<br />
<br />
=== CMake ausführen===<br />
<br />
==== Linux, BSD, and other Unix Systems ====<br />
Um die Build-Dateien für das System zu erzeugen, muss CMake aufgerufen werden. Sowohl Übersetzungsvorgänge innerhalb des Codes als auch in einem gesonderten werden von CMake unterstützt, wobei KDE derzeit einen Übersetzungsvorgang innerhalb des Quellcodes verbietet. <br />
<br />
Hat man zum Beispiel kdelibs/ in ~/src/kdelibs/, dann ruft man folgende Befehle auf:<br />
<code><br />
$ ls<br />
kdelibs/<br />
$ mkdir kdelibs-build<br />
$ cd kdelibs-build<br />
$ cmake ../kdelibs<br />
</code><br />
Das wird die Makefiles im Verzeichnis kdelibs-build erzeugen, die zum Übersetzen von kdelibs benötigt werden.<br />
<br />
==== Windows ====<br />
Um die Build-Dateien für das System zu erzeugen, muss CMake aufgerufen werden. Sowohl Übersetzungsvorgänge innerhalb des Codes als auch in einem gesonderten werden von CMake unterstützt, wobei KDE derzeit einen Übersetzungsvorgang innerhalb des Quellcodes verbietet. <br />
<br />
Hat man zum Beispiel kdelibs\ in c:\daten\kde4, dann ruft man folgende Befehle auf:<br />
<code><br />
c:\daten\kde4> cd kdelibs\win<br />
c:\daten\kde4> cmake<br />
c:\daten\kde4> make <br />
c:\daten\kde4> make install<br />
c:\daten\kde4> cd ..<br />
c:\daten\kde4> mkdir kdelibs-build<br />
c:\daten\kde4> cd kdelibs-build<br />
c:\daten\kde4\kdelibs-build> cmake ..\kdelibs<br />
</code><br />
<br />
Dadurch werden die Makefiles, um kdelibs\ zu erzeugen in kdelibs-build angelegt. Siehe auch [[KDE On Windows]] für mehr Informationen über das Übersetzen von KDE unter Windows.<br />
<br />
==== Projektdateien für KDevelop ====<br />
Benötigen Sie Projektdateien für KDevelop (was einfache Makefile mit einigen zusätzlichen Extradateien für KDevelop sind), rufen Sie folgenden Befehl auf:<br />
<code><br />
$ cmake ../kdelibs -GKDevelop3<br />
</code><br />
Mit 'cmake -h' kann man herausfinden, welche Generatoren CMake unterstützt und welche weiteren Optionen es gibt.<br />
<br />
==== CMake und Qt4 ====<br />
Um Qt 4 zu finden sucht CMake nach qmake im Pfad für ausführbare Dateien. CMake benutzt ''nicht'' die QTDIR Umgebungsvariable. Daher müssen Sie sicherstellen, dass das erste qmake, welches im Pfad gefunden wird dasjenige ist, welches benutzt werden soll (also bei Parallelinstallationen von Qt3 und Qt4 entsprechend Qt4 zuerst gefunden wird).<br />
<br />
==== Mehr Details ====<br />
Wenn CMake seine Arbeit beendet hat, existiert eine Datei namens "CMakeCache.txt". Diese Datei enthält alle Einstellungen, die von CMake auf dem System entdeckt worden sind. Soll CMake mit einem anderen Generator aufgerufen werden oder das System neu untersucht werden, löschen Sie diese Datei.<br />
Wenn CMake etwas nicht findet, aber Sie wissen, dass es auf Ihrem System ist, können Sie CMake manuell mitteilen, wo man es findet. CMake benutzt Variablen um diese Information zu speichern und zwar in der eben erwähnten CMakeCache.txt Datei. Es gibt drei Möglichkeiten, diese Variablen manuell einzustellen:<br />
<br />
* CMake den korrekten Wert über die Kommandozeile mitteilen:<br />
cmake ../kdelibs -DNAME_OF_THE_VARIABLE=value<br />
* ccmake benutzen, welches eine auf curses basierende GUI aufruft, um CMake Variablen zu setzen ((run: ccmake ../kdelibs)<br />
* Die Datei CMakeCache.txt direkt bearbeiten (wird nicht empfohlen)<br />
<br />
Sie sollten "ccmake ../kdelibs" mindesten einmal aufrufen, so dass Sie einen Eindruck bekommen, welche Variable CMake benutzt. Drücken Sie "T" um die "fortgeschrittenen" Variablen zu sehen. Wenn also CMake etwas bestimmtes nicht von sich aus findet, rufen Sie ccmake auf und stellen Sie es von Hand ein.<br />
<br />
==== Kommandozeilenvariablen ====<br />
<br />
Folgende cmake Kommandozeilenvariablen könnten für Sie von Interesse sein:<br />
* '''CMAKE_INSTALL_PREFIX''': cmake ../kdelibs -DCMAKE_INSTALL_PREFIX=/opt/kde4 entspricht dem früheren ./configure --prefix=/opt/kde4<br />
* '''CMAKE_BUILD_TYPE''': Hier kann man sich aussuchen, welche Debug-Informationen erzeugt werden sollen. Folgende Möglichkkeiten gibt es:<br />
** "debugfull"<br />
** "debug"<br />
** "profile"<br />
** "relwithdebinfo" <br />
** "release". <br />
Voreinstellung ist "relwithdebinfo" (-O2 -g). Siehe auch FindKDE4Internal.cmake für weitere Details.<br />
* '''KDE4_BUILD_TESTS=ON''': erzeugt Makefiles die zusätzliche Testprogramme erzeugen und auch das Ziel 'test' zur Verfügung stellen.<br />
* '''KDE4_TEST_OUTPUT=xml''': Unit tests, die das QTestLib Framework benutzen werden xml-formatierte Logfiles erzeugen.<br />
* '''KDE4_DISABLE_MULTIMEDIA=ON''': Erzeugt KDE ohne jegliche Multimediaunterstützung (Audio und Video)<br />
* '''RPATH_STYLE''': Diese Kommandozeilenoption gibt es nicht mehr. Per Voreinstllung wird alles mit einem korrekten RPATH erzeugt. Möchten Sie RPATH nicht, setzten Sie CMAKE_SKIP_RPATH auf TRUE.<br />
* '''BUILD_foo=OFF''': Schaltet die Erzeugung im Unterverzeichnis 'foo' ab.<br />
* '''WITH_foo''': Hier gibt es mehrere Möglichkeiten, z.B. WITH_CUPS oder WITH_Jasper. Wenn Sie diese Punkte ausschalten, wird CMake nicht versuchen, die Pakete zu finden, ansonsten sucht CMake danach. Schlägt das Fehl, kann man wie oben beschrieben manuell nachhelfen.<br />
<br />
=== Umgebungsvariablen ===<br />
Wenn sich Header oder Bibliotheken an einem nicht-standarisierten Ort befinden, den CMake nicht findenkann (so wird zum Beispiel fink auf Mac OSX in /sw installiert), kann man folgendende Umgebungsvariablen setzen. Trotz der ähnlichen Namensgebung, funktionieren diese nicht als Kommandozeilenparameter für CMake: <br />
<br />
* '''CMAKE_INCLUDE_PATH''', Beispiel: export CMAKE_INCLUDE_PATH=/sw/include<br />
* '''CMAKE_LIBRARY_PATH''', Beispiel: export CMAKE_LIBRARY_PATH=/sw/lib<br />
<br />
Mehr Informationen über Umgebungsvariablen <br />
[http://www.cmake.org/Wiki/CMake_Useful_Variables hier]<br />
<br />
=== Nach dem Aufruf von CMake ===<br />
Schließt cmake mit der Meldung "Generating done" ab, gab es keine Fehler. Schließt es jedoch mit "Configuring done" ab, gab es Fehler, die es zu beheben gilt. Wenn cmake erfolgreich durchgelaufen ist, rufen Sie das entsprechende Werkzeug zur weiteren Bearbeitung auf (z.B. make, KDevelop, XCode oder MSVC). Das Ziel wird erzeugt, warten Sie bis die Erzeugung abgeschlossen ist. Anschließend können Sie z.B. "make install" aufrufen.<br />
<br />
Gibt es eine Fehlermeldung der Art<br />
<code><br />
CMake Error: This project requires some variables to be set,<br />
and cmake can not find them.<br />
Please set the following variables:<br />
X11_XTest_LIB (ADVANCED)<br />
</code><br />
kann es an einer fehlenden Bibliothek oder anderen Abhängigkeit liegen. Um herauszufinden, welche Bibliothek, suchen Sie im Verzeichnis cmake/modules nach der Variable, die cmake nicht finden kann. Im obigen Beispiel ist das<br />
<code><br />
FIND_LIBRARY(X11_XTest_LIB Xtst ${X11_LIB_SEARCH_PATH})<br />
</code><br />
Also fehlt die Biblothek Xtst. Diese muss ggf. nachinstalliert werden oder der Pfad dahin angegeben werden (s.o.). Anschließend rufen Sie cmake erneut auf.<br />
<br />
== CMake für eine einfache Applikation anwenden ==<br />
<br />
Die einfachste CMakeLists.txt Datei ist folgende:<br />
<code><br />
add_executable(hello main.cpp)<br />
</code><br />
Dadurch wird aus der Quelldatei "main.cpp" eine ausführbare Datei namens "hello" (oder "hello.exe" unter Windows) erzeugt. C und C++ Dateien können vermischt werden, wenn das gewünscht wird. Es kann mehrere ausführbare Dateien und/oder Bibliotheken in einer CMakeLists.txt Datei geben. Die selbe Quelldatei kann in mehreren Zielen benutzt werden, es wird für jedes Ziel unabhängig von anderen Zielen erzeugt. Der vielleicht interessanteste Teil an der CMake-Sprache sind die Variablen:<br />
<code><br />
SET( MY_SOURCES main.cpp widget.cpp)<br />
MESSAGE(STATUS "my sources: ${MY_SOURCES}")<br />
</code><br />
Mit dem SET() Kommando werden die Werte von Variblen gesetzt. Wenn Sie mehr als eine Zeichenkette übergeben, wird die Variable als Liste gesetzt. Eine Liste ist eine Liste von Zeichenketten, die durch Semikolon getrennt sind. Haben Sie nur einen Eintrag, wird die Variable nur auf diesen einen Wert gesetzt. Um den Wert einer Variable zu ermitteln, benutzen Sie ${VAR}. Eine Liste kann mit FOREACH() iteriert werden:<br />
<code><br />
FOREACH(next_ITEM ${MY_SOURCES})<br />
MESSAGE(STATUS "next item: ${next_ITEM}")<br />
ENDFOREACH(next_ITEM ${MY_SOURCES})<br />
</code><br />
Groß- und Kleinschreibung wird in CMake Kommandos ignoriert, jedoch in Variablen und den Namen von Parametern unterschieden.<br />
<br />
Man kann auch auf verschiedene Werte testen:<br />
<code><br />
IF (UNIX)<br />
MESSAGE(STATUS "This is UNIX (including OS X and CygWin)")<br />
ENDIF (UNIX)<br />
<br />
IF (MSVC)<br />
SET(MY_SRCS ${MY_SRCS} winextra.cpp)<br />
ENDIF (MSVC)<br />
</code><br />
Das zweite Beispiel zeigt gleichzeitig, wie man Einträge zu einer Liste hinzufügt.<br />
<br />
Es gibt auch in der CMake Wiki eine lesenswerte [http://www.cmake.org/Wiki/HowToBuildKDE4Software Anleitung], die erläutert, wie man cmake benutzt, um KDE 4 Software zu erzeugen. <br />
<br />
== CMake für ein KDE 4 Projekt benutzen ==<br />
<br />
Folgendes Beispiel demonstriert eine einfache CMakeList.txt Datei für ein kleines KDE 4 Projekt:<br />
<code><br />
PROJECT(kde4project)<br />
FIND_PACKAGE(KDE4 REQUIRED)<br />
INCLUDE_DIRECTORIES( ${KDE4_INCLUDES} )<br />
<br />
SET(KDE4ProjectSources kde4mainapp.cpp someclass.cpp someotherclass.cpp)<br />
<br />
KDE4_ADD_EXECUTABLE(kde4project ${KDE4ProjectSources} )<br />
<br />
TARGET_LINK_LIBRARIES(kde4project ${KDE4_KDEUI_LIBS} ${KDE4_KPARTS_LIBS} )<br />
</code><br />
<br />
Variablen, Makros und andere nützliche Informationen spezifisch für KDE kann unter [[Development/KDE and CMake Together]] gefunden werden.<br />
<br />
== CMake erweitern ==<br />
CMake kann mit cmake-Skripten erweitert werden. Es werden eine Reihe von Scripten mitgeliefert, die unter UNIX standardmäßig unter /usr/local/share/CMake/Modules/ installiert werden. Die KDE-Bibliotheken installieren selber einen Satz CMake-Module nach share/apps/cmake/modules/. Die Dateien dort werden denjenigen im globalen Modulpfad von cmake vorgezogen.<br />
<br />
Um Software-Pakete zu finden, gibt es FindFOO.cmake Dateien, siehe [http://www.cmake.org/Wiki/CMake_HowToFindInstalledSoftware hier] für weitere Informationen.<br />
Sie können auch Makros in CMake schreiben. Diese sind mächtig genug, die meisten Dinge zu erledigen, die Sie benötigen, um Software zu erstellen, sind jedoch nicht dazu konzipiert, als allgemeine Programmiersprache zu dienen.<br />
<br />
== autotools-basierte KDE Software nach CMake konvertieren ==<br />
In kdesdk/cmake/ gibt es ein Skript namens am2cmake. Da es sich um ein Ruby-Script handelt, muss ruby installiert sein. Rufen Sie am2cmake im obersten Verzeichnis ihres Projektes auf:<br />
<code><br />
$ cd src/mykooltool/<br />
$ am2cmake --kde4<br />
</code><br />
Vergessen Sie nicht den Schalter "--kde4", sonst werden keine für KDE 4 Software passenden Dateien erzeugt. Die erzeugten Dateien 'könnten' so wie sind funktieren, doch bei komplizierteren Projekten wird in der Regel zusätzliche Bearbeitung notwendig sein.<br />
<br />
Es könnte sein, dass<br />
* mit INCLUDE_DIRECTORIES() weitere benötigte Verzeichnisse hinzugefügt werden müssen<br />
* mit TARGET_LINK_LIBRARIES() zusätzliche Bibliotheken angeben werden müssen, die mit dem Projekt verlinkt werden müssen. <br />
* mit ADD_DEFINITIONS() zusätzliche Compiler-Schalter gesetzt werden müssen<br />
* einige zusätzliche "configure" Prüfungen gesetzt werden müssen, siehe auch [http://www.cmake.org/Wiki/CMake_HowToDoPlatformChecks How To Do Platform Checks] und [http://www.cmake.org/Wiki/CMake_HowToFindInstalledSoftware How To Find Installed Software]<br />
* Sie sich den sog. "convenience libraries" von libtool gesondert annehmen müssen. Diese werden von cmake nicht unterstützt, statt dessen wird eine Datei namens ConvenienceLibs.cmake created erzeugt. In dieser Datei finden Sie für jede einzelne "convenience library" eine einzelne Variable, welche alle Quelldateien für diese Bibliothek beinhaltet. Für Ziele, die mit diesen Bibliotheken verlinkt werden, fügen Sie einfach die Variable zu den Quellen hinzu. <br />
* Eine Datei namens AdditionalInfo.txt wird erzeugt. Hier werden alle *.in und *.in.in Dateien des Projektes aufgelistet. Die Aufgaben in diesen Dateien müssen von Hand nach cmake konvertiert werden.<br />
<br />
== Häufig gestellte Fragen (FAQs) ==<br />
<br />
=== Wie kann ich meinem bevorzugten Editor beibringen, die CMake Syntax hevorzuheben? ===<br />
Lesen Sie [http://www.cmake.org/Wiki/CMake_Editors_Support CMake Editors Support]. Hier wird beschrieben, wie man Emacs (auch XEmacs), VIM, Kate, KWrite, and KDevelop anpasst.<br />
<br />
=== Ich benötige einige Dateien während des Übersetzen erzeugt. Wie bewerkstellige ich das? ===<br />
Fügen Sie ADD_CUSTOM_COMMAND() hinzu. Das wird im CMake wiki erklärt: [http://www.cmake.org/Wiki/CMake_FAQ#How_can_I_generate_a_source_file_during_the_build.3F How can I generate a source file during the build]<br />
<br />
=== Ich benötige ausführbare Dateien, die im späteren Übersetzungsvorgang bestimmte Dateien erzeugen. Wie mache ich das? ===<br />
Nehmen wir an die ausführbare Datei heißt genembed. Benutzen Sie KDE4_ADD_EXECUTABLE(foo RUN_UNINSTALLED ${fooSources}) um diese ausführbare Datei zu erzeugen. Die RUN_UNINSTALLED Option ist wichtig, da die ausführbare Datei vom build Verzeichnis aus aufgerufen wird und Bibliotheken in diesem Verzeichnis benötigt. Um das zu bewerkstelligen, wird die ausführbare Datei wird mit einem entsprechend gesetztem RPATH kompiliert, und ein Wrapper Shell Skript erzeugt, welches genau so heißt wie die ausführbare Datei nur mit der Endung ".sh". Diese Script setzt die Variable LD_LIBRARY_PATH und ruft die eigentliche ausführbare Datei auf<br />
<br />
Benutzen Sie dieses Script im oben beschriebenen ADD_CUSTOM_COMMAND(). Sie könnnen den Namen und den Pfad ermittelt, indem Sie die Eigenschaft WRAPPER_SCRIPT abfragen. Das hier ist ein vollständiges Beispiel aus kdelibs/kstyles/keramik/ :<br />
<code><br />
# build the executable<br />
KDE4_ADD_EXECUTABLE(genembed RUN_UNINSTALLED ${genembed_SRCS})<br />
<br />
# get the name of the generated wrapper script (which sets up LD_LIBRARY_PATH)<br />
GET_TARGET_PROPERTY(GENEMBED_EXECUTABLE genembed WRAPPER_SCRIPT)<br />
<br />
# and the custom command<br />
ADD_CUSTOM_COMMAND(OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/keramikrc.h<br />
COMMAND ${GENEMBED_EXECUTABLE} --file ${CMAKE_CURRENT_BINARY_DIR}/keramikPics.txt > \<br />
${CMAKE_CURRENT_BINARY_DIR}/pixmaps.keramik<br />
DEPENDS genembed ${keramikPics}<br />
)<br />
</code><br />
<br />
Wie Sie sehen, ist genembed auch als Abhängigkeit gelistet. Das heißt, dass cmake weiß, daß es diese Datei erzeugen muss, bevor diese Regel aushgeführt wird. <br />
<br />
=== Ich möchte statt der -DCMAKE_INSTALL_PREFIX Kommandozeilenoptionen lieber die KDEDIR Umgebungsvariable benutzen. Wird das von CMake unterstützt? ===<br />
Nein. $KDEDIR ist in KDE4 veraltet.<br />
<br />
=== Warum bekomme ich Compilerfehler wie /usr/lib/qt4/include/QtCore/qstring.h:536: undefined reference to `QString::fromLatin1_helper(char const*, int)'? ===<br />
A: Wenn Sie eine alte Qt4 Version im qt/lib Verzeichnis installiert haben, müssen die alten (4.0.1) Dateien gelöscht werden.<br />
<br />
=== Wie kann ich cmake anweisen, mehr Makefiles mit mehr Ausgaben zu erzeugen. Ich möchte genau sehen, welche Kommandos während des Make-Prozesses ausgeführt werden ===<br />
Übergeben Sie einfach die VERBOSE Variable zu make, z.B.<br />
<code><br />
% make VERBOSE=1<br />
</code><br />
oder<br />
<code><br />
% VERBOSE=1 make<br />
</code><br />
<br />
Nähere Informationen können dem Artikel [http://www.cmake.org/Wiki/CMake_FAQ#Is_there_an_option_to_produce_more_.27verbose.27_compiling.3F Is there an option to produce more 'verbose' compiling?] entnommen werden.<br />
<br />
=== Es gibt kein 'make distclean' Ziel in den erzeugten Makefiles. Wie kann ich das Projekt einschließlich der Cache-Dateien komplett neu erzeugen? ===<br />
Entfernen Sie einfach das build Verzeichnis oder den Inhalt dieses Verzeichnisses.<br />
<br />
[[Category:Programming]]<br />
[[Category:Tutorial]]<br />
[[Category:FAQs]]</div>Danimohttp://techbase.kde.org/User:DanimoUser:Danimo2007-12-20T14:55:01Z<p>Danimo: </p>
<hr />
<div>== Subpages ==<br />
<br />
{{List_subpages}}<br />
<br />
== TODO ==<br />
<br />
* Beautify Subpage titles<br />
<br />
<br />
== Bugs ==<br />
sorry for reporting a bug here; but this seems like as good a place as any :)<br />
When using <nowiki><code cpp></nowiki> tags I noted a bug. Specifically when you use the colon (or other means) to indent it. [[User:Zander|Zander]] 20:39, 9 April 2007 (CEST)<br />
Example code:<br />
<br />
:<code cpp><br />
#include <iostream><br />
#include <QtCore/QDate><br />
#include <zlib.h><br />
</code><br />
<br />
== Edges in KDE 4 ==<br />
<br />
What I found when installing the openSUSE packages and how I think we could go about it: [[User:Danimo/Edges in KDE 4]]</div>Danimohttp://techbase.kde.org/Projects/KDE_RelicensingProjects/KDE Relicensing2007-11-10T10:38:42Z<p>Danimo: </p>
<hr />
<div>== KDE GPL v2.0 Relicensing effort ==<br />
<br />
=== Why does it matter ? ===<br />
<br />
A couple of KDE dependent projects or even libraries have moved or are going to move to GPLv3 ([http://gpl3.palamida.com:8080/ State of GPLv3 movement]). <br />
<br />
Unfortunately, GPL v3 is incompatible with GPL v2. This means that it is not possible to create a project linking GPL v2 and v3 code together. There is no problem for projects which are licensed GPLv2+ (version 2 or above).<br />
<br />
A few parts of KDE are currently licensed as GPLv2 only. So far we have no reason to believe that this was something other than an oversight. However, we still need to validate with the individual copyright holders that a relicense to GPLv2+ or GPLv2+v3 is okay with them. <br />
<br />
Therefore, in an effort we're trying to identify the contributors that have contributed under the terms of GPLv2 and where the "+" part was not explicetly mentioned. If we know that all contributors agreed to a relicense, we can go ahead and flip the license of the individual source file.<br />
<br />
== How can I help ? ==<br />
<br />
By identifying a contributor who as contributed under the terms of GPLv2 (use kdesdk/scripts/relicensecheck.pl on the file in question), and contacting him if he wasn't already contacted. Ask him the following questions: <br />
<br />
* Are you okay with relicensing your contributions done under GPLv2 to GPLv2+?<br />
<br />
* Are you okay with relicensing your contributions done under GPLv2 to GPLv2 or GPLv3 ?<br />
<br />
* Are you okay with relicensing your contributions done under LGPLv2 to LGPLv2+?<br />
<br />
* Are you okay with relicensing your contributions done under LGPLv2 to LGPLv2 or LGPLv3?<br />
<br />
* Are you okay with the KDE e.V. deciding on a future licensing change to your code, should that be necessary?<br />
<br />
=== Whats next? ===<br />
<br />
# you checkout relicensecheck.pl from trunk/KDE/kdesdk/scripts<br />
# you run it on the file or directory in question<br />
# you interpret the result. check each commit that is being complained about carefully. Try to get the copyright's holder's permission. if you get it, update the whitelist in the script.<br />
# review the list of declared copyright holders in the file.<br />
# if you're all clear, change the license to the most liberal license possible. Document your change verbosely in the SVN commit log.<br />
<br />
== Current Reply List ==<br />
<br />
* Please keep the list sorted by family name!<br />
* Please only use "YES" or "NO"<br />
<br />
{| border="1"<br />
! Name !! GPLv2->GPLv2+ !! LGPLv2 -> LGPLv2+ !! GPLv2 -> GPLv2+v3 !! LGPLv2 -> LGPLv2+LGPLv3 || KDE e.V. decides<br />
|-<br />
|Adam, Till || YES || YES || YES || YES || NO<br />
|-<br />
|Bastian, Waldo || NO || NO || YES || YES || YES<br />
|-<br />
|Boemann, Casper || YES || YES || YES || YES || YES<br />
|-<br />
|Broadstone, Matt || NO || NO || YES || YES || YES<br />
|-<br />
|Cullmann, Christoph || NO || NO || YES || YES || NO<br />
|-<br />
|Drummond, Craig || YES || YES || YES || YES || YES<br />
|-<br />
|Dymo, Alexander || YES || YES || YES || YES || NO<br />
|-<br />
|Faure, David || YES || YES || YES || YES || YES<br />
|-<br />
|Granroth, Kurt || YES || YES || YES || YES || YES<br />
|-<br />
|Herden, Jens || YES || YES || YES || YES || YES<br />
|-<br />
|Hoeglund, Fredrik || NO || NO || YES || YES ||<br />
|-<br />
|Kainhofer, Reinhold || YES || YES || YES || YES || YES<br />
|-<br />
|Kellet, Alexander || YES || YES || YES || YES || YES<br />
|-<br />
|Knight, Robert || YES || YES || YES || YES || YES<br />
|-<br />
|Kretz, Matthias || NO || NO || YES || YES || NO<br />
|-<br />
|Kulow, Stephan || YES || YES || YES || YES || NO<br />
|-<br />
|Lunak, Lubos || YES || YES || YES || YES || NO<br />
|-<br />
|Mac-Vicar, Duncan || YES || YES || YES || YES || NO<br />
|-<br />
|Macieira, Thiago || YES || YES || YES || YES || YES<br />
|-<br />
|Mantia, Andras || NO || NO || YES || YES || YES<br />
|-<br />
|Martyn, Greg || YES || YES || YES || YES || YES<br />
|-<br />
|Molkentin, Daniel || YES || YES || YES || YES || NO<br />
|-<br />
|Montel, Laurent || YES || YES || YES || YES || YES<br />
|-<br />
|Moore, Richard || NO || NO || YES || YES || YES<br />
|-<br />
|Mueller, Dirk || YES || YES || YES || YES || NO<br />
|-<br />
|Mutz, Marc || YES || YES || NO || NO || NO<br />
|-<br />
|Riddell, Jonathan || YES || YES || YES || YES || YES<br />
|-<br />
|Sand, Espen || YES || YES || || || YES<br />
|-<br />
|Schlaeger, Chris || NO || NO || YES || YES || NO<br />
|-<br />
|Seigo, Aaron || YES || YES || YES || YES || YES<br />
|-<br />
|Stephenson, Will || YES || YES || YES || YES || YES<br />
|-<br />
|Tapsell, John || YES || YES || YES || YES || YES<br />
|-<br />
|Trueg, Sebastian (Exception: K3b) || YES || YES || YES || YES || YES<br />
|-<br />
|Wolfer, Urs || YES || YES || YES || YES || YES<br />
|-<br />
|}<br />
<br />
== Current TODO List ==<br />
<br />
* KDAB<br />
* Tobias Koenig<br />
* Matthew Woehlke<br />
* Daniel Teske<br />
* Dawit Alemayehu<br />
* Oswald Buddenhagen<br />
* Alex Zepeda<br />
* Thomas Leitner<br />
* Lars Knoll<br />
* Kevin Ottens<br />
* Simon Hausmann<br />
* Maksim Orlovich<br />
* Sirtaj Singh Kang<br />
* Karol Szwed<br />
* Thorsten Roeder<br />
* Joseph Wenninger<br />
<br />
== Current list of problematic directories ==<br />
<br />
<pre><br />
kdeadmin/ksysv/<br />
kdeadmin/kuser/<br />
kdeartwork/kscreensaver/kdesavers/<br />
kdebase/apps/kappfinder/<br />
kdebase/apps/keditbookmarks/<br />
kdebase/apps/konqueror/settings/filetypes/<br />
kdebase/apps/konqueror/settings/kio/<br />
kdebase/apps/konqueror/src/<br />
kdebase/apps/konqueror/src/tests/<br />
kdebase/apps/lib/konq/<br />
kdebase/apps/nsplugins/viewer/<br />
kdebase/runtime/kcontrol/componentchooser/<br />
kdebase/runtime/khelpcenter/<br />
kdebase/runtime/kpasswdserver/<br />
kdebase/runtime/kurifilter-plugins/fixhost/<br />
kdebase/runtime/kurifilter-plugins/localdomain/<br />
kdebase/runtime/nepomuk/strigibackend/<br />
kdebase/runtime/phonon/xine/<br />
kdebase/workspace/kcontrol/background/<br />
kdebase/workspace/kcontrol/input/core/<br />
kdebase/workspace/kcontrol/input/xcursor/<br />
kdebase/workspace/kcontrol/krdb/<br />
kdebase/workspace/kcontrol/style/<br />
kdebase/workspace/kdm/kfrontend/<br />
kdebase/workspace/kmenuedit/<br />
kdebase/workspace/ksplash/ksplashx/<br />
kdebase/workspace/ksysguard/gui/<br />
kdebase/workspace/ksysguard/gui/ksgrd/<br />
kdebase/workspace/ksysguard/gui/SensorDisplayLib/<br />
kdebase/workspace/ksysguard/ksysguardd/<br />
kdebase/workspace/ksysguard/ksysguardd/FreeBSD/<br />
kdebase/workspace/ksysguard/ksysguardd/Irix/<br />
kdebase/workspace/ksysguard/ksysguardd/Linux/<br />
kdebase/workspace/ksysguard/ksysguardd/NetBSD/<br />
kdebase/workspace/ksysguard/ksysguardd/Solaris/<br />
kdebase/workspace/ksysguard/ksysguardd/Tru64/<br />
kdebase/workspace/ktip/<br />
kdebase/workspace/libs/kdm/<br />
kdebase/workspace/libs/ksysguard/processui/<br />
kdebase/workspace/libs/plasma/widgets/<br />
kdebase/workspace/plasma/dataengines/filebrowser/<br />
kdebase/workspace/solid/kcm/<br />
kdebase/workspace/solid/networking/tests/<br />
kdebindings/csharp/qyoto/tools/csrcc/<br />
kdebindings/csharp/qyoto/tools/uics/<br />
kdebindings/ruby/qtruby/tools/rbrcc/<br />
kdebindings/ruby/qtruby/tools/rbuic/<br />
kdebindings/ruby/qtruby/tools/rbuic/ruby/<br />
kdebindings/xparts/xpart_notepad/<br />
kdeedu/klettres/src/<br />
kdeedu/kstars/kstars/indi/drivers/ccd/<br />
kdeedu/kstars/kstars/indi/drivers/focuser/<br />
kdeedu/kstars/kstars/indi/drivers/telescope/<br />
kdeedu/kstars/kstars/indi/drivers/video/<br />
kdeedu/kstars/kstars/indi/libs/webcam/<br />
kdeedu/kturtle/src/<br />
kdeedu/kturtle/src/interpreter/<br />
kdeedu/libkdeedu/extdate/<br />
kdeedu/marble/src/lib/geodata/<br />
kdeedu/marble/src/lib/geodata/data/<br />
kdeedu/marble/src/lib/geodata/handlers/gpx/<br />
kdeedu/marble/src/lib/geodata/handlers/kml/<br />
kdeedu/marble/src/lib/geodata/parser/<br />
kdegames/knetwalk/src/<br />
kdegraphics/gwenview/lib/<br />
kdegraphics/okular/generators/chm/kio-msits/<br />
kdegraphics/okular/generators/chm/lib/<br />
kdegraphics/okular/generators/comicbook/<br />
kdegraphics/okular/generators/plucker/unpluck/<br />
kdegraphics/okular/generators/spectre/libspectre/<br />
kdegraphics/okular/generators/spectre/libspectre/ghostscript/<br />
kdelibs/cmake/automoc/<br />
kdelibs/kde3support/tests/<br />
kdelibs/kdecore/tests/<br />
kdelibs/kdeui/tests/<br />
kdelibs/kfile/tests/<br />
kdelibs/kinit/tests/<br />
kdelibs/kioslave/http/kcookiejar/<br />
kdelibs/kioslave/http/kcookiejar/tests/<br />
kdelibs/kjsembed/examples/editor/<br />
kdelibs/kpty/<br />
kdelibs/phonon/kcm/<br />
kdelibs/phonon/tests/<br />
kdelibs/solid/examples/tutorial6/<br />
kdelibs/solid/tests/<br />
kdenetwork/kopete/doc/t2/<br />
kdenetwork/kopete/doc/t3/<br />
kdenetwork/kopete/protocols/irc/<br />
kdenetwork/kopete/protocols/jabber/libiris/cutestuff/legacy/<br />
kdenetwork/kopete/protocols/jabber/libiris/cutestuff/network/<br />
kdenetwork/kopete/protocols/jabber/libiris/cutestuff/util/<br />
kdenetwork/kopete/protocols/jabber/libiris/iris/include/<br />
kdenetwork/kopete/protocols/jabber/libiris/iris/jabber/<br />
kdenetwork/kopete/protocols/jabber/libiris/iris/xmpp-core/<br />
kdenetwork/kopete/protocols/jabber/libiris/iris/xmpp-im/<br />
kdenetwork/kopete/protocols/oscar/liboscar/utils/<br />
kdenetwork/kopete/protocols/qq/<br />
kdenetwork/kopete/protocols/yahoo/libkyahoo/<br />
kdepim/akonadi/resources/openchange/<br />
kdepim/akonadi/server/sqlplugin/<br />
kdepim/kaddressbook/xxport/<br />
kdepim/kdgantt/<br />
kdepim/kdgantt1/<br />
kdepim/kleopatra/utils/<br />
kdepim/kmail/<br />
kdepim/libkleo/ui/<br />
kdepimlibs/kcal/libical/vzic-1.3/<br />
kdepimlibs/kcal/versit/<br />
kdepimlibs/kioslave/sieve/<br />
kdepimlibs/syndication/tests/<br />
kdepim/views/conversationview/<br />
kdesdk/kioslave/svn/ksvnd/<br />
kdesdk/kompare/komparepart/<br />
kdevelop/buildtools/managers/automake/tests/<br />
kdevelop/plugins/qtdesigner/internals/<br />
kdevplatform/interfaces/<br />
kdevplatform/test/common/<br />
kdewebdev/kommander/editor/<br />
kdewebdev/kommander/factory/<br />
kdewebdev/kommander/plugin/<br />
</pre><br />
<br />
== Current top 30 of possible contributors to GPLv2-only files ==<br />
<br />
<pre> 23647 sequitur<br />
20801 gerken<br />
20659 craig<br />
17365 rdale<br />
17080 tokoe<br />
15023 dfaure<br />
13945 lunakl<br />
9339 arnorehn<br />
8703 thorsen<br />
8273 coolo<br />
7458 cies<br />
7448 mutlaqja<br />
7424 rogowski<br />
6018 gyurco<br />
5692 djurban<br />
5531 mrudolf<br />
5525 aacid<br />
5446 ogoffart<br />
5299 mkretz<br />
5245 winterz<br />
4216 cschlaeg<br />
4152 johnflux<br />
3652 waba<br />
3327 fredrik<br />
3138 chehrlic<br />
2944 mlaurent<br />
2916 teske<br />
2661 kniederk<br />
2614 martyn<br />
2484 lypanov<br />
</pre></div>Danimohttp://techbase.kde.org/User:DanimoUser:Danimo2007-08-12T09:17:01Z<p>Danimo: </p>
<hr />
<div>== Subpages ==<br />
<br />
{{List_subpages}}<br />
<br />
== TODO ==<br />
<br />
* Beautify Subpage titles<br />
<br />
<br />
== Bugs ==<br />
sorry for reporting a bug here; but this seems like as good a place as any :)<br />
When using <nowiki><code cpp></nowiki> tags I noted a bug. Specifically when you use the colon (or other means) to indent it. [[User:Zander|Zander]] 20:39, 9 April 2007 (CEST)<br />
Example code:<br />
<br />
:<code cpp><br />
#include <iostream><br />
#include <QtCore/QDate><br />
#include <zlib.h><br />
</code></div>Danimohttp://techbase.kde.org/Template:List_subpagesTemplate:List subpages2007-08-12T09:16:16Z<p>Danimo: </p>
<hr />
<div><div style="border:1px solid #CCC;"><br />
{{{caption|{{#ifeq:{{{2|{{NAMESPACE}}}}}:{{{1|{{PAGENAME}}}}}|{{FULLPAGENAME}}|In this {{NAMESPACE}}space|Pages with the prefix '{{{1|{{PAGENAME}}}}}' in the '{{{2|{{SUBJECTSPACE}}}}}' and '{{#if:{{{2|}}}|{{{2}}} talk|{{TALKSPACE}}}}' namespaces}}:}}}<br />
<div style="margin-bottom:-1px; padding:0.1em; border-bottom:1px solid #CCC; font-size:0.9em;">{{{2|{{SUBJECTSPACE}}}}}:{{#ifexist:{{{2|{{SUBJECTSPACE}}}}}:{{{1|{{PAGENAME}}}}}|<br />[[{{{2|{{SUBJECTSPACE}}}}}:{{{1|{{PAGENAME}}}}}|{{{1|{{PAGENAME}}}}}]]<br />}}{{Special:Prefixindex/{{{2|{{SUBJECTSPACE}}}}}:{{{1|{{PAGENAME}}}}}/}}</div><br />
<div style="padding:2px; font-size:0.9em;">{{#if:{{{2|}}}|{{{2}}} talk|{{TALKSPACE}}}}: {{#ifexist:{{{2|{{TALKSPACE}}}}}:{{{1|{{PAGENAME}}}}}|<br />[[{{{2|{{TALKSPACE}}}}}:{{{1|{{PAGENAME}}}}}|{{{1|{{PAGENAME}}}}}]]<br />}}{{Special:Prefixindex/{{#if:{{{2|}}}|{{{2}}} talk|{{TALKSPACE}}}}:{{{1|{{PAGENAME}}}}}/}}<br />
</div></div><noinclude>{{template documentation}}</noinclude></div>Danimohttp://techbase.kde.org/Getting_Started_(de)Getting Started (de)2007-07-20T09:05:52Z<p>Danimo: </p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|Getting_Started}}<br />
{{Box|Zugriff auf die Quellen|<br />
[[Image:Action_down.svg|right|32px]]<br />
Der KDE-Quelltext ist auf verschiedenen Wegen erhältlich:<br />
* [[Getting Started/Sources/Anonymous SVN|Anonymes SVN Schnellstart Anleitung]]<br />
* [[Getting Started/Sources/Using Subversion with KDE|Benutzung von Subversion mit KDE]] ''Benutzung von Subversion mit KDE Ein mehr in die Tiefe gehender Einblick für den Zugriff auf KDEs Quelltext mit Subversion, einschließlich dem Depot Layout und dem Arbeiten mit Revisionen und Patches.''<br />
* [http://websvn.kde.org/ Durchstöbern Sie den Quelltext online]<br />
* [[Getting Started/Sources/Snapshots|Tägliche Schnappschüsse]]<br />
|100%}}<br />
<br />
{{Box|Erstellung von KDE|<br />
[[Image:Action_tool.svg|right|32px]]<br />
Es existieren verschiedene KDE Branches. Für den produktiven Einsatz ist eine stabile Version empfohlen.<br />
* [[Getting Started/Build/KDE4_(de)|KDE 4 (Entwicklungs Version, Trunk)]]<br />
* [[Getting Started/Build/Stable Version|KDE 3.5 (Stabile Version)]]<br />
* [[Getting Started/Build|Andere Versionen und das FAQ]] ''Einschließlich Informationen für die Erstellung auf Nicht-Linux Systemen''<br />
|100%}}<br />
<br />
{{Box|Aufsetzen der Umgebung|<br />
[[Image:Action_pen.svg|right|32px]]<br />
Nachdem KDE erstellt worden ist, möchten Sie wahrscheinlich einen wirksamen Weg für das Starten der Anwendungen und das Ausführen Ihrer üblichen Entwicklungsaufgaben haben:<br />
* [[Getting Started/Increased Productivity in KDE4 with Scripts|Erhöhen Sie Ihre Produktivität in KDE4 mit Skripten]]<br />
* [[Getting Started/Set up KDE 4 for development|Setzen Sie KDE4 für die Entwicklung auf]]<br />
|100%}}<br />
[[Category:Build KDE]]</div>Danimohttp://techbase.kde.org/KDE_System_Administration_(de)KDE System Administration (de)2007-07-20T08:46:01Z<p>Danimo: /* Benutzer- und Gruppenprofile */</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|SysAdmin}}<br />
<br />
Dieser Abschnitt bietet Systemadministratoren, welche KDE neu aufsetzen oder vorhandene Einsätze verwalten die Informationen, die sie benötigen um dies effektiv zu tun.<br />
<br />
== Dateisystem ==<br />
;[[SysAdmin/Configuration Files|Syntax der Konfigurations Dateien]]<br />
:''KDEs Konfigurations Dateien sind textbasiert. Sie enthalten Gruppen aus Schlüssel-Wert Paaren. Dieser Abschnitt erläutert deren Syntax und behandelt folgende Bereiche:''<br />
* Lokalisation,<br />
* Shell Variablen,<br />
* komplettes oder teilweises Sperren der Konfigurationsdateien<br />
* Editier Hilfsprogramme<br />
* andere fortgeschrittene Eigenschaften.<br />
<br />
;[[SysAdmin/KDE Filesystem Hierarchy|KDE Hierarchie]]<br />
:''Dieser Artikel beschreibt wie KDE das Dateisystem benutzt, wo nach Dateien gesucht wird und wo sie abgespeichert werden. Er erklärt wie man diese Orte wechselt. Er beinhaltet auch eine kurz gefasste Übersicht der von den größten OS Anbietern benutzten Standard-Einstellungen.''<br />
<br />
;[[SysAdmin/XDG Filesystem Hierarchy|XDG Hierarchie]]<br />
:''In Ergänzung zu [[SysAdmin/KDE Filesystem Hierarchy|KDEs Datei Hierarchie]], benutzt KDE auch verschiedene Verzeichnisse, die in der XDG Spezifikation auf [http://freedesktop.org freedesktop.org] definiert sind. Dieser Artikel dokumentiert die benutzten Pfade und deren Funktionen.''<br />
<br />
== Desktop-Sitzungen ==<br />
<br />
;[[SysAdmin/Environment Variables|Umgebungsvariablen]]<br />
:''Eine Vielfalt an Umgebungs Variablen, die in diesem Artikel dokumentiert sind, ist vorhanden, um verschiedene Aspekte sowie das Laufzeitverhalten von KDE zu beeinflussen.''<br />
<br />
;[[SysAdmin/Startup|Startvorgang]]<br />
:''Während des Startvorganges werden die sichtbaren sowie die im hintergrund bleibenden Desktop-Komponenten gestartet. Dieser Artikel beschreibt die Startreihenfolge, liefert einen Überblick über einige der gestarteten Dienste und erklärt wie man Veränderungen macht.''<br />
<br />
;[http://docs.kde.org/development/en/kdebase/kdm/ Anmeldungsmanager]<br />
:''Der KDE Display Manager (KDM) bietet die Dienste, die üblicherweise mit einem Anmeldungsmanager assoziiert werden. Der erste Kontakt, den Ihre Benutzer mit einem KDE System haben, ist üblicherweise der KDM Bildschirm. Dieser Abschnitt behandelt die Grundlagen wie man einen KDM aufsetzt, sowie fortgeschrittene Themen wie Fernanmeldung, automatische Anmeldung, und mehr.''<br />
<br />
== Benutzer- und Gruppenprofile ==<br />
<br />
;[[SysAdmin/Kiosk/Introduction|Kiosk-Einführung]]<br />
:''Das Kiosk Rahmenwerk bietet eine Menge an Optionen, welche es erlauben einfach und mächtig die Fähigkeiten einer KDE Umgebung, basierend auf Benutzer- und Gruppenlegitimationen, zu definieren und einzuschränken. Zusätzlich zu dem einführenden Überblick umfasst dieser Artikel das Sperren der Konfigurationsdateien, Einschränkungen der Handlungsfreiheiten und Ressourcen, die Zuweisung von Benutzer- und Gruppenprofilen, und mehr.''<br />
<br />
;[[SysAdmin/Kiosk/Keys|Kiosk-Schlüssel]]<br />
:''Dieses Dokument detailliert bekannte globale und anwendungsspezifische Schlüssel für Aktionen, Ressourcen und URL Beschränkungen und macht es zu einer handlichen Referenzanleitung um Kiosk-Profile zu erstellen''<br />
<br />
;[[SysAdmin/Kiosk/Resources|Weitere Ressourcen]]<br />
:''KDEs Benutzer- und Gruppenprofile betreffe Links zu Werkzeugen, Mailinglisten, und zusätzlicher Dokumentation.''<br />
<br />
== Werkzeuge ==<br />
<br />
;[http://extragear.kde.org/apps/kiosktool/ KioskTool]<br />
:''Eine graphische Anwendung, die einem beim Verwalten von Benutzer- und Gruppenprofilen behilflich ist.''<br />
<br />
;[http://docs.kde.org/development/en/kdenetwork/krfb/ Gemeinsame Nutzung des Desktops]<br />
:''Die Fähigkeit zur gemeinsame Nutzung des Desktops macht auch eine Nutzung auf Distanz möglich. Neben zahlreichen anderen Verwendungsmöglichkeiten, ist diese Fähigkeit eine große Hilfe für das Betreuungspersonal, welches eine telefonische Unterstützung bietet.''<br />
<br />
;[[Development/Tutorials/Shell_Scripting_with_KDE_Dialogs|Benutzung von KDE Dialogen in Shell-Scripten]]<br />
:''Um verschiedene Dialoge anzuzeigen, können Sie KDialog Shell Scripte benutzen. Diese erlauben Ihnen eine nahtlose Eingliederung Ihrer eigenen GUI Erweiterungen.''<br />
<br />
;[[SysAdmin/Controlling_Access_To_Get_New_Stuff|Kontrollierter Zugang zu Get New Stuff Inhalten]]<br />
:''Dieser Abschnitt bietet Informationen, wie Sie die vom Internet durch die Get New Stuff Option herunterladbaren Inhalte kontrollieren können.''</div>Danimohttp://techbase.kde.org/KDE_System_Administration_(de)KDE System Administration (de)2007-07-20T08:45:34Z<p>Danimo: /* Benutzer- und Gruppenprofile */</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|SysAdmin}}<br />
<br />
Dieser Abschnitt bietet Systemadministratoren, welche KDE neu aufsetzen oder vorhandene Einsätze verwalten die Informationen, die sie benötigen um dies effektiv zu tun.<br />
<br />
== Dateisystem ==<br />
;[[SysAdmin/Configuration Files|Syntax der Konfigurations Dateien]]<br />
:''KDEs Konfigurations Dateien sind textbasiert. Sie enthalten Gruppen aus Schlüssel-Wert Paaren. Dieser Abschnitt erläutert deren Syntax und behandelt folgende Bereiche:''<br />
* Lokalisation,<br />
* Shell Variablen,<br />
* komplettes oder teilweises Sperren der Konfigurationsdateien<br />
* Editier Hilfsprogramme<br />
* andere fortgeschrittene Eigenschaften.<br />
<br />
;[[SysAdmin/KDE Filesystem Hierarchy|KDE Hierarchie]]<br />
:''Dieser Artikel beschreibt wie KDE das Dateisystem benutzt, wo nach Dateien gesucht wird und wo sie abgespeichert werden. Er erklärt wie man diese Orte wechselt. Er beinhaltet auch eine kurz gefasste Übersicht der von den größten OS Anbietern benutzten Standard-Einstellungen.''<br />
<br />
;[[SysAdmin/XDG Filesystem Hierarchy|XDG Hierarchie]]<br />
:''In Ergänzung zu [[SysAdmin/KDE Filesystem Hierarchy|KDEs Datei Hierarchie]], benutzt KDE auch verschiedene Verzeichnisse, die in der XDG Spezifikation auf [http://freedesktop.org freedesktop.org] definiert sind. Dieser Artikel dokumentiert die benutzten Pfade und deren Funktionen.''<br />
<br />
== Desktop-Sitzungen ==<br />
<br />
;[[SysAdmin/Environment Variables|Umgebungsvariablen]]<br />
:''Eine Vielfalt an Umgebungs Variablen, die in diesem Artikel dokumentiert sind, ist vorhanden, um verschiedene Aspekte sowie das Laufzeitverhalten von KDE zu beeinflussen.''<br />
<br />
;[[SysAdmin/Startup|Startvorgang]]<br />
:''Während des Startvorganges werden die sichtbaren sowie die im hintergrund bleibenden Desktop-Komponenten gestartet. Dieser Artikel beschreibt die Startreihenfolge, liefert einen Überblick über einige der gestarteten Dienste und erklärt wie man Veränderungen macht.''<br />
<br />
;[http://docs.kde.org/development/en/kdebase/kdm/ Anmeldungsmanager]<br />
:''Der KDE Display Manager (KDM) bietet die Dienste, die üblicherweise mit einem Anmeldungsmanager assoziiert werden. Der erste Kontakt, den Ihre Benutzer mit einem KDE System haben, ist üblicherweise der KDM Bildschirm. Dieser Abschnitt behandelt die Grundlagen wie man einen KDM aufsetzt, sowie fortgeschrittene Themen wie Fernanmeldung, automatische Anmeldung, und mehr.''<br />
<br />
== Benutzer- und Gruppenprofile ==<br />
<br />
;[[SysAdmin/Kiosk/Introduction|Kiosk Einführung]]<br />
:''Das Kiosk Rahmenwerk bietet eine Menge an Optionen, welche es erlauben einfach und mächtig die Fähigkeiten einer KDE Umgebung, basierend auf Benutzer- und Gruppenlegitimationen, zu definieren und einzuschränken. Zusätzlich zu dem einführenden Überblick umfasst dieser Artikel das Sperren der Konfigurationsdateien, Einschränkungen der Handlungsfreiheiten und Ressourcen, die Zuweisung von Benutzer- und Gruppenprofilen, und mehr.''<br />
<br />
;[[SysAdmin/Kiosk/Keys|Kiosk Schlüssel]]<br />
:''Dieses Dokument detailliert bekannte globale und anwendungsspezifische Schlüssel für Aktionen, Ressourcen und URL Beschränkungen und macht es zu einer handlichen Referenzanleitung um Kiosk-Profile zu erstellen''<br />
<br />
;[[SysAdmin/Kiosk/Resources|Zusätzliche Ressourcen]]<br />
:''KDEs Benutzer- und Gruppenprofile betreffe Links zu Werkzeugen, Mailinglisten, und zusätzlicher Dokumentation.''<br />
<br />
== Werkzeuge ==<br />
<br />
;[http://extragear.kde.org/apps/kiosktool/ KioskTool]<br />
:''Eine graphische Anwendung, die einem beim Verwalten von Benutzer- und Gruppenprofilen behilflich ist.''<br />
<br />
;[http://docs.kde.org/development/en/kdenetwork/krfb/ Gemeinsame Nutzung des Desktops]<br />
:''Die Fähigkeit zur gemeinsame Nutzung des Desktops macht auch eine Nutzung auf Distanz möglich. Neben zahlreichen anderen Verwendungsmöglichkeiten, ist diese Fähigkeit eine große Hilfe für das Betreuungspersonal, welches eine telefonische Unterstützung bietet.''<br />
<br />
;[[Development/Tutorials/Shell_Scripting_with_KDE_Dialogs|Benutzung von KDE Dialogen in Shell-Scripten]]<br />
:''Um verschiedene Dialoge anzuzeigen, können Sie KDialog Shell Scripte benutzen. Diese erlauben Ihnen eine nahtlose Eingliederung Ihrer eigenen GUI Erweiterungen.''<br />
<br />
;[[SysAdmin/Controlling_Access_To_Get_New_Stuff|Kontrollierter Zugang zu Get New Stuff Inhalten]]<br />
:''Dieser Abschnitt bietet Informationen, wie Sie die vom Internet durch die Get New Stuff Option herunterladbaren Inhalte kontrollieren können.''</div>Danimohttp://techbase.kde.org/KDE_System_Administration_(de)KDE System Administration (de)2007-07-20T08:45:11Z<p>Danimo: /* Desktop Sitzungen */</p>
<hr />
<div>{{Template:I18n/Language Navigation Bar|SysAdmin}}<br />
<br />
Dieser Abschnitt bietet Systemadministratoren, welche KDE neu aufsetzen oder vorhandene Einsätze verwalten die Informationen, die sie benötigen um dies effektiv zu tun.<br />
<br />
== Dateisystem ==<br />
;[[SysAdmin/Configuration Files|Syntax der Konfigurations Dateien]]<br />
:''KDEs Konfigurations Dateien sind textbasiert. Sie enthalten Gruppen aus Schlüssel-Wert Paaren. Dieser Abschnitt erläutert deren Syntax und behandelt folgende Bereiche:''<br />
* Lokalisation,<br />
* Shell Variablen,<br />
* komplettes oder teilweises Sperren der Konfigurationsdateien<br />
* Editier Hilfsprogramme<br />
* andere fortgeschrittene Eigenschaften.<br />
<br />
;[[SysAdmin/KDE Filesystem Hierarchy|KDE Hierarchie]]<br />
:''Dieser Artikel beschreibt wie KDE das Dateisystem benutzt, wo nach Dateien gesucht wird und wo sie abgespeichert werden. Er erklärt wie man diese Orte wechselt. Er beinhaltet auch eine kurz gefasste Übersicht der von den größten OS Anbietern benutzten Standard-Einstellungen.''<br />
<br />
;[[SysAdmin/XDG Filesystem Hierarchy|XDG Hierarchie]]<br />
:''In Ergänzung zu [[SysAdmin/KDE Filesystem Hierarchy|KDEs Datei Hierarchie]], benutzt KDE auch verschiedene Verzeichnisse, die in der XDG Spezifikation auf [http://freedesktop.org freedesktop.org] definiert sind. Dieser Artikel dokumentiert die benutzten Pfade und deren Funktionen.''<br />
<br />
== Desktop-Sitzungen ==<br />
<br />
;[[SysAdmin/Environment Variables|Umgebungsvariablen]]<br />
:''Eine Vielfalt an Umgebungs Variablen, die in diesem Artikel dokumentiert sind, ist vorhanden, um verschiedene Aspekte sowie das Laufzeitverhalten von KDE zu beeinflussen.''<br />
<br />
;[[SysAdmin/Startup|Startvorgang]]<br />
:''Während des Startvorganges werden die sichtbaren sowie die im hintergrund bleibenden Desktop-Komponenten gestartet. Dieser Artikel beschreibt die Startreihenfolge, liefert einen Überblick über einige der gestarteten Dienste und erklärt wie man Veränderungen macht.''<br />
<br />
;[http://docs.kde.org/development/en/kdebase/kdm/ Anmeldungsmanager]<br />
:''Der KDE Display Manager (KDM) bietet die Dienste, die üblicherweise mit einem Anmeldungsmanager assoziiert werden. Der erste Kontakt, den Ihre Benutzer mit einem KDE System haben, ist üblicherweise der KDM Bildschirm. Dieser Abschnitt behandelt die Grundlagen wie man einen KDM aufsetzt, sowie fortgeschrittene Themen wie Fernanmeldung, automatische Anmeldung, und mehr.''<br />
<br />
== Benutzer- und Gruppenprofile ==<br />
<br />
;[[SysAdmin/Kiosk/Introduction|Einführung zu Kiosk]]<br />
:''Das Kiosk Rahmenwerk bietet eine Menge an Optionen, welche es erlauben einfach und mächtig die Fähigkeiten einer KDE Umgebung, basierend auf Benutzer- und Gruppenlegitimationen, zu definieren und einzuschränken. Zusätzlich zu dem einführenden Überblick umfasst dieser Artikel das Sperren der Konfigurationsdateien, Einschränkungen der Handlungsfreiheiten und Ressourcen, die Zuweisung von Benutzer- und Gruppenprofilen, und mehr.''<br />
<br />
;[[SysAdmin/Kiosk/Keys|Kiosk Schlüssel]]<br />
:''Dieses Dokument detailliert bekannte globale und anwendungsspezifische Schlüssel für Aktionen, Ressourcen und URL Beschränkungen und macht es zu einer handlichen Referenzanleitung um Kiosk-Profile zu erstellen''<br />
<br />
;[[SysAdmin/Kiosk/Resources|Zusätzliche Ressourcen]]<br />
:''KDEs Benutzer- und Gruppenprofile betreffe Links zu Werkzeugen, Mailinglisten, und zusätzlicher Dokumentation.''<br />
<br />
== Werkzeuge ==<br />
<br />
;[http://extragear.kde.org/apps/kiosktool/ KioskTool]<br />
:''Eine graphische Anwendung, die einem beim Verwalten von Benutzer- und Gruppenprofilen behilflich ist.''<br />
<br />
;[http://docs.kde.org/development/en/kdenetwork/krfb/ Gemeinsame Nutzung des Desktops]<br />
:''Die Fähigkeit zur gemeinsame Nutzung des Desktops macht auch eine Nutzung auf Distanz möglich. Neben zahlreichen anderen Verwendungsmöglichkeiten, ist diese Fähigkeit eine große Hilfe für das Betreuungspersonal, welches eine telefonische Unterstützung bietet.''<br />
<br />
;[[Development/Tutorials/Shell_Scripting_with_KDE_Dialogs|Benutzung von KDE Dialogen in Shell-Scripten]]<br />
:''Um verschiedene Dialoge anzuzeigen, können Sie KDialog Shell Scripte benutzen. Diese erlauben Ihnen eine nahtlose Eingliederung Ihrer eigenen GUI Erweiterungen.''<br />
<br />
;[[SysAdmin/Controlling_Access_To_Get_New_Stuff|Kontrollierter Zugang zu Get New Stuff Inhalten]]<br />
:''Dieser Abschnitt bietet Informationen, wie Sie die vom Internet durch die Get New Stuff Option herunterladbaren Inhalte kontrollieren können.''</div>Danimohttp://techbase.kde.org/User:Danimo/Wiki_ScenariosUser:Danimo/Wiki Scenarios2007-07-08T10:28:45Z<p>Danimo: </p>
<hr />
<div>== Possible Scenarios for future Wiki use on *.kde.org ==<br />
<br />
The suggestions below are the outcome of a BoF during Akademy 2007 in Glasgow. We'd especially like to inquire the opinions of the subproject maintainers. Please add your opinions into the discussion page of this page or contact me on IRC. --[[User:Danimo|Danimo]] 12:28, 8 July 2007 (CEST)<br />
<br />
=== wiki.kde.org with namespaces === <br />
'''Note:''' wiki.kde.org will then run mediawiki<br />
<br />
*Pros<br />
** Easy to maintain<br />
<br />
*Cons<br />
** Might grow very big<br />
** Requires namespaces<br />
** No obvious structure<br />
** No homogenous target audience<br />
<br />
Unattractive for subprojects<br />
<br />
=== n /wiki per site ===<br />
<br />
*Pros<br />
** Very flexible for projects<br />
<br />
*Cons<br />
** Sharing templates impossible <br />
** Sharing files quite hard<br />
** Interwiki-Links are of limited use<br />
** n databases<br />
<br />
=== n role-based wiki sites === <br />
'''Description:''' Wikis on domains that target the supposed audience, e.g. users.kde.org.<br />
<br />
Possible compromise between the two suggestions above.<br />
<br />
*Pros<br />
** Less wiki instances than one per site<br />
<br />
*Cons<br />
** Sharing templates impossible <br />
** Sharing files quite hard<br />
** Interwiki-Links are of limited use<br />
** n databases<br />
<br />
== Action items ==<br />
<br />
* Investigate OpenID<br />
* Investigate which target audiences we/the projects want<br />
* Talk to subprojects<br />
** What solution do they prefer?<br />
** To what extend would they go with whatever we do?<br />
** Whats the additional value for them to join the effort?<br />
* How and where to migrate the contents of the current wikis?<br />
<br />
<br />
== Vote ==<br />
<br />
Please put sign underneath either bullet point that you want to vote for.<br />
Anonymous votes will not be counted.<br />
'''Example:''' <nowiki>**--~~~~</nowiki><br />
<br />
<br />
<br />
* wiki.kde.org with namespaces<br />
* n /wiki per site<br />
* n role-based wiki sites</div>Danimohttp://techbase.kde.org/User:Danimo/Wiki_ScenariosUser:Danimo/Wiki Scenarios2007-07-08T10:25:52Z<p>Danimo: </p>
<hr />
<div>== Possible Scenarios for future Wiki use on *.kde.org ==<br />
<br />
=== wiki.kde.org with namespaces === <br />
'''Note:''' wiki.kde.org will then run mediawiki<br />
<br />
*Pros<br />
** Easy to maintain<br />
<br />
*Cons<br />
** Might grow very big<br />
** Requires namespaces<br />
** No obvious structure<br />
** No homogenous target audience<br />
<br />
Unattractive for subprojects<br />
<br />
=== n /wiki per site ===<br />
<br />
*Pros<br />
** Very flexible for projects<br />
<br />
*Cons<br />
** Sharing templates impossible <br />
** Sharing files quite hard<br />
** Interwiki-Links are of limited use<br />
** n databases<br />
<br />
=== n role-based wiki sites === <br />
'''Description:''' Wikis on domains that target the supposed audience, e.g. users.kde.org.<br />
<br />
Possible compromise between the two suggestions above.<br />
<br />
*Pros<br />
** Less wiki instances than one per site<br />
<br />
*Cons<br />
** Sharing templates impossible <br />
** Sharing files quite hard<br />
** Interwiki-Links are of limited use<br />
** n databases<br />
<br />
== Action items ==<br />
<br />
* Investigate OpenID<br />
* Investigate which target audiences we/the projects want<br />
* Talk to subprojects<br />
** What solution do they prefer?<br />
** To what extend would they go with whatever we do?<br />
** Whats the additional value for them to join the effort?<br />
* How and where to migrate the contents of the current wikis?<br />
<br />
<br />
== Vote ==<br />
<br />
Please put sign underneath either bullet point that you want to vote for.<br />
Anonymous votes will not be counted.<br />
'''Example:''' <nowiki>**--~~~~</nowiki><br />
<br />
<br />
<br />
* wiki.kde.org with namespaces<br />
* n /wiki per site<br />
* n role-based wiki sites</div>Danimohttp://techbase.kde.org/User:Danimo/Wiki_ScenariosUser:Danimo/Wiki Scenarios2007-07-08T10:25:21Z<p>Danimo: </p>
<hr />
<div>== Possible Scenarios for future Wiki use on *.kde.org ==<br />
<br />
=== wiki.kde.org with namespaces === <br />
'''Note:''' wiki.kde.org will then run mediawiki<br />
<br />
*Pros<br />
** Easy to maintain<br />
<br />
*Cons<br />
** Might grow very big<br />
** Requires namespaces<br />
** No obvious structure<br />
** No homogenous target audience<br />
<br />
Unattractive for subprojects<br />
<br />
=== n /wiki per site ===<br />
<br />
*Pros<br />
** Very flexible for projects<br />
<br />
*Cons<br />
** Sharing templates impossible <br />
** Sharing files quite hard<br />
** Interwiki-Links are of limited use<br />
** n databases<br />
<br />
=== n role-based wiki sites === <br />
'''Description:''' Wikis on domains that target the supposed audience, e.g. users.kde.org.<br />
<br />
Possible compromise between the two suggestions above.<br />
<br />
*Pros<br />
** Less wiki instances than one per site<br />
<br />
*Cons<br />
** Sharing templates impossible <br />
** Sharing files quite hard<br />
** Interwiki-Links are of limited use<br />
** n databases<br />
<br />
== Action items ==<br />
<br />
* Investigate OpenID<br />
* Investigate which target audiences we/the projects want<br />
* Talk to subprojects<br />
** What solution do they prefer?<br />
** To what extend would they go with whatever we do?<br />
** Whats the additional value for them to join the effort?<br />
* How and where to migrate the contents of the current wikis?<br />
<br />
<br />
== Vote ==<br />
<br />
Please put sign underneath either bullet point that you want to vote for.<br />
Anonymous votes will not be counted.<br />
<nowiki>**--~~~~</nowiki><br />
<br />
<br />
<br />
* wiki.kde.org with namespaces<br />
* n /wiki per site<br />
* n role-based wiki sites</div>Danimohttp://techbase.kde.org/User:Danimo/Wiki_ScenariosUser:Danimo/Wiki Scenarios2007-07-02T18:07:17Z<p>Danimo: </p>
<hr />
<div>== Possible Scenarios for future Wiki use on *.kde.org ==<br />
<br />
=== wiki.kde.org with namespaces === <br />
<br />
*Pros<br />
** Easy to maintain<br />
<br />
*Cons<br />
** Might grow very big<br />
** Requires namespaces<br />
** No obvious structure<br />
** No homogenous target audience<br />
<br />
Unattractive for subprojects<br />
<br />
=== n /wiki per site ===<br />
<br />
*Pros<br />
** Very flexible for projects<br />
<br />
*Cons<br />
** Sharing templates impossible <br />
** Sharing files quite hard<br />
** Interwiki-Links are of limited use<br />
** n databases<br />
<br />
=== n role-based wiki sites === <br />
<br />
Possible compromise between the two suggestions above.<br />
<br />
*Pros<br />
** Less wiki instances than one per site<br />
<br />
*Cons<br />
** Sharing templates impossible <br />
** Sharing files quite hard<br />
** Interwiki-Links are of limited use<br />
** n databases<br />
<br />
== Action items ==<br />
<br />
* Investigate OpenID<br />
* Investigate which target audiences we/the projects want<br />
* Talk to subprojects<br />
** What solution do they prefer?<br />
** To what extend would they go with whatever we do?<br />
** Whats the additional value for them to join the effort?<br />
* How and where to migrate the contents of the current wikis?</div>Danimohttp://techbase.kde.org/User:Danimo/Wiki_ScenariosUser:Danimo/Wiki Scenarios2007-07-02T18:02:00Z<p>Danimo: </p>
<hr />
<div>== Possible Scenarios for future Wiki use on *.kde.org ==<br />
<br />
=== wiki.kde.org with namespaces === <br />
<br />
*Pros<br />
** Easy to maintain<br />
<br />
*Cons<br />
** Might grow very big<br />
** Requires namespaces<br />
<br />
=== n /wiki per site ===<br />
<br />
*Pros<br />
** Very flexible for projects<br />
<br />
*Cons<br />
** Sharing templates impossible <br />
** Sharing files quite hard<br />
** Interwiki-Links are of limited use<br />
** n databases<br />
<br />
=== n role-based wiki sites === <br />
<br />
Possible compromise between the two suggestions above.<br />
<br />
*Pros<br />
** Less wiki instances than one per site<br />
<br />
*Cons<br />
** Sharing templates impossible <br />
** Sharing files quite hard<br />
** Interwiki-Links are of limited use<br />
** n databases<br />
<br />
== Action items ==<br />
<br />
* Investigate OpenID</div>Danimohttp://techbase.kde.org/User:Danimo/Wiki_ScenariosUser:Danimo/Wiki Scenarios2007-07-02T17:55:47Z<p>Danimo: </p>
<hr />
<div>== Possible Scenarios for future Wiki use on *.kde.org ==<br />
<br />
=== /wiki per site ===<br />
<br />
*Pros<br />
*Cons<br />
<br />
=== wiki.kde.org with namespaces === <br />
<br />
*Pros<br />
*Cons<br />
<br />
=== n role-based wiki sites === <br />
<br />
*Pros<br />
*Cons<br />
<br />
== Action items ==<br />
<br />
* Investigate OpenID</div>Danimo