http://techbase.kde.org/api.php?action=feedcontributions&user=Sebastian&feedformat=atom 2013-05-26T03:01:45Z User contributions MediaWiki 1.20.2 http://techbase.kde.org/Schedules/KDE4/4.11_Feature_Plan 2013-05-21T20:59:37Z

<p>Sebastian: /* kdeedu */ add new KTouch features</p> <hr /> <div>This is a list of planned features for the SC 4.11 release. <br /> <br /> See also: <br /> <br /> *[[Schedules/KDE4/4.11 Release Schedule]] <br /> *[[Schedules/KDE4/4.10 Feature Plan]] (previous major release)<br /> *[[Schedules/KDE4/4.12 Feature Plan]] (next major release)<br /> <br /> &lt;br&gt; Legend: <br /> <br /> *to do =&amp;gt; not started yet <br /> *in-progress =&amp;gt; started, but not completed yet <br /> *done =&amp;gt; completed<br /> <br /> __TOC__ <br /> <br /> &lt;br&gt;<br /> <br /> = kdelibs =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> |}<br /> &lt;b&gt;NO NEW FEATURES ALLOWED&lt;/b&gt;<br /> &lt;br&gt;<br /> <br /> = kde-runtime =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|kio-mtp|KIO-Slave for MTP|philschmidt@gmx.net|Philipp Schmidt}}<br /> {{FeatureInProgress|nepomuk filemetadatawidget|Nepomuk Metadata Widget|me@vhanda.in|Vishesh Handa}}<br /> {{FeatureInProgress|nepomukcontroller-qml|QML version of the current Nepomuk controller. |joerg.ehrichs@gmx.de|Jörg Ehrichs}}<br /> {{FeatureDone|Web Shortcuts|Update old shortcuts.|de.meyer.maarten@gmail.com|Maarten De Meyer}}<br /> {{FeatureDone|Web Shortcuts|Use https where possible. ({{bug |308029}})|de.meyer.maarten@gmail.com|Maarten De Meyer}}<br /> {{FeatureDone|Web Shortcuts|Look for url on clipboard when creating new shortcut. ({{bug |146880}})|de.meyer.maarten@gmail.com|Maarten De Meyer}}<br /> {{FeatureInProgress|Web Shortcuts|Insert query placeholder button. ({{bug |146879}})|de.meyer.maarten@gmail.com|Maarten De Meyer}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kde-workspace =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> &lt;!-- The following section of entries has been auto generated by ChangelogGenerator. Do not edit!<br /> BEGIN GENERATED SECTION --&gt;<br /> {{FeatureTodo|kwin|windows that are moved to another desktop should be treated as sticky windows ({{bug |213847}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Medium focus stealing prevention should also prevent focus stealing when the timestamp on the active window is uncertain ({{bug |304746}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Integration with KScreen ({{bug |319994}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Support for buffer age extensions ({{bug |319995}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Egl backend using Wayland Surfaces ({{bug |319996}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|KWin keybindings is missing a shortcut for move window to previous screen ({{bug |303083}})|thomas.luebking@gmail.com}}<br /> {{FeatureTodo|kwin|There should be a shortcut to close window group ({{bug |238233}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|JJ: Use a bit of Wobbly effect while closing a window also. ({{bug |250856}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Highlight/shadow of application on screen 1 displayed on screen 0 ({{bug |278697}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Allow Effects to Temporarily Grab All Screen Edges ({{bug |283397}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Translucency Effect needs to be rewritten on top of AnimationEffect ({{bug |294856}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Break NETWM to allow inner xinerama struts ({{bug |299247}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Make ShaderManager act as a real stack ({{bug |300349}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Display content of resizing/moving windows: KDE-Help shows obsolete instructions ({{bug |305297}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Broken Desktop Switch On-Screen Display Animation ({{bug |316372}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Windows with no border (decoration) are visible on all activities ({{bug |274931}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|&quot;Thumbnail Aside&quot; effect visible when screen is locked -- privacy issue ({{bug |255712}}, Review 108670)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Quick Tile shortcuts should be toggle buttons ({{bug |263755}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Shaded windows are not considered in ::checkWorkspacePosition ({{bug |268660}}, Review 109679)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|build fails - getdomainname ({{bug |270586}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Window Specific Settings for Disabling Screen Edges ({{bug |271607}}, Review 108513)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Add fade in/fade out for outline effect ({{bug |274474}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Compositing not possible on each screen with multi head ({{bug |282677}}, Review 107853)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Remove &quot;Move TBLR&quot; from Zoom or at least pass the shortcuts reasonable names ({{bug |288903}}, Review 108290)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Hot Screen Corners do not work properly in multiscreen setup with different resolutions ({{bug |290887}}, Review 108513)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|When &quot;dim inactive&quot; is used, and &quot;apply effect to groups&quot; is disabled, blocky shadows appear everywhere ({{bug |293236}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|kwin does not honor disableMultihead true and causes window focus problems ({{bug |293734}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|DesktopThumbnailItem for QML ({{bug |296067}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Packages for Desktop Switching Layouts ({{bug |296068}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Walk Through Desktop layout rendering desktop previews ({{bug |296069}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Move ThumbnailBar from BoxSwitch to CoverSwitch ({{bug |296070}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Drop BoxSwitch effect ({{bug |296071}}, Review 104454)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Fix fullscreen state handling: NETWM says it's bound to focus and not stacking order, also see bug #224600 ({{bug |296076}}, Review 109572)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|New Window Decoration for Thin Clients ({{bug |299143}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Get rid of &quot;Display borders on maximized windows&quot; setting ({{bug |299245}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Cube animation on border approach should not be used unless the electric borders are actually in use and the config should be disabled, align or hint the electric border configuration ({{bug |299901}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|clientPopup: &quot;'More actions' and &quot;Attach as tab to&quot; lack mnemonics ({{bug |302833}}, Review 110402)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Make KWin compile with C++11 ({{bug |303313}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Maximized windows should be moved and maximized to second screen if they are moved with shortcut ({{bug |304506}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Window shortcut containing space: &quot;Launch Mail&quot; doesn't work ({{bug |305434}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Windows list icon does not show up in &quot;Walk Through Desktop List&quot; ({{bug |306187}}, Review 108445)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|The &quot;walk through desktop&quot; shortcuts don't show up in the desktop kcm ({{bug |306404}}, Review 108287)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Game mode ({{bug |306448}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Usability issue: &quot;Attach as tab to&quot; menu can be empty ({{bug |306451}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Upper part of windows tears when moving it left/right ONLY in upper part of display ({{bug |307965}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|KWin uses getdomainname() to obtain the hostname, should use getaddrinfo() ({{bug |308391}}, Review 108235)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Use Resize Area in Aurorae ({{bug |308992}}, Review 107936)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Configurable quick tile area config GUI ({{bug |308993}}, Review 109683)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Crash in KWin::Screenedge::unreserve on deactivating Actos script ({{bug |309695}}, Review 108513)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|[JJ] GHNS button displays icon, even if disabled in style settings ({{bug |309724}}, Review 108286)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|ScreenEdge::raisePanelProxies() is slow due to sync XLib communication ({{bug |311592}}, Review 108513)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|add rule to disobey configure requests ({{bug |311720}}, Review 109691)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Drop explosion effect ({{bug |312176}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Windows wider/taller than screen are cut off/partially mirrored when doing a screenshot of them using ksnapshot ({{bug |312851}}, Review 108258)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Desktop Effects - Zoom: Mouse Tracking &quot;Push&quot; laggy, inprecise and/or not working ({{bug |312956}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|&quot;Login&quot; effect does not fade in on secondary monitor(s) with a multi screen setup ({{bug |313061}}, Review 108362)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Overlap factor of keepAbove windows in placeSmart should be infinite ({{bug |313379}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|XReconfigureWMWindow fails to stack (lower) a window using an Above CWSibling combination ({{bug |313909}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Position rule conflicts with maximization rule ({{bug |314392}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|String representation of KWin::Client should include caption, not name. ({{bug |314402}}, Review 108959)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Please explain the meaning of vsync in the config gui ({{bug |314998}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|KWin crashes when switching windows ({{bug |315528}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|kwin crash when clicking kickoff widget (&quot;K menu&quot;) ({{bug |315951}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Dual screen issue caused by d6b3f6983efebc42abd6028ece9c3ec7facea2d0 ({{bug |316040}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Description text for the Slide Back effect is incorrect ({{bug |316877}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Java Swing Apps do not receive Deiconify event if window is shaded ({{bug |317025}}, Review 109593)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Snapping: Can no longer move window to occupy full screen width ({{bug |317845}}, Review 109864)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|when using flip switch to switch virtual desktop, activating hot corner trigger becomes difficult ({{bug |318294}}, Review 110013)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Mouse action support for sending window to different activity ({{bug |305758}})|rickstockton@reno-computerhelp.com}}<br /> {{FeatureDone|kwin|'Slide back' effect should react on stacking order changes ({{bug |294490}})|thomas.luebking@gmail.com}}<br /> {{FeatureDone|kwin|Track mouse effect generates graphics artifacts ({{bug |304435}})|thomas.luebking@gmail.com}}<br /> {{FeatureDone|kwin|vertical maximization doesn't work as expected ({{bug |91703}}, Review 103948)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Slide Back: Sometimes the Inactive window pops to the font for apprx. one frame when it is activated. ({{bug |294865}})|kwin-bugs-null@kde.org}}<br /> <br /> &lt;!-- END GENERATED SECTION --&gt;<br /> <br /> {{FeatureInProgress|plasma workspace|Port Task Manager applets to QML|hein@kde.org|Eike Hein (Sho_)}}<br /> {{FeatureInProgress|plasma workspace|refresh Air Plasma theme|mart@kde.org|Marco Martin}}<br /> {{FeatureInProgress|plasma workspace|Port Kickoff to qml|yellowcake-@gmx.net|Greg T}}<br /> {{FeatureTodo|systemsettings|Replace krandr KCM by libkscreen-based one|dvratil@redhat.com|Dan Vrátil}}<br /> {{FeatureInProgress|plasma workspace|Port rssnow to qml|terietor@gmail.com|Giorgos Tsiapaliokas}}<br /> {{FeatureInProgress|various|KActivities/SLC support for most our applications|ivan.cukic@kde.org|Ivan Čukić}}<br /> {{FeatureInProgress|plasma workspace|first desktop SLC applet release|mart@kde.org|Marco Martin}}<br /> {{FeatureTodo|plasma workspace|Top-rated documents for Task Manager|ivan.cukic@kde.org|Ivan Čukić}}<br /> {{FeatureInProgress|window manager|Rework and optimize vertex specification|fredrik@kde.org|Fredrik Höglund}}<br /> {{FeatureInProgress|window manager|Dynamic shader generation|fredrik@kde.org|Fredrik Höglund}}<br /> {{FeatureInProgress|window manager|Partial port to xcb|fredrik@kde.org|Fredrik Höglund}}<br /> {{FeatureInProgress|window manager|New launch feedback effect|fredrik@kde.org|Fredrik Höglund}}<br /> {{FeatureInProgress|activities|Encrypted activities|ivan.cukic@kde.org|Ivan Čukić}}<br /> {{FeatureInProgress|powerdevil|Improve profile error handling (DPMS)|kde@privat.broulik.de|Kai Uwe Broulik}}<br /> {{FeatureTodo|plasma workspace|Social Feed|mklapetek@kde.org|Martin Klapetek}}<br /> {{FeatureInProgress|plasma workspace|Order and group tasks by activity|fid@gpul.org|José Millán Soto}}<br /> {{FeatureDone|kmenuedit|Ability to sort entries in the sub-menus ({{bug |108419}})|frajibe@gmail.com|Julien Borderie}}<br /> {{FeatureDone|kmenuedit|Add move up/down buttons ({{bug |61537}})|frajibe@gmail.com|Julien Borderie}}<br /> {{FeatureDone|plasma notifications|Add button to notifications that allow configuring them|kde@privat.broulik.de|Kai Uwe Broulik}}<br /> {{FeatureDone|plasma batterymonitor|Improve situtation with multiple batteries (show battery names, dont just sum up _all_ the percentages etc)|kde@privat.broulik.de|Kai Uwe Broulik}}<br /> {{FeatureInProgress|powerdevil|Implement notifications for non-internal batteries (aka &quot;Your mouse is running low&quot;)|kde@privat.broulik.de|Kai Uwe Broulik}}<br /> {{FeatureInProgress|plasma batterymonitor|UI overhaul for battery monitor|kde@privat.broulik.de|Kai Uwe Broulik}}<br /> {{FeatureInProgress|powerdevil|Remember action settings when action is disabled|kde@privat.broulik.de|Kai Uwe Broulik}}<br /> {{FeatureInProgress|klipper|Allow to keep items in clipboard history|fid@gpul.org|José Millán Soto}}<br /> {{FeatureTodo|plasma weather data engine|Add search query (based on code from libplasmaweather)|emdeck@gmail.com|Michał Dutkiewicz}}<br /> {{FeatureTodo|plasma weather data engine|Allow to sort search results by relevance score|emdeck@gmail.com|Michał Dutkiewicz}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kde-baseapps =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureTodo|FolderView|Split into PopupApplet and Containment|ignat.semenov@blue-systems.com|Ignat Semenov}}<br /> {{FeatureTodo|FolderView|Port to QML|ignat.semenov@blue-systems.com|Ignat Semenov}}<br /> <br /> {{FeatureTodo|Dolphin|Clean up Places panel context menus|kde@privat.broulik.de|Kai Uwe Broulik}}<br /> <br /> {{FeatureTodo|Kate|Search-plugin: Add &quot;Current file mode&quot;|kare.sars@iki.fi|Kåre Särs}}<br /> {{FeatureDone|Kate|Search-plugin: As-you-type search in current file|kare.sars@iki.fi|Kåre Särs}}<br /> {{FeatureDone|Kate|Search-plugin: Multi line search &amp; replace|kare.sars@iki.fi|Kåre Särs}}<br /> {{FeatureDone|Kate|Search-plugin: Replace &quot;\&lt;number&gt;&quot; with corresponding regexp-captures in the replace string|kare.sars@iki.fi|Kåre Särs}}<br /> {{FeatureDone|Kate|gdb-plugin: Unify the stack trace and local variables to one ToolView|kare.sars@iki.fi|Kåre Särs}}<br /> {{FeatureDone|Kate|gdb-plugin: Do not update stack/locals view if not visible|kare.sars@iki.fi|Kåre Särs}}<br /> {{FeatureInProgress|Kate|Vim Mode Macro support|kdedevel@etothepiplusone.com|Simon St James}}<br /> {{FeatureDone|Kate|Pâté plugin now supports Python2 or Python3 as a build-time option|srhaque@theiet.org|Shaheed Haque}}<br /> {{FeatureDone|Kate|Pâté GID plugin now supports autocompletion based on the contents of the ID file|srhaque@theiet.org|Shaheed Haque}}<br /> <br /> <br /> {{FeatureDone|Kate|Many generic functions and generic classes, likely the more outstanding are the autocompletations. Now you can create a code completion model with very few lines from Python<br /> |goinnn@gmail.com|Pablo Martín}}<br /> {{FeatureDone|Kate|Pâté python utils plugin. Utils to Python: Checker Parse, Checker Pep8, Checker Pyflakes, Snippets|goinnn@gmail.com|Pablo Martín}}<br /> {{FeatureDone|Kate|Pâté javascript utils plugin. Utils to JavaScript: Autocomplete, Autocomplete jQuery, Checker JSLint, Pretty JSON, Snippets|goinnn@gmail.com|Pablo Martín}}<br /> {{FeatureDone|Kate|Pâté XML pretty plugin. A simple XML pretty printer. XML formatter which a good indents|goinnn@gmail.com|Pablo Martín}}<br /> {{FeatureDone|Kate|Pâté Django utils plugin. Utils to Django: Snippets, and template utils|goinnn@gmail.com|Pablo Martín}}<br /> {{FeatureDone|Kate|Pâté Python autocomplete plugin.|goinnn@gmail.com|Pablo Martín}}<br /> {{FeatureDone|Kate|[http://kate-editor.org/2013/04/23/a-rich-python-console-and-more-in-kate-editor/ Integration of the python_autocomplete and python_console_ipython plugins with the project plugin] .|goinnn@gmail.com|Pablo Martín}}<br /> <br /> <br /> {{FeatureTodo|Konsole|Improve the search filter bar|francesco.cecconi@gmail.com|Francesco Cecconi}}<br /> <br /> <br /> {{FeatureTodo|Konsole|Add the --separate cmdline option for running in new process|adaptee@gmail.com|Jekyll Wu}}<br /> {{FeatureTodo|Konsole|Make the d&amp;d popup menu optional|adaptee@gmail.com|Jekyll Wu}}<br /> <br /> {{FeatureTodo|Konqueror|Settings for WebKit Part|sandfeld@kde.org|Allan Sandfeld}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdeedu =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureTodo|Marble|Have support for &quot;repeatX&quot; in the projection classes|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Satellite Map NG|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Mars &amp; Venus satellite plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}<br /> {{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}<br /> {{FeatureTodo|Marble|Help Menu polishing / Support page inclusion|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Toolbar polishing/refactoring|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureInProgress|Marble|Foursquare plugin|utkuaydin34@gmail.com|Utku Aydın}}<br /> {{FeatureDone|Marble|OSM vector rendering (GSOC branch merge)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureDone|Marble|Dock Widgets|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureDone|Marble|Stars Constellations|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureInProgress|Marble|KML I/O Improvements|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureInProgress|Marble|Basic KML Editor|tgridel@free.fr|Thibaut Gridel}}<br /> {{FeatureDone|Marble|WebKit Powered Info Dialog|marble-devel@kde.org|Various Artists}}<br /> {{FeatureDone|Marble|License Information Info Box|marble-devel@kde.org|Various Artists}}<br /> {{FeatureDone|Marble|Navigation Tool Redesign|rahn@kde.org|Torsten Rahn, Mohammed Nafees}}<br /> {{FeatureTodo|Marble|Zoom to content of geo file after loading (at least on start-up)|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Marble|Geo files thumbnailer|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Marble|Geo files metadata extractor|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureDone|Marble|GHNS Map Installation In Marble Qt|earthwings@gentoo.org|Dennis Nienhüser}}{{FeatureInProgress|Marble|Support GPX-tracks in elevationProfile|roman.karlstetter@googlemail.com|Roman Karlstetter}}<br /> {{FeatureTodo|Rocs|Data Structure Backend wise iconsets and preconfigurations for types|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Printing and image export of graphs.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Data Structure Snapshot and Recovery.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Visual Graph Editor Handling: copy&amp;paste, data structure focus, property display|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureInProgress|Rocs|In-Program documentation for scripting API|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureInProgress|Rocs|Scripting API cleanup|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Statistics module: scripts may add statistics data during algorithm executions|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Text-only interface for Rocs aka Cantor backend|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Worksheet Integration|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureInProgress|Cantor|Python backend|filipe@kde.org|Filipe Saraiva}}<br /> {{FeatureInProgress|Kig|Geogebra Support|david.narvaez@computer.org|David E. Narváez}}<br /> {{FeatureInProgress|Kig|CAS Backend|david.narvaez@computer.org|David E. Narváez}}<br /> {{FeatureInProgress|KAlgebra|Matrix support|aleixpol@kde.org|Aleix Pol Gonzalez}}<br /> {{FeatureDone|KTouch|Right-to-Left Training|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureInProgress|KTouch|Support for Custom Lessons|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdegames=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureDone|KJumpingCube|Make computer think-times shorter and responses faster|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Provide five skill levels (previously three)|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Provide board size up to 15x15 (previously 10x10)|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Add multi-move undo and redo (previously one move only)|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Improve the algorithm for computer opponent Newton|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Make a new toolbar layout with a general-purpose stop-start button|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Add optional pauses after computer moves or animation steps, to help new players understand how the game works|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Major internal restructure and rewrite: involving separation of model, view, control and AI classes, new classes for Game and AI_Box and executing AI code on a separate thread|iandw.au@gmail.com|Ian Wadham}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdegraphics=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|libkipi|[http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/dodonvictor/10002 Porting libkipi to KDE-XML GUI]|dodonvictor@gmail.com|Victor Dodon}}<br /> <br /> {{FeatureDone|kolourpaint|WebP image format plugin|kollix@aon.at|Martin Koller}}<br /> <br /> {{FeatureInProgress|okular|Configurable review tools {{bug |159601}}|okular-devel@kde.org|Okular Developers}}<br /> {{FeatureInProgress|okular|Undo/Redo support in PDF forms {{bug |177501}}|okular-devel@kde.org|Okular Developers}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdemultimedia =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|Juk|[http://community.kde.org/Juk#Porting_plan Port Juk away from kde3support]|martin.sandsmark@kde.org|Martin Sandsmark}}<br /> {{FeatureInProgress|Juk|Support excluding directories from a recursive search [https://git.reviewboard.kde.org/r/110273/ Review Request 110273]|biergaizi2009@gmail.com|Tom Li}}<br /> {{FeatureDone|Juk|Add support for [http://www.opus-codec.org/ Ogg Opus audio editing/playback] (requires TagLib and Phonon also support)|mpyne@kde.org|Michael Pyne}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdenetwork=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|KGet|Metalink/HTTP Support|dahalaishraj@gmail.com|Aish Raj Dahal}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdepim =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> {{FeatureTodo|Facebook resource|Include it in default install|martin.klapetek@gmail.com|Martin Klapetek}}<br /> {{FeatureTodo|KABC Contact groups|use uid's for references|mollekopf@kolabsys.com|Christian Mollekopf}}<br /> {{FeatureInProgress|Akregator2|Merge in kdepim|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|Knode|Merge in KMail|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|BackupMail|Extend backup to all kdepim apps|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|Sieve|Rewrite dialogbox|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|libs|Move folderview to kdepimlibs/akonadi|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|SendLaterAgent|Agent for allow to send later mails|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|PimActivity|Create a library to support activity in pim apps|montel@kde.org|Montel Laurent}}<br /> {{FeatureDone|kolab-resource|Make Kolab 3.0 option available|mollekopf@kolabsys.com|Christian Mollekopf}}<br /> {{FeatureDone|headerthemeeditor|Program to edit kmail header theme based on Grantlee|montel@kde.org|Montel Laurent}}<br /> {{FeatureDone|Sieve|Add support for autogenerate sieve script|montel@kde.org|Montel Laurent}}<br /> {{FeatureDone|Blogilo|Use new widget component based on qtwebkit for html editor|montel@kde.org|Montel Laurent}}<br /> {{FeatureDone|ImportWizard|Allow to import settings/data for trojita and improve all others importer|montel@kde.org|Montel Laurent}}<br /> <br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdeplasma-addons =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> {{FeatureInProgress|Microblog|replace with QML version|sebas@kde.org|Sebastian Kügler}}<br /> {{FeatureInProgress|Eyes|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> {{FeatureInProgress|FifteenPuzzle|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> {{FeatureInProgress|Luna|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> {{FeatureInProgress|Timer|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdesdk =<br /> <br /> {| cellspa/cing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> {{FeatureTodo|Okteta|Add a general KPart adapter to Kasten, than finish port of Okteta KPart to Okteta Kasten|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Add global toggle option for the offset display, hex or decimal|kossebau@kde.org|Friedrich W. H. Kossebau}} <br /> {{FeatureTodo|Okteta|Add Kate-like combined dialogs to query for actions on files|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Add Okular like embedded notifications|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add support for import by drop, both url and data|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add support for memory mapping of files and 64-bit addressing|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add support for jobs like io, printing, string search or filter|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|copy again puts also a value or char variant of the data to clipboard|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Improve the titels of the changes to the bytearray to be more descriptive, best using ids to avoid text string|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Make all user interaction in the KastenCore managers plugin-based|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Merge row and column widgets into one|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Store bookmarks|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Store bookmarks and other view settings for next load|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Add custom datatypes to structures tool|alex.richardson@gmx.de|Alex Richardson}}<br /> {{FeatureInProgress|Okteta|Add tagged unions to structures tool|alex.richardson@gmx.de|Alex Richardson}}<br /> {{FeatureInProgress|Okteta|Add array indices to structures tool|alex.richardson@gmx.de|Alex Richardson}}<br /> {{FeatureInProgress|Umbrello| widget resize and diagram auto resize feature |ralf.habacker@freenet.de|Ralf Habacker}}<br /> {{FeatureTodo|Umbrello|add spline based association lines to avoid autolayout widget/line overlapping (needs volunteers)|ralf.habacker@freenet.de|Ralf Habacker}}<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> = kdeutils=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureDone|KWallet|UI Refactoring|kde@rusu.info|Valentin Rusu}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdetoys =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureTodo|KTeaTime|Bring back the system tray progress indicator known from KTeaTime 4.6.5 and earlier ({{bug |279222}})|kde@hilefoks.org|Stefan Böhmann}}<br /> |}<br /> &lt;br&gt;</div>

Sebastian http://techbase.kde.org/User:Sebastian/Courses 2012-11-15T18:47:23Z

<p>Sebastian: introduction</p> <hr /> <div>= Overview over All Courses =<br /> <br /> This site lists all courses currently present in KTouch's [https://projects.kde.org/projects/kde/kdeedu/ktouch/repository/revisions/master/show/data/courses repository] and their status. Check [[../CourseQuality|Course Quality]] to learn more about what the individual quality criteria are about.</div>

Sebastian http://techbase.kde.org/User:Sebastian 2012-11-15T18:37:20Z

<p>Sebastian: </p> <hr /> <div>[[/CourseQuality]]<br /> <br /> [[/Courses]]</div>

Sebastian http://techbase.kde.org/User:Sebastian 2012-11-15T18:36:47Z

<p>Sebastian: </p> <hr /> <div>[[/CourseQuality]]<br /> [[/Courses]]</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-15T18:36:16Z

<p>Sebastian: /* Individual Lessons */ typos</p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Course Composition ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has two haptic markers for the keys on the second row belonging to the index fingers. These two keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjkl;&lt;/tt&gt; for the US keyboard layout.<br /> <br /> {{Info|2=Rationale|1=Those eight keys are the start position of each finger. One must internalize the location of these keys first to successfully learn touch typing.}}<br /> <br /> ; Introduce two new keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson early-on focusing on the accent key alone.<br /> <br /> {{Info|2=Rationale|1= If more keys are introduced the trainee might get overwhelmed by the difficulty of the lesson and loose his motivation. Introduce keys for important keys fist to able to form real words earlier.}}<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced keys are the most or at least very frequently used characters in the lesson text.<br /> <br /> {{Info|2=Rationale|1=If the trainee passes a lesson he should have mastered the new keys. This is only possible if the lesson contains a significant amount of the new characters.}}<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: Every two to three lessons add a repetition lesson without any new keys. These should have an even character mix covering all already introduced characters.<br /> <br /> {{Info|2=Rationale|1=Such lessons help to strengthen the acquired skills and and provide a way to check the overall training level. They are also better suited for repeated training to further improve one's general typing skills.}}<br /> <br /> ; Dedicated lessons for capitalization: There should be several lessons focusing sorely on capitalization. Ideally capitalization is introduced in multiple steps: At first only the left shift key, then the the right, then both and followed by one or more repetition lessons.<br /> <br /> {{Info|2=Rationale|1=Mastering capitalization is the most difficult part of learning touch typing. Therefore extra effort must be spend on these lessons.}}<br /> <br /> ; Cover the complete keyboard layout: This includes characters and symbols accessibly via other modifiers than shift. Ideally every character, number and symbol which is printed on a real keyboard should be covered.<br /> <br /> {{Info|2=Rationale|1=The more complete a course is the more the trainee can learn from it. It also keeps the course interesting for already advanced typists.}}<br /> <br /> == Individual Lessons ==<br /> <br /> ; Give lessons a descriptive title: Name the new characters if there are any or otherwise state what the lesson is about.<br /> <br /> {{Info|2=Rationale|1=Good titles make it easier to find the right course if one wants to train on something specific.}}<br /> <br /> ; The lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on a freely chosen subject.<br /> <br /> {{Info|2=Rationale|1=Training with real words and sentences is more effective than with arbitrary random character combinations since that is closer to real typing. And it is more fun.}}<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be used. Never use misspelled words.<br /> <br /> {{Info|2=Rationale|1=Random character combinations are hard to type and are seldom found in day-to-day typing. Misspelled words on the other hand are confusing and have even a negative learning value, since the trainee may memorize the wrong spelling.}}<br /> <br /> ; Lesson text should be roughly 600 characters long: They may be longer, up to 1200 characters is okay, but shorter lessons should be avoided. This is especially true for repetition lessons.<br /> <br /> {{Info |2=Rationale|1=Keeping within this range ensures that a untrained typist (~120 characters per minute) can finish a lesson in five to ten minutes. Longer lessons get frustrating, shorter ones are ineffective.}}</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-15T18:31:59Z

<p>Sebastian: /* Course Composition */ typos</p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Course Composition ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has two haptic markers for the keys on the second row belonging to the index fingers. These two keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjkl;&lt;/tt&gt; for the US keyboard layout.<br /> <br /> {{Info|2=Rationale|1=Those eight keys are the start position of each finger. One must internalize the location of these keys first to successfully learn touch typing.}}<br /> <br /> ; Introduce two new keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson early-on focusing on the accent key alone.<br /> <br /> {{Info|2=Rationale|1= If more keys are introduced the trainee might get overwhelmed by the difficulty of the lesson and loose his motivation. Introduce keys for important keys fist to able to form real words earlier.}}<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced keys are the most or at least very frequently used characters in the lesson text.<br /> <br /> {{Info|2=Rationale|1=If the trainee passes a lesson he should have mastered the new keys. This is only possible if the lesson contains a significant amount of the new characters.}}<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: Every two to three lessons add a repetition lesson without any new keys. These should have an even character mix covering all already introduced characters.<br /> <br /> {{Info|2=Rationale|1=Such lessons help to strengthen the acquired skills and and provide a way to check the overall training level. They are also better suited for repeated training to further improve one's general typing skills.}}<br /> <br /> ; Dedicated lessons for capitalization: There should be several lessons focusing sorely on capitalization. Ideally capitalization is introduced in multiple steps: At first only the left shift key, then the the right, then both and followed by one or more repetition lessons.<br /> <br /> {{Info|2=Rationale|1=Mastering capitalization is the most difficult part of learning touch typing. Therefore extra effort must be spend on these lessons.}}<br /> <br /> ; Cover the complete keyboard layout: This includes characters and symbols accessibly via other modifiers than shift. Ideally every character, number and symbol which is printed on a real keyboard should be covered.<br /> <br /> {{Info|2=Rationale|1=The more complete a course is the more the trainee can learn from it. It also keeps the course interesting for already advanced typists.}}<br /> <br /> == Individual Lessons ==<br /> <br /> ; Give lessons a descriptive title: Name the the new characters if there are any or otherwise state what the lesson is about.<br /> <br /> {{Info|2=Rationale|1=Good titles make it easier to find the right course if one wants to train something specific.}}<br /> <br /> ; The lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on a freely chosen subject.<br /> <br /> {{Info|2=Rationale|1=Training with real words and sentences is more effective than with arbitrary random character combinations since it that is closer to real typing usage. And it is more fun.}}<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be uses. Do not employ misspelled words at all costs.<br /> <br /> {{Info|2=Rationale|1=Random character combinations are hard to type and are seldom found in day-to-day typing. Misspelled words on the other hand are confusing and have even a negative learning value, since the trainee may memorize the wrong spelling.}}<br /> <br /> ; Lesson text should be roughly 600 characters long: Texts may be longer, up to 1200 characters is okay, but shorter lessons should be avoided. This is especially true for repetition lessons.<br /> <br /> {{Info |2=Rationale|1=Keeping within this range ensures that a untrained typist (~120 characters per minute) can finish a lesson in five to ten minutes. Longer lessons get frustrating, shorter ones are ineffective.}}</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-05T17:42:48Z

<p>Sebastian: </p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Course Composition ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has to haptic markers for the keys belonging to we index fingers on the second row. These keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjkl;&lt;/tt&gt; for the US keyboard layout.<br /> <br /> {{Info|2=Rationale|1=Those eight keys are the start position of each finger. One must internalize the location of these keys first to successfully learn touch typing.}}<br /> <br /> ; Introduce two new keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson focusing on the accent key alone.<br /> <br /> {{Info|2=Rationale|1= If more keys are introduced the trainee might get overwhelmed by the difficulty of the lesson and loose his motivation. Introduce keys for important keys for the ability to form real words earlier.}}<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced are the most or at least very frequently used characters in the lesson text.<br /> <br /> {{Info|2=Rationale|1=If the trainee passes a lesson he should have mastered the new keys. This is only possible if the lesson contains a significant amount of the new characters.}}<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: Every two to three lessons add a repetition lesson without new keys. These should have an even character mix covering all already introduced characters.<br /> <br /> {{Info|2=Rationale|1=Such lessons help to strengthen the acquired skills and and provide a way to check the overall training level. They are also better suited for repeated training to further improve one's general typing skills.}}<br /> <br /> ; Dedicated lessons for capitalization: There should be several lessons focusing sorely on capitalization. Ideally capitalization is introduced in multiple steps: At first only the left shift key, then the the right, then both and followed by one or more repetition lessons.<br /> <br /> {{Info|2=Rationale|1=Mastering capitalization is the most difficult part of learning touch typing. Therefore extra effort must be spend on these lessons.}}<br /> <br /> ; Cover the complete keyboard layout: This includes characters and symbols accessibly via additional modifiers. Ideally every character, number and symbol which is printed on a real keyboard should be covered.<br /> <br /> {{Info|2=Rationale|1=This keeps the course interesting for already advanced typists.}}<br /> <br /> == Individual Lessons ==<br /> <br /> ; Give lessons a descriptive title: Name the the new characters if there are any or otherwise state what the lesson is about.<br /> <br /> {{Info|2=Rationale|1=Good titles make it easier to find the right course if one wants to train something specific.}}<br /> <br /> ; The lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on a freely chosen subject.<br /> <br /> {{Info|2=Rationale|1=Training with real words and sentences is more effective than with arbitrary random character combinations since it that is closer to real typing usage. And it is more fun.}}<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be uses. Do not employ misspelled words at all costs.<br /> <br /> {{Info|2=Rationale|1=Random character combinations are hard to type and are seldom found in day-to-day typing. Misspelled words on the other hand are confusing and have even a negative learning value, since the trainee may memorize the wrong spelling.}}<br /> <br /> ; Lesson text should be roughly 600 characters long: Texts may be longer, up to 1200 characters is okay, but shorter lessons should be avoided. This is especially true for repetition lessons.<br /> <br /> {{Info |2=Rationale|1=Keeping within this range ensures that a untrained typist (~120 characters per minute) can finish a lesson in five to ten minutes. Longer lessons get frustrating, shorter ones are ineffective.}}</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-05T17:28:19Z

<p>Sebastian: /* Lessons */</p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Course Composition ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has to haptic markers for the keys belonging to we index fingers on the second row. These keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjklö&lt;/tt&gt; for the US keyboard layout.<br /> <br /> {{Info|2=Rationale|1=Those eight keys are the start position of each finger. One must internalize the location of these keys first to successfully learn touch typing.}}<br /> <br /> ; Introduce two new keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson focusing on the accent key alone.<br /> <br /> {{Info|2=Rationale|1= If more keys are introduced the trainee might get overwhelmed by the difficulty of the lesson and loose his motivation. Introduce keys for important keys for the ability to form real words earlier.}}<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced are the most or at least very frequently used characters in the lesson text.<br /> <br /> {{Info|2=Rationale|1=If the trainee passes a lesson he should have mastered the new keys. This is only possible if the lesson contains a significant amount of the new characters.}}<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: Every two to three lessons add a repetition lesson without new keys. These should have an even character mix covering all already introduced characters.<br /> <br /> {{Info|2=Rationale|1=Such lessons help to strengthen the acquired skills and and provide a way to check the overall training level. They are also better suited for repeated training to further improve one's general typing skills.}}<br /> <br /> ; Dedicated lessons for capitalization: There should be several lessons focusing sorely on capitalization. Ideally capitalization is introduced in multiple steps: At first only the left shift key, then the the right, then both and followed by one or more repetition lessons.<br /> <br /> {{Info|2=Rationale|1=Mastering capitalization is the most difficult part of learning touch typing. Therefore extra effort must be spend on these lessons.}}<br /> <br /> ; Cover the complete keyboard layout: This includes characters and symbols accessibly via additional modifiers. Ideally every character, number and symbol which is printed on a real keyboard should be covered.<br /> <br /> {{Info|2=Rationale|1=This keeps the course interesting for already advanced typists.}}<br /> <br /> == Individual Lessons ==<br /> <br /> ; Give lessons a descriptive title: Name the the new characters if there are any or otherwise state what the lesson is about.<br /> <br /> {{Info|2=Rationale|1=Good titles make it easier to find the right course if one wants to train something specific.}}<br /> <br /> ; The lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on a freely chosen subject.<br /> <br /> {{Info|2=Rationale|1=Training with real words and sentences is more effective than with arbitrary random character combinations since it that is closer to real typing usage. And it is more fun.}}<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be uses. Do not employ misspelled words at all costs.<br /> <br /> {{Info|2=Rationale|1=Random character combinations are hard to type and are seldom found in day-to-day typing. Misspelled words on the other hand are confusing and have even a negative learning value, since the trainee may memorize the wrong spelling.}}<br /> <br /> ; Lesson text should be roughly 600 characters long: Texts may be longer, up to 1200 characters is okay, but shorter lessons should be avoided. This is especially true for repetition lessons.<br /> <br /> {{Info |2=Rationale|1=Keeping within this range ensures that a untrained typist (~120 characters per minute) can finish a lesson in five to ten minutes. Longer lessons get frustrating, shorter ones are ineffective.}}</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-05T17:09:21Z

<p>Sebastian: </p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Course Composition ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has to haptic markers for the keys belonging to we index fingers on the second row. These keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjklö&lt;/tt&gt; for the US keyboard layout.<br /> <br /> {{Info|2=Rationale|1=Those eight keys are the start position of each finger. One must internalize the location of these keys first to successfully learn touch typing.}}<br /> <br /> ; Introduce two new keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson focusing on the accent key alone.<br /> <br /> {{Info|2=Rationale|1= If more keys are introduced the trainee might get overwhelmed by the difficulty of the lesson and loose his motivation. Introduce keys for important keys for the ability to form real words earlier.}}<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced are the most or at least very frequently used characters in the lesson text.<br /> <br /> {{Info|2=Rationale|1=If the trainee passes a lesson he should have mastered the new keys. This is only possible if the lesson contains a significant amount of the new characters.}}<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: Every two to three lessons add a repetition lesson without new keys. These should have an even character mix covering all already introduced characters.<br /> <br /> {{Info|2=Rationale|1=Such lessons help to strengthen the acquired skills and and provide a way to check the overall training level. They are also better suited for repeated training to further improve one's general typing skills.}}<br /> <br /> ; Dedicated lessons for capitalization: There should be several lessons focusing sorely on capitalization. Ideally capitalization is introduced in multiple steps: At first only the left shift key, then the the right, then both and followed by one or more repetition lessons.<br /> <br /> {{Info|2=Rationale|1=Mastering capitalization is the most difficult part of learning touch typing. Therefore extra effort must be spend on these lessons.}}<br /> <br /> ; Cover the complete keyboard layout: This includes characters and symbols accessibly via additional modifiers. Ideally every character, number and symbol which is printed on a real keyboard should be covered.<br /> <br /> {{Info|2=Rationale|1=This keeps the course interesting for already advanced typists.}}<br /> <br /> == Lessons ==<br /> <br /> ; Give lessons a descriptive title: Name the the new characters if there are any or otherwise state what the lesson is about.<br /> <br /> {{Info|2=Rationale|1=Good titles make it easier to find the right course if one wants to train something specific.}}<br /> <br /> ; The lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on a freely chosen subject.<br /> <br /> {{Info|2=Rationale|1=Training with real words and sentences is more effective than with arbitrary random character combinations since it that is closer to real typing usage. And it is more fun.}}<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be uses. Do not employ misspelled words at all costs.<br /> <br /> {{Info|2=Rationale|1=Random character combinations are hard to type and are seldom found in day-to-day typing. Misspelled words on the other hand are confusing and have even a negative learning value, since the trainee may memorize the wrong spelling.}}<br /> <br /> ; Lesson text should be roughly 600 characters long: Texts may be longer, up to 1200 characters is okay, but shorter lessons should be avoided. This is especially true for repetition lessons.<br /> <br /> {{Info |2=Rationale|1=Keeping within this range ensures that a untrained typist (~120 characters per minute) can finish a lesson in five to ten minutes. Longer lessons get frustrating, shorter ones are ineffective.}}</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-05T15:35:25Z

<p>Sebastian: </p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Course Composition ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has to haptic markers for the keys belonging to we index fingers on the second row. These keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjklö&lt;/tt&gt; for the US keyboard layout.<br /> <br /> {{Info|2=Rationale|1=Those eight keys are the start position of each finger. One must internalize the location of these keys first to successfully learn touch typing.}}<br /> <br /> ; Introduce two new keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson focusing on the accent key alone.<br /> <br /> {{Info|2=Rationale|1= If more keys are introduced the trainee might get overwhelmed by the difficulty of the lesson and loose his motivation. Introduce keys for important keys for the ability to form real words earlier.}}<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced are the most or at least very frequently used characters in the lesson text.<br /> <br /> {{Info|2=Rationale|1=If the trainee passes a lesson he should have mastered the new keys. This is only possible if the lesson contains a significant amount of the new characters.}}<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: Every two to three lessons add a repetition lesson without new keys. These should have an even character mix covering all already introduced characters.<br /> <br /> {{Info|2=Rationale|1=Such lessons help to strengthen the acquired skills and and provide a way to check the overall training level. They are also better suited for repeated training to further improve one's general typing skills.}}<br /> <br /> ; Dedicated lessons for capitalization: There should be several lessons focusing sorely on capitalization. Ideally capitalization is introduced in multiple steps: At first only the left shift key, then the the right, then both and followed by one or more repetition lessons.<br /> <br /> {{Info|2=Rationale|1=Mastering capitalization is the most difficult part of learning touch typing. Therefore extra effort must be spend on these lessons.}}<br /> <br /> == Lessons ==<br /> <br /> ; Give lessons a descriptive title: Name the the new characters if there are any or otherwise state what the lesson is about.<br /> <br /> {{Info|2=Rationale|1=Good titles make it easier to find the right course if one wants to train something specific.}}<br /> <br /> ; The lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on a freely chosen subject.<br /> <br /> {{Info|2=Rationale|1=Training with real words and sentences is more effective than with arbitrary random character combinations since it that is closer to real typing usage. And it is more fun.}}<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be uses. Do not employ misspelled words at all costs.<br /> <br /> {{Info|2=Rationale|1=Random character combinations are hard to type and are seldom found in day-to-day typing. Misspelled words on the other hand are confusing and have even a negative learning value, since the trainee may memorize the wrong spelling.}}<br /> <br /> ; Lesson text should be roughly 600 characters long: Texts may be longer, up to 1200 characters is okay, but shorter lessons should be avoided. This is especially true for repetition lessons.<br /> <br /> {{Info |2=Rationale|1=Keeping within this range ensures that a untrained typist (~120 characters per minute) can finish a lesson in five to ten minutes. Longer lessons get frustrating, shorter ones are ineffective.}}</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-05T15:34:43Z

<p>Sebastian: /* Lessons */</p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Course Composition ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has to haptic markers for the keys belonging to we index fingers on the second row. These keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjklö&lt;/tt&gt; for the US keyboard layout.<br /> <br /> {{Info|2=Rationale|1=Those eight keys are the start position of each finger. One must internalize the location of these keys first to successfully learn touch typing.}}<br /> <br /> ; Introduce two new keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson focusing on the accent key alone.<br /> <br /> {{Info|2=Rationale|1= If more keys are introduced the trainee might get overwhelmed by the difficulty of the lesson and loose his motivation. Introduce keys for important keys for the ability to form real words earlier.}}<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced are the most or at least very frequently used characters in the lesson text.<br /> <br /> {{Info|2=Rationale|1=If the trainee passes a lesson he should have mastered the new keys. This is only possible if the lesson contains a significant amount of the new characters.}}<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: Every two to three lessons add a repetition lesson without new keys. These should have an even character mix covering all already introduced characters.<br /> <br /> {{Info|2=Rationale|1=Such lessons help to strengthen the acquired skills and and provide a way to check the overall training level. They are also better suited for repeated training to further improve one's general typing skills.}}<br /> <br /> ; Dedicated lessons for capitalization: There should be several lessons focusing sorely on capitalization. Ideally capitalization is introduced in multiple steps: At first only the left shift key, then the the right, then both and followed by one or more repetition lessons.<br /> <br /> {{Info|2=Rationale|1=Mastering capitalization is the most difficult part of learning touch typing. Therefore extra effort must be spend on these lessons.}}<br /> <br /> == Lessons ==<br /> <br /> ; Give lessons a descriptive title: Name the the new characters if there are any or otherwise state what the lesson is about.<br /> <br /> {{Info|2=Rationale|1=Good titles make it easier to find the right course if one wants to train something specific.}}<br /> <br /> ; The lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on a freely chosen subject.<br /> <br /> {{Info|2=Rationale|1=Training with real words and sentences is more effective than with arbitrary random character combinations since it that is closer to real typing usage. And it is more fun.}}<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be uses. Do not employ misspelled words at all costs.<br /> <br /> {{Info|2=Rationale|1=Random character combinations are hard to type and are seldom found in day-to-day typing. Misspelled words on the other hand are confusing and have even a negative learning value, since the trainee may memorize the wrong spelling.}}<br /> <br /> ; Lesson text should be roughly 600 characters long: Texts may be longer, up to 1200 characters is okay, but shorter lessons should be avoided. This is especially true for repetition lessons.<br /> <br /> {{Info |2=Rationale|1=Keeping within this range ensures that a untrained typist (~120 characters per minute) can finish a lesson in five to ten minutes. Longer lessons get frustrating, shorter ones are ineffective.}}t</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-05T15:34:10Z

<p>Sebastian: /* Lessons */</p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Course Composition ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has to haptic markers for the keys belonging to we index fingers on the second row. These keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjklö&lt;/tt&gt; for the US keyboard layout.<br /> <br /> {{Info|2=Rationale|1=Those eight keys are the start position of each finger. One must internalize the location of these keys first to successfully learn touch typing.}}<br /> <br /> ; Introduce two new keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson focusing on the accent key alone.<br /> <br /> {{Info|2=Rationale|1= If more keys are introduced the trainee might get overwhelmed by the difficulty of the lesson and loose his motivation. Introduce keys for important keys for the ability to form real words earlier.}}<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced are the most or at least very frequently used characters in the lesson text.<br /> <br /> {{Info|2=Rationale|1=If the trainee passes a lesson he should have mastered the new keys. This is only possible if the lesson contains a significant amount of the new characters.}}<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: Every two to three lessons add a repetition lesson without new keys. These should have an even character mix covering all already introduced characters.<br /> <br /> {{Info|2=Rationale|1=Such lessons help to strengthen the acquired skills and and provide a way to check the overall training level. They are also better suited for repeated training to further improve one's general typing skills.}}<br /> <br /> ; Dedicated lessons for capitalization: There should be several lessons focusing sorely on capitalization. Ideally capitalization is introduced in multiple steps: At first only the left shift key, then the the right, then both and followed by one or more repetition lessons.<br /> <br /> {{Info|2=Rationale|1=Mastering capitalization is the most difficult part of learning touch typing. Therefore extra effort must be spend on these lessons.}}<br /> <br /> == Lessons ==<br /> <br /> ; Give lessons a descriptive title: Name the the new characters if there are any or otherwise state what the lesson is about.<br /> <br /> {{Info|2=Rationale|1=Good titles make it easier to find the right course if one wants to train something specific.}}<br /> <br /> ; The lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on a freely chosen subject.<br /> <br /> {{Info|2=Rationale|1=Training with real words and sentences is more effective than with arbitrary random character combinations since it that is closer to real typing usage. And it is more fun.}}<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be uses. Do not employ misspelled words at all costs.<br /> <br /> {{Info|2=Rationale|1=Random character combinations are hard to type and are seldom found in day-to-day typing. Misspelled words on the other hand are confusing and have even a negative learning value, since the trainee may memorize the wrong spelling.}}<br /> <br /> ; Lesson text should be roughly 600 characters long: Texts may be longer, up to 1200 characters is okay, but shorter lessons should be avoided. This is especially true for repetition lessons.<br /> <br /> {{Info |2=Rationale|1=Keeping within this range ensures that a untrained types (~120 characters per minute) can finish a lesson in five to ten minutes. Longer lessons get frustrating, shorter ones are ineffective.}}</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-05T15:32:51Z

<p>Sebastian: </p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Course Composition ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has to haptic markers for the keys belonging to we index fingers on the second row. These keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjklö&lt;/tt&gt; for the US keyboard layout.<br /> <br /> {{Info|2=Rationale|1=Those eight keys are the start position of each finger. One must internalize the location of these keys first to successfully learn touch typing.}}<br /> <br /> ; Introduce two new keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson focusing on the accent key alone.<br /> <br /> {{Info|2=Rationale|1= If more keys are introduced the trainee might get overwhelmed by the difficulty of the lesson and loose his motivation. Introduce keys for important keys for the ability to form real words earlier.}}<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced are the most or at least very frequently used characters in the lesson text.<br /> <br /> {{Info|2=Rationale|1=If the trainee passes a lesson he should have mastered the new keys. This is only possible if the lesson contains a significant amount of the new characters.}}<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: Every two to three lessons add a repetition lesson without new keys. These should have an even character mix covering all already introduced characters.<br /> <br /> {{Info|2=Rationale|1=Such lessons help to strengthen the acquired skills and and provide a way to check the overall training level. They are also better suited for repeated training to further improve one's general typing skills.}}<br /> <br /> ; Dedicated lessons for capitalization: There should be several lessons focusing sorely on capitalization. Ideally capitalization is introduced in multiple steps: At first only the left shift key, then the the right, then both and followed by one or more repetition lessons.<br /> <br /> {{Info|2=Rationale|1=Mastering capitalization is the most difficult part of learning touch typing. Therefore extra effort must be spend on these lessons.}}<br /> <br /> == Lessons ==<br /> <br /> ; Give lessons a descriptive title: Name the the new characters if there are any or otherwise state what the lesson is about.<br /> <br /> {{Info|2=Rationale|1=Good titles make it easier to find the right course if one wants to train something specific.}}<br /> <br /> ; The lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on a freely chosen subject.<br /> <br /> {{Info|2=Rationale|1=Training with real words and sentences is more effective than with arbitrary random character combinations since it that is closer to real typing usage. And it is more fun.}}<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be uses. Do not employ misspelled words at all costs.<br /> <br /> {{Info|2=Rationale|1=Random character combinations are hard to type and are seldom found in day-to-day typing. Misspelled words on the other hand are confusing and have even a negative learning value, since the trainee may memorize the wrong spelling.}}<br /> <br /> ; Lesson text should be roughly 600 characters long: Texts may be longer, up to 1200 characters is okay, but shorter lessons should be avoided. This is especially true for repetition lessons.<br /> <br /> {{Info |2=Rationale|1=Keeping within this range ensured that a untrained types (~120 characters per minute) can finish a lesson in five to ten minutes. Longer lessons get frustrating, shorter ones are ineffective.}}</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-05T15:25:30Z

<p>Sebastian: </p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Course Composition ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has to haptic markers for the keys belonging to we index fingers on the second row. These keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjklö&lt;/tt&gt; for the US keyboard layout.<br /> <br /> {{Info|2=Rationale|1=Those eight keys are the start position of each finger. One must internalize the location of these keys first to successfully learn touch typing.}}<br /> <br /> ; Introduce two new keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson focusing on the accent key alone.<br /> <br /> {{Info|2=Rationale|1= If more keys are introduced the trainee might get overwhelmed by the difficulty of the lesson and loose his motivation. Introduce keys for important keys for the ability to form real words earlier.}}<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced are the most or at least very frequently used characters in the lesson text.<br /> <br /> {{Info|2=Rationale|1=If the trainee passes a lesson he should have mastered the new keys. This is only possible if the lesson contains a significant amount of the new characters.}}<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: Every two to three lessons add a repetition lesson without new keys. These should have an even character mix covering all already introduced characters.<br /> <br /> {{Info|2=Rationale|1=Such lessons help to strengthen the acquired skills and and provide a way to check the overall training level. They are also better suited for repeated training to further improve one's general typing skills.}}<br /> <br /> ; Dedicated lessons for capitalization: There should be several lessons focusing sorely on capitalization. Ideally capitalization is introduced in multiple steps: At first only the left shift key, then the the right, then both and followed by one or more repetition lessons.<br /> <br /> {{Info|2=Rationale|1=Mastering capitalization is the most difficult part of learning touch typing. Therefore extra effort must be spend on these lessons.}}<br /> <br /> == Lessons ==<br /> <br /> ; Give lessons a descriptive title: Name the the new characters if there are any or otherwise state what the lesson is about.<br /> <br /> {{Info|2=Rationale|1=Good titles make it easier to fi}}<br /> <br /> ; The lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on a freely chosen subject.<br /> <br /> {{Info|2=Rationale|1=Training with real words and sentences is more effective than with arbitrary random character combinations since it that is closer to real typing usage. And it is more fun.}}<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be uses. Do not employ misspelled words at all costs.<br /> <br /> {{Info|2=Rationale|1=Random character combinations are hard to type and are seldom found in day-to-day typing. Misspelled words on the other hand are confusing and have even a negative learning value, since the trainee may memorize the wrong spelling.}}<br /> <br /> ; Lesson text should be roughly 600 characters long: Texts may be longer, up to 1200 characters is okay, but shorter lessons should be avoided. This is especially true for repetition lessons.<br /> <br /> {{Info |2=Rationale|1=Keeping within this range ensured that a untrained types (~120 characters per minute) can finish a lesson in five to ten minutes. Longer lessons get frustrating, shorter ones are ineffective.}}</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-05T15:24:21Z

<p>Sebastian: </p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Course Composition ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has to haptic markers for the keys belonging to we index fingers on the second row. These keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjklö&lt;/tt&gt; for the US keyboard layout.<br /> <br /> {{Info|2=Rationale|1=Those eight keys are the start position of each finger. One must internalize the location of these keys first to successfully learn touch typing.}}<br /> <br /> ; Introduce two new keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson focusing on the accent key alone.<br /> <br /> {{Info|2=Rationale|1= If more keys are introduced the trainee might get overwhelmed by the difficulty of the lesson and loose his motivation. Introduce keys for important keys for the ability to form real words earlier.}}<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced are the most or at least very frequently used characters in the lesson text.<br /> <br /> {{Info|2=Rationale|1=If the trainee passes a lesson he should have mastered the new keys. This is only possible if the lesson contains a significant amount of the new characters.}}<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: Every two to three lessons add a repetition lesson without new keys. These should have an even character mix covering all already introduced characters.<br /> <br /> {{Info|2=Rationale|1=Such lessons help to strengthen the acquired skills and and provide a way to check the overall training level. They are also better suited for repeated training to further improve one's general typing skills.}}<br /> <br /> ; Dedicated lessons for capitalization: There should be several lessons focusing sorely on capitalization. Ideally capitalization is introduced in multiple steps: At first only the left shift key, then the the right, then both and followed by one or more repetition lessons.<br /> <br /> {{Info|2=Rationale|1=Mastering capitalization is the most difficult part of learning touch typing. Therefore extra effort must be spend on these lessons.}}<br /> <br /> == Lessons ==<br /> <br /> ; Give lessons a descriptive title: Name the the new characters if there are any or otherwise state what the lesson is about.<br /> <br /> {{Info|2=Rationale|1=Good titles make it easier to fi}}<br /> <br /> ; The lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on a freely chosen subject.<br /> <br /> {{Info|2=Rationale|1=Training with real words and sentences is more effective than with arbitrary random character combinations since it that is closer to real typing usage. And it is more fun.}}<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be uses. Do not employ misspelled words at all costs.<br /> <br /> {{Info|2=Rationale|1=Random character combinations are hard to type and are seldom found in day-to-day typing. Misspelled words on the other hand are confusing and have even a negative learning value, since the trainee may memorize the wrong spelling.}}<br /> <br /> ; Lesson text should be roughly 600 characters long: Texts may be longer, up too 1200 characters is okay, but shorter lessons should be avoided. This is especially true for repetition lessons.<br /> <br /> {{Info |2=Rationale|1=Keeping within this range ensured that a untrained types (~120 characters per minute) can finish a lesson in five to ten minutes. Longer lessons get frustrating, shorter ones are ineffective.}}</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-05T15:22:26Z

<p>Sebastian: </p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Course Composition ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has to haptic markers for the keys belonging to we index fingers on the second row. These keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjklö&lt;/tt&gt; for the US keyboard layout.<br /> <br /> {{Info|2=Rationale|1=Those eight keys are the start position of each finger. One must internalize the location of these keys first to successfully learn touch typing.}}<br /> <br /> ; Introduce two new keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson focusing on the accent key alone.<br /> <br /> {{Info|2=Rationale|1= If more keys are introduced the trainee might get overwhelmed by the difficulty of the lesson and loose his motivation. Introduce keys for important keys for the ability to form real words earlier.}}<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced are the most or at least very frequently used characters in the lesson text.<br /> <br /> {{Info|2=Rationale|1=If the trainee passes a lesson he should have mastered the new keys. This is only possible if the lesson contains a significant amount of the new characters.}}<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: Every two to three lessons add a repetition lesson without new keys. These should have an even character mix covering all already introduced characters.<br /> <br /> {{Info|2=Rationale|1=Such lessons help to strengthen the acquired skills and and provide a way to check the overall training level. They are also better suited for repeated training to further improve one's general typing skills.}}<br /> <br /> ; Dedicated lessons for capitalization: There should be several lessons focusing sorely on capitalization. Ideally capitalization is introduced in multiple steps: At first only the left shift key, then the the right, then both and followed by one or more repetition lessons.<br /> <br /> {{Info|2=Rationale|1=Mastering capitalization is the most difficult part of learning touch typing. Therefore extra effort must be spend on these lessons.}}<br /> <br /> == Lessons ==<br /> <br /> ; Give lessons a descriptive title: Name the the new characters if there are any or otherwise state what the lesson is about.<br /> <br /> {{Info|2=Rationale|1=Good titles make it easier to fi}}<br /> <br /> ; The lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on a freely chosen subject.<br /> <br /> {{Info|2=Rationale|1=Training with real words and sentences is more effective than with arbitrary random character combinations since it that is closer to real typing usage. And it is more fun.}}<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be uses. Do not employ misspelled words at all costs.<br /> <br /> {{Info|2=Rationale|1=Random character combinations are hard to type and are seldom found in day-to-day typing. Misspelled words on the other hand are confusing and have even a negative learning value, since the trainee may memorize the wrong spelling.}}<br /> <br /> ; Lesson text should be roughly 600 characters long: Texts may be longer, up too 1200 characters is okay, but shorter lessons should be avoided. This is especially true for repetition lessons.<br /> <br /> {{Info |2=Rationale|1=Keeping within this range ensured that a untrained types (~120 characters per minute) can finish the a lesson in five to ten minutes. Longer lessons get frustrating, shorter ones are ineffective.}}</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-05T13:52:40Z

<p>Sebastian: </p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Lessons should establish a course ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has to haptic markers for the keys belonging to we index fingers on the second row. These keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjklö&lt;/tt&gt; for the US keyboard layout.<br /> <br /> {{Info|2=Rationale|1=Those eight keys are the start position of each finger. One must internalize the location of these keys first to successfully learn touch typing.}}<br /> <br /> ; Introduce two new keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson focusing on the accent key alone.<br /> <br /> {{Info|2=Rationale|1= If more keys are introduced the trainee might get overwhelmed by the difficulty of the lesson and loose his motivation. Introduce keys for important keys for the ability to form real words earlier.}}<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced are the most or at least very frequently used characters in the lesson text.<br /> <br /> {{Info|2=Rationale|1=If the trainee passes a lesson he should have mastered the new keys. This is only possible if the lesson contains a significant amount of the new characters.}}<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: Every two to three lessons add a repetition lesson without new keys. These should have an even character mix covering all already introduced characters.<br /> <br /> {{Info|2=Rationale|1=Such lessons help to strengthen the acquired skills and and provide a way to check the overall training level. They are also better suited for repeated training to further improve one's general typing skills.}}<br /> <br /> ; Dedicated lessons for capitalization: There should be several lessons focusing sorely on capitalization. Ideally capitalization is introduced in multiple steps: At first only the left shift key, then the the right, then both and followed by one or more repetition lessons.<br /> <br /> {{Info|2=Rationale|1=Mastering capitalization is the most difficult part of learning touch typing. Therefore extra effort must be spend these lessons.}}<br /> <br /> == Text should be plausible ==<br /> <br /> ;Lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on a freely chosen subject.<br /> <br /> {{Info|2=Rationale|1=Training with real words and sentences is more effective than with arbitrary random character combinations since it that is closer to real typing usage. And it is more fun.}}<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be uses. Do not employ misspelled words at all costs.<br /> <br /> {{Info|2=Rationale|1=Random character combinations are hard to type and are seldom found in day-to-day typing. Misspelled words on the other hand are confusing and have even a negative learning value, since the trainee may memorize the wrong spelling.}}</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-05T12:44:43Z

<p>Sebastian: </p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Lessons should establish a course ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has to haptic markers for the keys belonging to we index fingers on the second row. These keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjklö&lt;/tt&gt; for the US keyboard layout.<br /> <br /> ; Introduce two new keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson focusing on the accent key alone.<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced are the most or at least very frequently used characters in the lesson text.<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: These should have an even character mix covering all already introduced characters.<br /> <br /> ; Dedicated lessons for capitalization: There should be several lessons focusing sorely on capitalization. <br /> <br /> == Text should be plausible ==<br /> <br /> ;Lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on some subject.<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be uses. Do not employ misspelled words at all cost.</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-05T11:09:19Z

<p>Sebastian: </p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Lessons should establish a course ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has to haptic markers for the keys belonging to we index fingers on the second row. These keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjklö&lt;/tt&gt; for the US keyboard layout.<br /> <br /> ; Introduce more two keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson focusing on the accent key alone.<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced are the most or at least very frequently used characters in the lesson text.<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: These should have an even character mix covering all already introduced characters.<br /> <br /> == Text should be plausible ==<br /> <br /> ;Lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on some subject.<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be uses. Do not employ misspelled words at all cost.</div>

Sebastian http://techbase.kde.org/User:Sebastian/CourseQuality 2012-11-05T11:08:17Z

<p>Sebastian: Created page with &quot;= Quality Criteria for Courses = A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements. ==...&quot;</p> <hr /> <div>= Quality Criteria for Courses =<br /> <br /> A course is a ordered set of lessons. To be efficient for learning touch typing the content of the course should meet a few requirements.<br /> <br /> == Lessons should establish a course ==<br /> <br /> ;The first lesson should cover the home keys: Usually a keyboard has to haptic markers for the keys belonging to we index fingers on the second row. These keys and the three adjacent keys outwards are the home keys. That's &lt;tt&gt;asdfjklö&lt;/tt&gt; for the US keyboard layout.<br /> <br /> ; Introduce more two new keys per lesson: The unlocking order of keys is not fixed, but usually keys are introduced in pairs belonging to the same finger on both hands. Make your way from the home keys to the ones further away. Thus, the forth row should be introduced at last. Prefer keys for important characters of your language, this may require to bend the introduction pattern a bit. For example in French accents are really important, this warrants a lesson focusing on the accent key alone.<br /> <br /> ; Extra emphasis on the new keys: Make sure the characters belonging to the newly introduced are the most or at least very frequently used characters in the lesson text.<br /> <br /> ; Intersperse lessons with new keys with repetition lessons: These should have an even character mix covering all already introduced characters.<br /> <br /> == Text should be plausible ==<br /> <br /> ;Lesson text should be composed out of real words and sentences: Optimally a lesson forms a comprehensible contiguous text on some subject.<br /> <br /> ;Avoid non-word character combinations: This may impossible in the very first lessons where only a few characters are available, but as soon as possible only real words should be uses. Do not employ misspelled words at all cost.</div>

Sebastian http://techbase.kde.org/User:Sebastian 2012-11-05T11:07:53Z

<p>Sebastian: </p> <hr /> <div>[[/CourseQuality]]</div>

Sebastian http://techbase.kde.org/User:Sebastian 2012-11-05T11:07:39Z

<p>Sebastian: Created page with &quot;CourseQuality&quot;</p> <hr /> <div>[[CourseQuality]]</div>

Sebastian http://techbase.kde.org/Projects/Edu/KTouch 2012-11-05T09:42:23Z

<p>Sebastian: /* About KTouch */ fix typo</p> <hr /> <div>== About KTouch ==<br /> <br /> KTouch is a touch typing trainer. [http://userbase.kde.org/KTouch More on Userbase]<br /> <br /> == Developer Information ==<br /> <br /> ;[[/Courses|Overview over courses]]<br /> ;[[/CourseQuality|Quality criteria for courses]]</div>

Sebastian http://techbase.kde.org/Projects/Edu/KTouch 2012-11-05T09:41:30Z

<p>Sebastian: create page for KTouch</p> <hr /> <div>== About KTouch ==<br /> <br /> KTouch is a touch typing trainer. [http://userbase.kde.org/KTouch More on on Userbase]<br /> <br /> == Developer Information ==<br /> <br /> ;[[/Courses|Overview over courses]]<br /> ;[[/CourseQuality|Quality criteria for courses]]</div>

Sebastian http://techbase.kde.org/Projects/Edu 2012-11-05T09:22:03Z

<p>Sebastian: /* Miscellaneous */ add KTouch</p> <hr /> <div><br /> Educational Software for KDE<br /> <br /> [[/ProjectSuggestions|Project Suggestions]]: a list of suggestions for future Edu (and some non-Edu) projects. If you're a developer, and in need of something to do, pick a suggestion and see what you can come up with! :)<br /> == Development ==<br /> * [[KNewStuff2 Development Page]]<br /> <br /> == Developer Resources for Applications ==<br /> <br /> === Languages ===<br /> {| style=&quot;width:100%&quot;<br /> {{EduAppCell|name=KAnagram|link=Projects/Edu/KAnagram|icon=Kanagram.png}}<br /> {{EduAppCell|name=KHangman|link=Projects/Edu/Khangman|icon=Khangman.png}}<br /> {{EduAppCell|name=Kiten|link=Projects/Edu/Kiten|icon=Kiten.png}}<br /> {{EduAppCell|name=KLettres|link=Projects/Edu/KLettres|icon=Klettres.png}}<br /> |-<br /> {{EduAppCell|name=Parley|link=Projects/Edu/Parley|icon=Parley.png}}<br /> |}<br /> <br /> === Mathematics ===<br /> {| style=&quot;width:100%&quot;<br /> {{EduAppCell|name=Cantor|link=Projects/Edu/Cantor|icon=Cantor.png}}<br /> {{EduAppCell|name=KAlgebra|link=Projects/Edu/KAlgebra|icon=Kalgebra.png}}<br /> {{EduAppCell|name=KBruch|link=Projects/Edu/KBruch|icon=Kbruch.png}}<br /> {{EduAppCell|name=Kig|link=Projects/Edu/Kig|icon=Kig.png}}<br /> |-<br /> {{EduAppCell|name=KmPlot|link=Projects/Edu/KmPlot|icon=Kmplot.png}}<br /> |}<br /> <br /> === Miscellaneous ===<br /> <br /> {| style=&quot;width:100%&quot;<br /> {{EduAppCell|name=blinKen|link=Projects/Edu/blinKen|icon=Blinken.png}}<br /> {{EduAppCell|name=Kard|link=Projects/Edu/Kard}}<br /> {{EduAppCell|name=KGeography|link=Projects/Edu/KGeography|icon=Kgeography.png}}<br /> {{EduAppCell|name=KidsPlay|link=Projects/Edu/KidsPlay}}<br /> |-<br /> {{EduAppCell|name=KTurtle|link=Projects/Edu/KTurtle|icon=Kturtle.png}}<br /> {{EduAppCell|name=KWordQuiz|link=Projects/Edu/KWordQuiz|icon=Kwordquiz.png}}<br /> {{EduAppCell|name=KTouch|link=Projects/Edu/KTouch|icon=ktouch.png}}<br /> |}<br /> <br /> === Science ===<br /> <br /> {| style=&quot;width:100%&quot;<br /> {{EduAppCell|name=Kalzium|link=Projects/Edu/Kalzium|icon=Kalzium.png}}<br /> {{EduAppCell|name=KStars|link=Projects/Edu/KStars|icon=Kstars.png}}<br /> {{EduAppCell|name=Marble|link=Projects/Marble|icon=Marble.png}}<br /> {{EduAppCell|name=Step|link=Projects/Edu/Step|icon=Step.png}}<br /> |-<br /> {{EduAppCell|name=Rocs|link=Projects/Edu/Rocs}}<br /> |}<br /> <br /> === Teaching Tools ===<br /> <br /> {| style=&quot;width:100%&quot; border=&quot;0&quot;<br /> {{EduAppCell|name=KEduca|link=Projects/Edu/KEduca|icon=Keduca.png}} <br /> | &amp;nbsp;<br /> | &amp;nbsp;<br /> | &amp;nbsp;<br /> |}<br /> <br /> == Resources ==<br /> <br /> Here you have generic development resources for KDE-Edu.<br /> <br /> * [[/Using_Custom_Fonts|Using Custom Fonts]]<br /> * [[/kvtml2|kvtml2 file format]]<br /> <br /> [[Category:education]]</div>

Sebastian http://techbase.kde.org/Schedules/KDE4/4.10_Feature_Plan 2012-11-04T11:17:44Z

<p>Sebastian: two more features for KTouch done</p> <hr /> <div>This is a list of planned features for the SC 4.10 release. <br /> <br /> See also: <br /> <br /> *[[Schedules/KDE4/4.10 Release Schedule]] <br /> *[[Schedules/KDE4/4.9 Feature Plan]] (previous major release)<br /> <br /> &lt;br&gt; Legend: <br /> <br /> *todo =&amp;gt; not started yet <br /> *in-progress =&amp;gt; started, but not completed yet <br /> *done =&amp;gt; completed<br /> <br /> __TOC__ <br /> <br /> &lt;br&gt;<br /> <br /> = kdelibs =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> |}<br /> &lt;b&gt;NO NEW FEATURES ALLOWED&lt;/b&gt;<br /> &lt;br&gt;<br /> <br /> = kde-runtime =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|kio-mtp|KIO-Slave for MTP|philschmidt@gmx.net|Philipp Schmidt}}<br /> {{FeatureInProgress|QML Containments|Making it possible to do full-featured containments in QML|sebas@kde.org|Sebastian Kügler}}<br /> {{FeatureInProgress|nepomuk-indexer|New Nepomuk Indexer|me@vhanda.in|Vishesh Handa}}<br /> {{FeatureInProgress|nepomukbakcup|Nepomuk Backup rewritten from scratch|me@vhanda.in|Vishesh Handa}}<br /> {{FeatureInProgress|nepomukcleaner|An application to port/clean invalid/legacy data in Nepomuk|me@vhanda.in|Vishesh Handa}}<br /> {{FeatureInProgress|nepomuk KCM|Rewrite the Nepomuk KCM|me@vhanda.in|Vishesh Handa}}<br /> {{FeatureInProgress|nepomuk tags|Nepomuk Tags KIO Slave|me@vhanda.in|Vishesh Handa}}<br /> {{FeatureInProgress|nepomuk filemetadtawdiget|Nepomuk Metadata Widget|me@vhanda.in|Vishesh Handa}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kde-workspace =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|ksmserver|Merge the new qml based screen locker|mart@kde.org|Marco Martin}}<br /> <br /> &lt;!-- The following section of entries has been auto generated by ChangelogGenerator. Do not edit!<br /> BEGIN GENERATED SECTION --&gt;<br /> {{FeatureTodo|kwin|windows that are moved to another desktop should be treated as sticky windows ({{bug |213847}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Fix fullscreen state handling: NETWM says it's bound to focus and not stacking order, also see bug #224600 ({{bug |296076}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Medium focus stealing prevention should also prevent focus stealing when the timestamp on the active window is uncertain ({{bug |304746}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Usability issue: &quot;Attach as tab to&quot; menu can be empty ({{bug |306451}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Display application menu and title bar side by side for maximized windows ({{bug |102607}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Add support for appmenu-qt ({{bug |266596}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Import Scripted Effect from All Effets Tab ({{bug |296772}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|GHNS support for Scripted Effects ({{bug |296773}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Window Tab support for QML based Aurorae ({{bug |299138}})|kwin-bugs-null@kde.org}}<br /> {{FeatureInProgress|kwin|Remove legacy window decorations ({{bug |299144}}, Review 104281)|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Get rid of &quot;Display borders on maximized windows&quot; setting ({{bug |299245}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Break NETWM to allow inner xinerama struts ({{bug |299247}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Cube animation on border approach should not be used unless the electric borders are actually in use and the config should be disabled, align or hint the electric border configuration ({{bug |299901}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Make ShaderManager act as a real stack ({{bug |300349}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|clientPopup: &quot;'More actions' and &quot;Attach as tab to&quot; lack mnemonics ({{bug |302833}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Make KWin compile with C++11 ({{bug |303313}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Copy all useful Client properties to Deleted ({{bug |303916}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Display content of resizing/moving windows: KDE-Help shows obsolete instructions ({{bug |305297}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Mouse action support for sending window to different activity ({{bug |305758}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Windows list icon does not show up in &quot;Walk Through Desktop List&quot; ({{bug |306187}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Game mode ({{bug |306448}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Animate Window Maximize/Restore ({{bug |308990}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Common animation settings for effects of same type ({{bug |308991}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Use Resize Area in Aurorae ({{bug |308992}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Configurable quick tile area config GUI ({{bug |308993}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Move ExtendedBorderRegion to stable API ({{bug |308994}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Support shortened titles like in bespin in all decorations ({{bug |308995}})|kwin-bugs-null@kde.org}}<br /> {{FeatureInProgress|kwin|Mouse Click effect ({{bug |309006}}, Review 105780)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Decorations not visible ({{bug |305875}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|drag-and-drop between windows by cover switch alt-tab causes apps to crash ({{bug |179077}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Add a rule to select the screen ({{bug |183996}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|JJ: Need Mouse navigation in flip switch mode ({{bug |244439}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Request category for scripted KWin Effects on kde-(look&lt;nowiki&gt;|&lt;/nowiki&gt;app).org ({{bug |297634}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Request category for KWin Scripts on kde-(look&lt;nowiki&gt;|&lt;/nowiki&gt;app).org ({{bug |297635}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Request category for Window Switcher Layouts on kde-(look&lt;nowiki&gt;|&lt;/nowiki&gt;app).org ({{bug |297637}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Allow direct rendering with fglrx ({{bug |301103}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Don't use OpenGL matrix stack in OpenGL 2 backend ({{bug |303093}}, Review 105455)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Refactor Screen/Window PaintData ({{bug |303314}}, Review 105141)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Rapid flickering in locked screen -- makes it difficult to unlock ({{bug |303579}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|double click menu to close needs GUI config ({{bug |305738}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Toplevel::windowType() needs performance improvements ({{bug |306384}}, Review 106349)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|GLPlatform should recommend either OpenGL1 or OpenGL2 compositing ({{bug |306436}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Zoom effect broken in master ({{bug |307609}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|kwin fails to build when the GLES support is disabled ({{bug |307866}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|[JJ] Some effect authors are listed as &quot;Name1 &amp; Name2&quot; ({{bug |307928}}, Review 106880)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Add screen management actions to window context menus ({{bug |269207}}, Review 106065)|mgraesslin@kde.org}}<br /> {{FeatureDone|kwin|Move Workspace's compositing functionality to own class Compositor ({{bug |299277}}, Review 102420)|mgraesslin@kde.org}}<br /> {{FeatureDone|kwin|Option to disable close on double click in Aurorae ({{bug |301327}}, Review 106160)|mgraesslin@kde.org}}<br /> {{FeatureDone|kwin|Remove Tiling Support From KWin ({{bug |303090}}, Review 105546)|mgraesslin@kde.org}}<br /> {{FeatureDone|kwin|Allow Scripts to add menus to useractions menu ({{bug |303756}}, Review 106285)|mgraesslin@kde.org}}<br /> {{FeatureDone|kwin|Generic QML support for Aurorae Themes ({{bug |303810}}, Review 105768)|mgraesslin@kde.org}}<br /> {{FeatureDone|kwin|Split out Useractions Menu from Workspace ({{bug |305832}}, Review 106085)|mgraesslin@kde.org}}<br /> <br /> &lt;!-- END GENERATED SECTION --&gt;<br /> {{FeatureInProgress|kwin|Implement color correction (Review 106141)|skeletk13@gmail.com|Casian Andrei}}<br /> {{FeatureInProgress|oxygen decoration|Implement ExtendedBorderRegion support, to resize windows outside of their actual borders|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}<br /> {{FeatureDone|oxygen style|Implement BlurBehind semi-transparent tooltips when available|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}<br /> {{FeatureDone|plasma-wallpapers|Color wallpaper: add listview to display thumbnails for background mode|rshah0385@kireihana.com|Reza Fatahilah Shah}}<br /> {{FeatureInProgress|plasma workspace|Port Notifications applet to QML|mart@kde.org|Marco Martin}}<br /> {{FeatureInProgress|plasma workspace|Port Task Manager applets to QML|hein@kde.org|Eike Hein (Sho_)}}<br /> {{FeatureInProgress|plasma workspace|refresh Air Plasma theme|mart@kde.org|Marco Martin}}<br /> {{FeatureInProgress|plasma workspace|Port Kickoff to qml|yellowcake-@gmx.net|Greg T}}<br /> {{FeatureInProgress|systemsettings|Replace krandr KCM by libkscreen-based one|dvratil@redhat.com|Dan Vrátil}}<br /> {{FeatureInProgress|plasma workspace|Port rssnow to qml|terietor@gmail.com|Giorgos Tsiapaliokas}}<br /> {{FeatureInProgress|various|KActivities/SLC support for most our applications|ivan.cukic@kde.org|Ivan Čukić}}<br /> {{FeatureInProgress|plasma workspace|first desktop SLC applet release|mart@kde.org|Marco Martin}}<br /> {{FeatureDone|System Tray|System tray with interface in QML|dmitry.ashkadov@gmail.com|Dmitry Ashkadov}}<br /> {{FeatureTodo|plasma workspace|Top-rated documents for Task Manager|ivan.cukic@kde.org|Ivan Čukić}}<br /> {{FeatureInProgress|systemsettings|Keyboard layout preview|amourphious1992@gmail.com|Shivam Makkar}}<br /> {{FeatureInProgress|window manager|Rework and optimize vertex specification|fredrik@kde.org|Fredrik Höglund}}<br /> {{FeatureInProgress|window manager|Dynamic shader generation|fredrik@kde.org|Fredrik Höglund}}<br /> {{FeatureInProgress|window manager|Partial port to xcb|fredrik@kde.org|Fredrik Höglund}}<br /> {{FeatureInProgress|window manager|New launch feedback effect|fredrik@kde.org|Fredrik Höglund}}<br /> {{FeatureInProgress|activities|Encrypted activities|ivan.cukic@kde.org|Ivan Čukić}}<br /> {{FeatureInProgress|powerdevil|Improve profile error handling (DPMS)|kde@privat.broulik.de|Kai Uwe Broulik}}<br /> {{FeatureInProgress|plasma workspace|Social Feed|mklapetek@kde.org|Martin Klapetek}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kde-baseapps =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureTodo|FolderView|Split into PopupApplet and Containment|ignat.semenov@blue-systems.com|Ignat Semenov}}<br /> <br /> {{FeatureTodo|FolderView|Port to QML|ignat.semenov@blue-systems.com|Ignat Semenov}}<br /> <br /> {{FeatureTodo|Dolphin|Implement files quick preview feature (named Klook) |evgeniy.augin@osinit.ru|Evgeniy Auzhin}}<br /> <br /> {{FeatureDone|Dolphin|Implement parallel sort algorithm|emmanuelpescosta099@gmail.com|Emmanuel Pescosta}}<br /> <br /> {{FeatureDone|Dolphin|Add GUI option for the &quot;Rename Inline&quot; setting|frank78ac@googlemail.com|Frank Reininghaus}}<br /> <br /> {{FeatureDone|Dolphin|Add &quot;Icon Size&quot; submenu to the Places Panel context menu|frank78ac@googlemail.com|Frank Reininghaus}}<br /> <br /> {{FeatureDone|print-manager|New Print manager KCM and applet (plasmoid) replacement, using C++ |dantti12@gmail.com|Daniel Nicoletti}}<br /> <br /> {{FeatureDone|Kate|Support for Python plugins|srhaque@theiet.org|Shaheed Haque}}<br /> <br /> {{FeatureDone|Kate|Advanced gid(1) plugin using both ID files and etags|srhaque@theiet.org|Shaheed Haque}}<br /> <br /> {{FeatureTodo|Kate|As-you-type search for the search plugin|kare.sars@iki.fi|Kåre Särs}}<br /> <br /> {{FeatureTodo|Kate|Session name API for plugins + automatic ctags database naming|kare.sars@iki.fi|Kåre Särs}}<br /> <br /> {{FeatureInProgress|Kate|Add optional document &quot;minimap&quot; to the Symbols view plugin|kare.sars@iki.fi|Kåre Särs}}<br /> <br /> {{FeatureInProgress|Kate|Vim Mode Macro support|kdedevel@etothepiplusone.com|Simon St James}}<br /> <br /> {{FeatureTodo|Kdialog|Add support for detailedsorry/detailederror messages|kde@privat.broulik.de|Kai Uwe Broulik}}<br /> <br /> {{FeatureTodo|Konsole|Improve the search filter bar|francesco.cecconi@gmail.com|Francesco Cecconi}}<br /> <br /> {{FeatureTodo|Konsole|Add the --separate cmdline option for running in new process|adaptee@gmail.com|Jekyll Wu}}<br /> <br /> {{FeatureTodo|Konsole|Make the d&amp;d popup menu optional|adaptee@gmail.com|Jekyll Wu}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdeedu =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureTodo|Marble|Have support for &quot;repeatX&quot; in the projection classes|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Satellite Map NG|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Mars &amp; Venus satellite plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}<br /> {{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}<br /> {{FeatureTodo|Marble|Help Menu polishing / Support page inclusion|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Toolbar polishing/refactoring|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureInProgress|Marble|Worldwide hillshading|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Extended library API (no MarbleWidget dependency for tasks like parsing, routing)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Marble Touch on Plasma Active|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureInProgress|Marble|Foursquare plugin|utkuaydin34@gmail.com|Utku Aydın}}<br /> {{FeatureTodo|Marble|Marble Touch on Android (including SOK branch merge)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Support for loading geolocated photos (e.g. in a Gallery activity in Marble Touch)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Layer Management (by the user: Toggle layer visibility; maybe move layers from legend and layers in menus to one central place/tab)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|OSM vector rendering (GSOC branch merge)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Zoom to content of geo file after loading (at least on start-up)|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Marble|Geo files thumbnailer|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Marble|Geo files metadata extractor|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureDone|Rocs|Journal files for projects.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureInProgress|Rocs|Revisit graph export/import functionality to fully support: TGF, DOT, GML, GraphML|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Printing and image export of graphs.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Data Structure Snapshot and Recovery.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureDone|Rocs|Main Window UI Reorganization: Editor Toolbar, dialogs, Information Panel|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Visual Graph Editor Handling: copy&amp;paste, data structure focus, property display|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Visual Graph Editor Edit Menu|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureInProgress|Rocs|Configuration Dialog Optimizations: Code-Editor, Graph Editor|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Data Structure Backend wise iconsets and preconfigurations for types|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureDone|KTouch|Ship ktouch/next|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureDone|KTouch|Smart resizing of training screen with aligned vertical lines|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureDone|KTouch|Prominent hint during training if the user makes repeatedly errors|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureDone|KTouch|Show course descriptions in course selector|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureDone|KTouch|Show a message when keyboard layout visualization isn't available due missing data|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureDone|Analitza|New plotting framework|percy.camilo.ta@gmail.com|Percy Camilo Triveño Aucahuasi}}<br /> {{FeatureDone|KAlgebra|Splitted the QML Components from KAlgebraMobile|aleixpol@kde.org|Aleix Pol Gonzalez}}<br /> {{FeatureDone|KAlgebra|New plotting plasmoid graphs, in QtQuick|aleixpol@kde.org|Aleix Pol Gonzalez}}<br /> {{FeatureDone|Pairs|Pairs Theme editor|marco.calignano@gmail.com|Marco Calignano}}<br /> {{FeatureInProgress|Cantor|Python backend|filipe@kde.org|Filipe Saraiva}}<br /> {{FeatureInProgress|Kig|Mark right angles|david.narvaez@computer.org|David E. Narváez}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdegames=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|libkdegames|[http://community.kde.org/KDE_Games/API_cleanup Major cleanup and rewrite] (done, except for the new highscore classes)&lt;br/&gt;&lt;br/&gt;'''Release team:''' please link to the [[Projects/Games/Porting_to_libkdegames_v5|porting instructions]] for third-party developers|stefan.majewsky@googlemail.com|Stefan Majewsky}}<br /> {{FeatureDone|KGoldrunner|Use KGameRenderer and QGraphicsView for all graphics: the gameplay is the same as before.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KGoldrunner|Remove the status bar. All scores and status messages are in the viewport now.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Allow the displayed speed of moves to be adjusted.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Animate multi-stage moves, to make it easier for a human player to follow their progress.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Show multi-stage moves in an order that is easier to follow.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Validate the loading of saved games and report errors.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Rewrite the main AI class and make it use a true Minimax method.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Provide a choice of two AI styles, Kepler and Newton, with the possibility to add more.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Add settings to choose computer player, AI style and skill level for either or both of players 1 and 2.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Add board sizes 3x3 and 4x4, for simplified play.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KSudoku|Add a simple Print facility for KSudoku puzzles.|iandw.au@gmail.com|Ian Wadham}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdegraphics=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|libkipi|[http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/dodonvictor/10002 Porting libkipi to KDE-XML GUI]|dodonvictor@gmail.com|Victor Dodon}}<br /> {{FeatureInProgress|okular|Tiled rendering|okular-devel@kde.org|Okular Developers}}<br /> {{FeatureInProgress|Gwenview|Recursive importer|agateau@kde.org|Aurélien Gâteau}}<br /> {{FeatureInProgress|Gwenview|Color profile support|agateau@kde.org|Aurélien Gâteau}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdemultimedia =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|Juk|[http://community.kde.org/Juk#Porting_plan Port Juk away from kde3support]|martin.sandsmark@kde.org|Martin Sandsmark}}<br /> {{FeatureDone|Juk|Add lyrics view|martin.sandsmark@kde.org|Martin Sandsmark}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdenetwork=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|KGet|Metalink/HTTP Support|dahalaishraj@gmail.com|Aish Raj Dahal}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdepim =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> {{FeatureInProgress|Facebook resource|Include it in default install|martin.klapetek@gmail.com|Martin Klapetek}}<br /> {{FeatureInProgress|Akregator2|Merge in kdepim|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|Knode|Merge in KMail|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|BackupMail|Extend backup to all kdepim apps|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|Sieve|Rewrite dialogbox|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|libs|Move folderview to kdepimlibs/akonadi|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|kolab-resource|Make Kolab 3.0 option available|mollekopf@kolabsys.com|Christian Mollekopf}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdeplasma-addons =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> {{FeatureInProgress|Microblog|replace with QML version|sebas@kde.org|Sebastian Kügler}}<br /> {{FeatureInProgress|StackFolder|Add applet for quick browse the stack of folders|ural.mullabaev@rosalab.ru|Ural Mullabaev}}<br /> {{FeatureInProgress|ComicStrip|Replace with QML version|rshah0385@kireihana.com|Reza Fatahilah Shah}}<br /> {{FeatureInProgress|Calculator|Replace with QML version|luizromario@gmail.com|Luiz Romário Santana Rios}}<br /> {{FeatureDone|QML Wallpapers|Make it possible to have animated wallpapers written in QtQuick technologies.|aleixpol@blue-systems.com|Aleix Pol Gonzalez}}<br /> {{FeatureDone|Dictionary KRunner|Look up words in the dictionary by typing in 'define {word}' in krunner.|Jason@zx2c4.com|Jason A. Donenfeld}}<br /> {{FeatureInProgress|Eyes|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> {{FeatureInProgress|FifteenPuzzle|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> {{FeatureInProgress|Luna|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> {{FeatureInProgress|Timer|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdesdk =<br /> <br /> {| cellspa/cing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> {{FeatureTodo|Okteta|Add a general KPart adapter to Kasten, than finish port of Okteta KPart to Okteta Kasten|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Add global toggle option for the offset display, hex or decimal|kossebau@kde.org|Friedrich W. H. Kossebau}} <br /> {{FeatureTodo|Okteta|Add Kate-like combined dialogs to query for actions on files|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Add Okular like embedded notifications|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add support for import by drop, both url and data|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add support for memory mapping of files and 64-bit addressing|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add support for jobs like io, printing, string search or filter|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|copy again puts also a value or char variant of the data to clipboard|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Improve the titels of the changes to the bytearray to be more descriptive, best using ids to avoid text string|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Make all user interaction in the KastenCore managers plugin-based|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Merge row and column widgets into one|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Store bookmarks|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Store bookmarks and other view settings for next load|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Add custom datatypes to structures tool|alex.richardson@gmx.de|Alex Richardson}}<br /> {{FeatureInProgress|Okteta|Add tagged unions to structures tool|alex.richardson@gmx.de|Alex Richardson}}<br /> {{FeatureInProgress|Okteta|Add array indices to structures tool|alex.richardson@gmx.de|Alex Richardson}}<br /> {{FeatureDone|Umbrello|Line based diagram grid |ralf.habacker@freenet.de|Ralf Habacker}}<br /> {{FeatureTodo|Umbrello| widget resize and diagram auto resize feature |ralf.habacker@freenet.de|Ralf Habacker}}<br /> {{FeatureTodo|Umbrello|add spline based association lines to avoid autolayout widget/line overlapping (needs volunteers)|ralf.habacker@freenet.de|Ralf Habacker}}<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> = kdeutils=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|Ark|Make it possible to disable internal previewer|kde@privat.broulik.de|Kai Uwe Broulik}}<br /> |}<br /> &lt;br&gt;</div>

Sebastian http://techbase.kde.org/Schedules/KDE4/4.10_Feature_Plan 2012-10-30T18:08:23Z

<p>Sebastian: KTouch: Mark two features as done.</p> <hr /> <div>This is a list of planned features for the SC 4.10 release. <br /> <br /> See also: <br /> <br /> *[[Schedules/KDE4/4.10 Release Schedule]] <br /> *[[Schedules/KDE4/4.9 Feature Plan]] (previous major release)<br /> <br /> &lt;br&gt; Legend: <br /> <br /> *todo =&amp;gt; not started yet <br /> *in-progress =&amp;gt; started, but not completed yet <br /> *done =&amp;gt; completed<br /> <br /> __TOC__ <br /> <br /> &lt;br&gt;<br /> <br /> = kdelibs =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> |}<br /> &lt;b&gt;NO NEW FEATURES ALLOWED&lt;/b&gt;<br /> &lt;br&gt;<br /> <br /> = kde-runtime =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|kio-mtp|KIO-Slave for MTP|philschmidt@gmx.net|Philipp Schmidt}}<br /> {{FeatureInProgress|QML Containments|Making it possible to do full-featured containments in QML|sebas@kde.org|Sebastian Kügler}}<br /> {{FeatureInProgress|nepomuk-indexer|New Nepomuk Indexer|me@vhanda.in|Vishesh Handa}}<br /> {{FeatureInProgress|nepomukbakcup|Nepomuk Backup rewritten from scratch|me@vhanda.in|Vishesh Handa}}<br /> {{FeatureInProgress|nepomukcleaner|An application to port/clean invalid/legacy data in Nepomuk|me@vhanda.in|Vishesh Handa}}<br /> {{FeatureInProgress|nepomuk KCM|Rewrite the Nepomuk KCM|me@vhanda.in|Vishesh Handa}}<br /> {{FeatureInProgress|nepomuk tags|Nepomuk Tags KIO Slave|me@vhanda.in|Vishesh Handa}}<br /> {{FeatureInProgress|nepomuk filemetadtawdiget|Nepomuk Metadata Widget|me@vhanda.in|Vishesh Handa}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kde-workspace =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|ksmserver|Merge the new qml based screen locker|mart@kde.org|Marco Martin}}<br /> <br /> &lt;!-- The following section of entries has been auto generated by ChangelogGenerator. Do not edit!<br /> BEGIN GENERATED SECTION --&gt;<br /> {{FeatureTodo|kwin|windows that are moved to another desktop should be treated as sticky windows ({{bug |213847}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Fix fullscreen state handling: NETWM says it's bound to focus and not stacking order, also see bug #224600 ({{bug |296076}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Medium focus stealing prevention should also prevent focus stealing when the timestamp on the active window is uncertain ({{bug |304746}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Usability issue: &quot;Attach as tab to&quot; menu can be empty ({{bug |306451}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Display application menu and title bar side by side for maximized windows ({{bug |102607}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Add support for appmenu-qt ({{bug |266596}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Import Scripted Effect from All Effets Tab ({{bug |296772}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|GHNS support for Scripted Effects ({{bug |296773}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Window Tab support for QML based Aurorae ({{bug |299138}})|kwin-bugs-null@kde.org}}<br /> {{FeatureInProgress|kwin|Remove legacy window decorations ({{bug |299144}}, Review 104281)|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Get rid of &quot;Display borders on maximized windows&quot; setting ({{bug |299245}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Break NETWM to allow inner xinerama struts ({{bug |299247}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Cube animation on border approach should not be used unless the electric borders are actually in use and the config should be disabled, align or hint the electric border configuration ({{bug |299901}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Make ShaderManager act as a real stack ({{bug |300349}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|clientPopup: &quot;'More actions' and &quot;Attach as tab to&quot; lack mnemonics ({{bug |302833}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Make KWin compile with C++11 ({{bug |303313}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Copy all useful Client properties to Deleted ({{bug |303916}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Display content of resizing/moving windows: KDE-Help shows obsolete instructions ({{bug |305297}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Mouse action support for sending window to different activity ({{bug |305758}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Windows list icon does not show up in &quot;Walk Through Desktop List&quot; ({{bug |306187}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Game mode ({{bug |306448}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Animate Window Maximize/Restore ({{bug |308990}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Common animation settings for effects of same type ({{bug |308991}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Use Resize Area in Aurorae ({{bug |308992}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Configurable quick tile area config GUI ({{bug |308993}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Move ExtendedBorderRegion to stable API ({{bug |308994}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Support shortened titles like in bespin in all decorations ({{bug |308995}})|kwin-bugs-null@kde.org}}<br /> {{FeatureInProgress|kwin|Mouse Click effect ({{bug |309006}}, Review 105780)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Decorations not visible ({{bug |305875}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|drag-and-drop between windows by cover switch alt-tab causes apps to crash ({{bug |179077}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Add a rule to select the screen ({{bug |183996}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|JJ: Need Mouse navigation in flip switch mode ({{bug |244439}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Request category for scripted KWin Effects on kde-(look&lt;nowiki&gt;|&lt;/nowiki&gt;app).org ({{bug |297634}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Request category for KWin Scripts on kde-(look&lt;nowiki&gt;|&lt;/nowiki&gt;app).org ({{bug |297635}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Request category for Window Switcher Layouts on kde-(look&lt;nowiki&gt;|&lt;/nowiki&gt;app).org ({{bug |297637}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Allow direct rendering with fglrx ({{bug |301103}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Don't use OpenGL matrix stack in OpenGL 2 backend ({{bug |303093}}, Review 105455)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Refactor Screen/Window PaintData ({{bug |303314}}, Review 105141)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Rapid flickering in locked screen -- makes it difficult to unlock ({{bug |303579}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|double click menu to close needs GUI config ({{bug |305738}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Toplevel::windowType() needs performance improvements ({{bug |306384}}, Review 106349)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|GLPlatform should recommend either OpenGL1 or OpenGL2 compositing ({{bug |306436}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Zoom effect broken in master ({{bug |307609}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|kwin fails to build when the GLES support is disabled ({{bug |307866}})|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|[JJ] Some effect authors are listed as &quot;Name1 &amp; Name2&quot; ({{bug |307928}}, Review 106880)|kwin-bugs-null@kde.org}}<br /> {{FeatureDone|kwin|Add screen management actions to window context menus ({{bug |269207}}, Review 106065)|mgraesslin@kde.org}}<br /> {{FeatureDone|kwin|Move Workspace's compositing functionality to own class Compositor ({{bug |299277}}, Review 102420)|mgraesslin@kde.org}}<br /> {{FeatureDone|kwin|Option to disable close on double click in Aurorae ({{bug |301327}}, Review 106160)|mgraesslin@kde.org}}<br /> {{FeatureDone|kwin|Remove Tiling Support From KWin ({{bug |303090}}, Review 105546)|mgraesslin@kde.org}}<br /> {{FeatureDone|kwin|Allow Scripts to add menus to useractions menu ({{bug |303756}}, Review 106285)|mgraesslin@kde.org}}<br /> {{FeatureDone|kwin|Generic QML support for Aurorae Themes ({{bug |303810}}, Review 105768)|mgraesslin@kde.org}}<br /> {{FeatureDone|kwin|Split out Useractions Menu from Workspace ({{bug |305832}}, Review 106085)|mgraesslin@kde.org}}<br /> <br /> &lt;!-- END GENERATED SECTION --&gt;<br /> {{FeatureInProgress|kwin|Implement color correction (Review 106141)|skeletk13@gmail.com|Casian Andrei}}<br /> {{FeatureInProgress|oxygen decoration|Implement ExtendedBorderRegion support, to resize windows outside of their actual borders|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}<br /> {{FeatureDone|oxygen style|Implement BlurBehind semi-transparent tooltips when available|hugo@oxygen-icons.org|Hugo Pereira Da Costa}}<br /> {{FeatureDone|plasma-wallpapers|Color wallpaper: add listview to display thumbnails for background mode|rshah0385@kireihana.com|Reza Fatahilah Shah}}<br /> {{FeatureInProgress|plasma workspace|Port Notifications applet to QML|mart@kde.org|Marco Martin}}<br /> {{FeatureInProgress|plasma workspace|Port Task Manager applets to QML|hein@kde.org|Eike Hein (Sho_)}}<br /> {{FeatureInProgress|plasma workspace|refresh Air Plasma theme|mart@kde.org|Marco Martin}}<br /> {{FeatureInProgress|plasma workspace|Port Kickoff to qml|yellowcake-@gmx.net|Greg T}}<br /> {{FeatureInProgress|systemsettings|Replace krandr KCM by libkscreen-based one|dvratil@redhat.com|Dan Vrátil}}<br /> {{FeatureInProgress|plasma workspace|Port rssnow to qml|terietor@gmail.com|Giorgos Tsiapaliokas}}<br /> {{FeatureInProgress|various|KActivities/SLC support for most our applications|ivan.cukic@kde.org|Ivan Čukić}}<br /> {{FeatureInProgress|plasma workspace|first desktop SLC applet release|mart@kde.org|Marco Martin}}<br /> {{FeatureDone|System Tray|System tray with interface in QML|dmitry.ashkadov@gmail.com|Dmitry Ashkadov}}<br /> {{FeatureTodo|plasma workspace|Top-rated documents for Task Manager|ivan.cukic@kde.org|Ivan Čukić}}<br /> {{FeatureInProgress|systemsettings|Keyboard layout preview|amourphious1992@gmail.com|Shivam Makkar}}<br /> {{FeatureInProgress|window manager|Rework and optimize vertex specification|fredrik@kde.org|Fredrik Höglund}}<br /> {{FeatureInProgress|window manager|Dynamic shader generation|fredrik@kde.org|Fredrik Höglund}}<br /> {{FeatureInProgress|window manager|Partial port to xcb|fredrik@kde.org|Fredrik Höglund}}<br /> {{FeatureInProgress|window manager|New launch feedback effect|fredrik@kde.org|Fredrik Höglund}}<br /> {{FeatureInProgress|activities|Encrypted activities|ivan.cukic@kde.org|Ivan Čukić}}<br /> {{FeatureInProgress|powerdevil|Improve profile error handling (DPMS)|kde@privat.broulik.de|Kai Uwe Broulik}}<br /> {{FeatureInProgress|plasma workspace|Social Feed|mklapetek@kde.org|Martin Klapetek}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kde-baseapps =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureTodo|FolderView|Split into PopupApplet and Containment|ignat.semenov@blue-systems.com|Ignat Semenov}}<br /> <br /> {{FeatureTodo|FolderView|Port to QML|ignat.semenov@blue-systems.com|Ignat Semenov}}<br /> <br /> {{FeatureTodo|Dolphin|Implement files quick preview feature (named Klook) |evgeniy.augin@osinit.ru|Evgeniy Auzhin}}<br /> <br /> {{FeatureDone|Dolphin|Implement parallel sort algorithm|emmanuelpescosta099@gmail.com|Emmanuel Pescosta}}<br /> <br /> {{FeatureDone|Dolphin|Add GUI option for the &quot;Rename Inline&quot; setting|frank78ac@googlemail.com|Frank Reininghaus}}<br /> <br /> {{FeatureTodo|Dolphin|Add &quot;Icon Size&quot; submenu to the Places Panel context menu|frank78ac@googlemail.com|Frank Reininghaus}}<br /> <br /> {{FeatureDone|print-manager|New Print manager KCM and applet (plasmoid) replacement, using C++ |dantti12@gmail.com|Daniel Nicoletti}}<br /> <br /> {{FeatureDone|Kate|Support for Python plugins|srhaque@theiet.org|Shaheed Haque}}<br /> <br /> {{FeatureDone|Kate|Advanced gid(1) plugin using both ID files and etags|srhaque@theiet.org|Shaheed Haque}}<br /> <br /> {{FeatureTodo|Kate|As-you-type search for the search plugin|kare.sars@iki.fi|Kåre Särs}}<br /> <br /> {{FeatureTodo|Kate|Session name API for plugins + automatic ctags database naming|kare.sars@iki.fi|Kåre Särs}}<br /> <br /> {{FeatureInProgress|Kate|Add optional document &quot;minimap&quot; to the Symbols view plugin|kare.sars@iki.fi|Kåre Särs}}<br /> <br /> {{FeatureInProgress|Kate|Vim Mode Macro support|kdedevel@etothepiplusone.com|Simon St James}}<br /> <br /> {{FeatureTodo|Kdialog|Add support for detailedsorry/detailederror messages|kde@privat.broulik.de|Kai Uwe Broulik}}<br /> <br /> {{FeatureTodo|Konsole|Improve the search filter bar|francesco.cecconi@gmail.com|Francesco Cecconi}}<br /> <br /> {{FeatureTodo|Konsole|Add the --separate cmdline option for running in new process|adaptee@gmail.com|Jekyll Wu}}<br /> <br /> {{FeatureTodo|Konsole|Make the d&amp;d popup menu optional|adaptee@gmail.com|Jekyll Wu}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdeedu =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureTodo|Marble|Have support for &quot;repeatX&quot; in the projection classes|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Satellite Map NG|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Mars &amp; Venus satellite plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}<br /> {{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}<br /> {{FeatureTodo|Marble|Help Menu polishing / Support page inclusion|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Toolbar polishing/refactoring|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureInProgress|Marble|Worldwide hillshading|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Extended library API (no MarbleWidget dependency for tasks like parsing, routing)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Marble Touch on Plasma Active|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureInProgress|Marble|Foursquare plugin|utkuaydin34@gmail.com|Utku Aydın}}<br /> {{FeatureTodo|Marble|Marble Touch on Android (including SOK branch merge)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Support for loading geolocated photos (e.g. in a Gallery activity in Marble Touch)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Layer Management (by the user: Toggle layer visibility; maybe move layers from legend and layers in menus to one central place/tab)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|OSM vector rendering (GSOC branch merge)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Zoom to content of geo file after loading (at least on start-up)|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Marble|Geo files thumbnailer|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Marble|Geo files metadata extractor|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureDone|Rocs|Journal files for projects.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureInProgress|Rocs|Revisit graph export/import functionality to fully support: TGF, DOT, GML, GraphML|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Printing and image export of graphs.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Data Structure Snapshot and Recovery.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureDone|Rocs|Main Window UI Reorganization: Editor Toolbar, dialogs, Information Panel|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Visual Graph Editor Handling: copy&amp;paste, data structure focus, property display|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Visual Graph Editor Edit Menu|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureInProgress|Rocs|Configuration Dialog Optimizations: Code-Editor, Graph Editor|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Data Structure Backend wise iconsets and preconfigurations for types|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureDone|KTouch|Ship ktouch/next|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureTodo|KTouch|Smart resizing of training screen with aligned vertical lines|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureTodo|KTouch|Prominent hint during training if the user makes repeatedly errors|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureDone|KTouch|Show course descriptions in course selector|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureDone|KTouch|Show a message when keyboard layout visualization isn't available due missing data|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureDone|Analitza|New plotting framework|percy.camilo.ta@gmail.com|Percy Camilo Triveño Aucahuasi}}<br /> {{FeatureDone|KAlgebra|Splitted the QML Components from KAlgebraMobile|aleixpol@kde.org|Aleix Pol Gonzalez}}<br /> {{FeatureDone|KAlgebra|New plotting plasmoid graphs, in QtQuick|aleixpol@kde.org|Aleix Pol Gonzalez}}<br /> {{FeatureDone|Pairs|Pairs Theme editor|marco.calignano@gmail.com|Marco Calignano}}<br /> {{FeatureInProgress|Cantor|Python backend|filipe@kde.org|Filipe Saraiva}}<br /> {{FeatureInProgress|Kig|Mark right angles|david.narvaez@computer.org|David E. Narváez}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdegames=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|libkdegames|[http://community.kde.org/KDE_Games/API_cleanup Major cleanup and rewrite] (done, except for the new highscore classes)&lt;br/&gt;&lt;br/&gt;'''Release team:''' please link to the [[Projects/Games/Porting_to_libkdegames_v5|porting instructions]] for third-party developers|stefan.majewsky@googlemail.com|Stefan Majewsky}}<br /> {{FeatureDone|KGoldrunner|Use KGameRenderer and QGraphicsView for all graphics: the gameplay is the same as before.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KGoldrunner|Remove the status bar. All scores and status messages are in the viewport now.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Allow the displayed speed of moves to be adjusted.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Animate multi-stage moves, to make it easier for a human player to follow their progress.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Show multi-stage moves in an order that is easier to follow.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Validate the loading of saved games and report errors.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Rewrite the main AI class and make it use a true Minimax method.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Provide a choice of two AI styles, Kepler and Newton, with the possibility to add more.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Add settings to choose computer player, AI style and skill level for either or both of players 1 and 2.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Add board sizes 3x3 and 4x4, for simplified play.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KSudoku|Add a simple Print facility for KSudoku puzzles.|iandw.au@gmail.com|Ian Wadham}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdegraphics=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|libkipi|[http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/dodonvictor/10002 Porting libkipi to KDE-XML GUI]|dodonvictor@gmail.com|Victor Dodon}}<br /> {{FeatureInProgress|okular|Tiled rendering|okular-devel@kde.org|Okular Developers}}<br /> {{FeatureInProgress|Gwenview|Recursive importer|agateau@kde.org|Aurélien Gâteau}}<br /> {{FeatureInProgress|Gwenview|Color profile support|agateau@kde.org|Aurélien Gâteau}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdemultimedia =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|Juk|[http://community.kde.org/Juk#Porting_plan Port Juk away from kde3support]|martin.sandsmark@kde.org|Martin Sandsmark}}<br /> {{FeatureDone|Juk|Add lyrics view|martin.sandsmark@kde.org|Martin Sandsmark}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdenetwork=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|KGet|Metalink/HTTP Support|dahalaishraj@gmail.com|Aish Raj Dahal}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdepim =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> {{FeatureInProgress|Facebook resource|Include it in default install|martin.klapetek@gmail.com|Martin Klapetek}}<br /> {{FeatureInProgress|Akregator2|Merge in kdepim|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|Knode|Merge in KMail|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|BackupMail|Extend backup to all kdepim apps|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|Sieve|Rewrite dialogbox|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|libs|Move folderview to kdepimlibs/akonadi|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|kolab-resource|Make Kolab 3.0 option available|mollekopf@kolabsys.com|Christian Mollekopf}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdeplasma-addons =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> {{FeatureInProgress|Microblog|replace with QML version|sebas@kde.org|Sebastian Kügler}}<br /> {{FeatureInProgress|StackFolder|Add applet for quick browse the stack of folders|ural.mullabaev@rosalab.ru|Ural Mullabaev}}<br /> {{FeatureInProgress|ComicStrip|Replace with QML version|rshah0385@kireihana.com|Reza Fatahilah Shah}}<br /> {{FeatureInProgress|Calculator|Replace with QML version|luizromario@gmail.com|Luiz Romário Santana Rios}}<br /> {{FeatureDone|QML Wallpapers|Make it possible to have animated wallpapers written in QtQuick technologies.|aleixpol@blue-systems.com|Aleix Pol Gonzalez}}<br /> {{FeatureDone|Dictionary KRunner|Look up words in the dictionary by typing in 'define {word}' in krunner.|Jason@zx2c4.com|Jason A. Donenfeld}}<br /> {{FeatureInProgress|Calculator|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> {{FeatureInProgress|Eyes|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> {{FeatureInProgress|FifteenPuzzle|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> {{FeatureInProgress|Luna|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> {{FeatureInProgress|Timer|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdesdk =<br /> <br /> {| cellspa/cing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> {{FeatureTodo|Okteta|Add a general KPart adapter to Kasten, than finish port of Okteta KPart to Okteta Kasten|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Add global toggle option for the offset display, hex or decimal|kossebau@kde.org|Friedrich W. H. Kossebau}} <br /> {{FeatureTodo|Okteta|Add Kate-like combined dialogs to query for actions on files|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Add Okular like embedded notifications|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add support for import by drop, both url and data|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add support for memory mapping of files and 64-bit addressing|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add support for jobs like io, printing, string search or filter|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|copy again puts also a value or char variant of the data to clipboard|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Improve the titels of the changes to the bytearray to be more descriptive, best using ids to avoid text string|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Make all user interaction in the KastenCore managers plugin-based|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Merge row and column widgets into one|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Store bookmarks|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Store bookmarks and other view settings for next load|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Add custom datatypes to structures tool|alex.richardson@gmx.de|Alex Richardson}}<br /> {{FeatureInProgress|Okteta|Add tagged unions to structures tool|alex.richardson@gmx.de|Alex Richardson}}<br /> {{FeatureInProgress|Okteta|Add array indices to structures tool|alex.richardson@gmx.de|Alex Richardson}}<br /> {{FeatureDone|Umbrello|Line based diagram grid |ralf.habacker@freenet.de|Ralf Habacker}}<br /> {{FeatureTodo|Umbrello| widget resize and diagram auto resize feature |ralf.habacker@freenet.de|Ralf Habacker}}<br /> {{FeatureTodo|Umbrello|add spline based association lines to avoid autolayout widget/line overlapping (needs volunteers)|ralf.habacker@freenet.de|Ralf Habacker}}<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> = kdeutils=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|Ark|Make it possible to disable internal previewer|kde@privat.broulik.de|Kai Uwe Broulik}}<br /> |}<br /> &lt;br&gt;</div>

Sebastian http://techbase.kde.org/Schedules/KDE4/4.10_Feature_Plan 2012-10-24T16:19:11Z

<p>Sebastian: update KTouch section</p> <hr /> <div>This is a list of planned features for the SC 4.10 release. <br /> <br /> See also: <br /> <br /> *[[Schedules/KDE4/4.10 Release Schedule]] <br /> *[[Schedules/KDE4/4.9 Feature Plan]] (previous major release)<br /> <br /> &lt;br&gt; Legend: <br /> <br /> *todo =&amp;gt; not started yet <br /> *in-progress =&amp;gt; started, but not completed yet <br /> *done =&amp;gt; completed<br /> <br /> __TOC__ <br /> <br /> &lt;br&gt;<br /> <br /> = kdelibs =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> |}<br /> &lt;b&gt;NO NEW FEATURES ALLOWED&lt;/b&gt;<br /> &lt;br&gt;<br /> <br /> = kde-runtime =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|kio-mtp|KIO-Slave for MTP|philschmidt@gmx.net|Philipp Schmidt}}<br /> {{FeatureInProgress|QML Containments|Making it possible to do full-featured containments in QML|sebas@kde.org|Sebastian Kügler}}<br /> {{FeatureInProgress|nepomuk-indexer|New Nepomuk Indexer|me@vhanda.in|Vishesh Handa}}<br /> {{FeatureInProgress|nepomukbakcup|Nepomuk Backup rewritten from scratch|me@vhanda.in|Vishesh Handa}}<br /> {{FeatureInProgress|nepomukcleaner|An application to port/clean invalid/legacy data in Nepomuk|me@vhanda.in|Vishesh Handa}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kde-workspace =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|ksmserver|Merge the new qml based screen locker|mart@kde.org|Marco Martin}}<br /> <br /> &lt;!-- The following section of entries has been auto generated by ChangelogGenerator. Do not edit!<br /> BEGIN GENERATED SECTION --&gt;<br /> {{FeatureTodo|kwin|windows that are moved to another desktop should be treated as sticky windows ({{bug |213847}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Fix fullscreen state handling: NETWM says it's bound to focus and not stacking order, also see bug #224600 ({{bug |296076}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Lanczos Filter broken after screen size changes ({{bug |296065}})|kwin-bugs-null@kde.org}}<br /> {{FeatureInProgress|kwin|GHNS support for KWin Scripts ({{bug |296774}}, Review 104877)|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|KConf Update Script for KWin 4.9 ({{bug |296775}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Request category for scripted KWin Effects on kde-(look&lt;nowiki&gt;|&lt;/nowiki&gt;app).org ({{bug |297634}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Request category for KWin Scripts on kde-(look&lt;nowiki&gt;|&lt;/nowiki&gt;app).org ({{bug |297635}})|kwin-bugs-null@kde.org}}<br /> {{FeatureInProgress|kwin|GHNS support for Window Switching Layouts ({{bug |297636}}, Review 104894)|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Request category for Window Switcher Layouts on kde-(look&lt;nowiki&gt;|&lt;/nowiki&gt;app).org ({{bug |297637}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Update Documentation for Window Switcher Layouts ({{bug |297638}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|ThumbnailItem allows upscaling of Windows ({{bug |297864}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Window Tab support for QML based Aurorae ({{bug |299138}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Increase ABI version for KDecorations ({{bug |299140}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Break NETWM to allow inner xinerama struts ({{bug |299247}})|kwin-bugs-null@kde.org}}<br /> <br /> &lt;!-- END GENERATED SECTION --&gt;<br /> {{FeatureDone|plasma-wallpapers|Color wallpaper: add listview to display thumbnails for background mode|rshah0385@kireihana.com|Reza Fatahilah Shah}}<br /> {{FeatureInProgress|plasma workspace|Port Notifications applet to QML|mart@kde.org|Marco Martin}}<br /> {{FeatureInProgress|plasma workspace|Port Task Manager applets to QML|hein@kde.org|Eike Hein (Sho_)}}<br /> {{FeatureInProgress|plasma workspace|refresh Air Plasma theme|mart@kde.org|Marco Martin}}<br /> {{FeatureInProgress|plasma workspace|Port Kickoff to qml|yellowcake-@gmx.net|Greg T}}<br /> {{FeatureInProgress|systemsettings|Replace krandr KCM by libkscreen-based one|dvratil@redhat.com|Dan Vrátil}}<br /> {{FeatureInProgress|plasma workspace|Port rssnow to qml|terietor@gmail.com|Giorgos Tsiapaliokas}}<br /> {{FeatureInProgress|various|KActivities/SLC support for most our applications|ivan.cukic@kde.org|Ivan Čukić}}<br /> {{FeatureInProgress|plasma workspace|first desktop SLC applet release|mart@kde.org|Marco Martin}}<br /> {{FeatureDone|System Tray|System tray with interface in QML|dmitry.ashkadov@gmail.com|Dmitry Ashkadov}}<br /> {{FeatureTodo|plasma workspace|Top-rated documents for Task Manager|ivan.cukic@kde.org|Ivan Čukić}}<br /> {{FeatureInProgress|systemsettings|Keyboard layout preview|amourphious1992@gmail.com|Shivam Makkar}}<br /> {{FeatureInProgress|window manager|Rework and optimize vertex specification|fredrik@kde.org|Fredrik Höglund}}<br /> {{FeatureInProgress|window manager|Dynamic shader generation|fredrik@kde.org|Fredrik Höglund}}<br /> {{FeatureInProgress|window manager|Partial port to xcb|fredrik@kde.org|Fredrik Höglund}}<br /> {{FeatureInProgress|window manager|New launch feedback effect|fredrik@kde.org|Fredrik Höglund}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kde-baseapps =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureTodo|FolderView|Split into PopupApplet and Containment|ignat.semenov@blue-systems.com|Ignat Semenov}}<br /> <br /> {{FeatureTodo|FolderView|Port to QML|ignat.semenov@blue-systems.com|Ignat Semenov}}<br /> <br /> {{FeatureTodo|Dolphin|Implement files quick preview feature (named Klook) |evgeniy.augin@osinit.ru|Evgeniy Auzhin}}<br /> <br /> {{FeatureDone|print-manager|New Print manager KCM and applet (plasmoid) replacement, using C++ |dantti12@gmail.com|Daniel Nicoletti}}<br /> <br /> {{FeatureDone|Kate|Support for Python plugins|srhaque@theiet.org|Shaheed Haque}}<br /> <br /> {{FeatureDone|Kate|Advanced gid(1) plugin using both ID files and etags|srhaque@theiet.org|Shaheed Haque}}<br /> <br /> {{FeatureTodo|Kate|As-you-type search for the search plugin|kare.sars@iki.fi|Kåre Särs}}<br /> <br /> {{FeatureTodo|Kate|Session name API for plugins + automatic ctags database naming|kare.sars@iki.fi|Kåre Särs}}<br /> <br /> {{FeatureInProgress|Kate|Add optional document &quot;minimap&quot; to the Symbols view plugin|kare.sars@iki.fi|Kåre Särs}}<br /> <br /> {{FeatureInProgress|Kate|Macro support|kdedevel@etothepiplusone.com|Simon St James}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdeedu =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureTodo|Marble|Have support for &quot;repeatX&quot; in the projection classes|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Satellite Map NG|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Mars &amp; Venus satellite plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}<br /> {{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}<br /> {{FeatureTodo|Marble|Help Menu polishing / Support page inclusion|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Toolbar polishing/refactoring|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureInProgress|Marble|Worldwide hillshading|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Extended library API (no MarbleWidget dependency for tasks like parsing, routing)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Marble Touch on Plasma Active|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureInProgress|Marble|Foursquare plugin|utkuaydin34@gmail.com|Utku Aydın}}<br /> {{FeatureTodo|Marble|Marble Touch on Android|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Support for loading geolocated photos (e.g. in a Gallery activity in Marble Touch)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Layer Management (by the user: Toggle layer visibility; maybe move layers from legend and layers in menus to one central place/tab)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Rocs|Journal files for projects.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureInProgress|Rocs|Revisit graph export/import functionality to fully support: TGF, DOT, GML, GraphML|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Printing and image export of graphs.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Data Structure Snapshot and Recovery.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureInProgress|Rocs|Main Window UI Reorganization|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Visual Graph Editor Handling: copy&amp;paste, data structure focus, property display|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Visual Graph Editor Edit Menu|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Code Editor Configuration Dialog|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Data Structure Backend wise iconsets and preconfigurations for types|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureDone|KTouch|Ship ktouch/next|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureTodo|KTouch|Smart resizing of training screen with aligned vertical lines|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureTodo|KTouch|Prominent hint during training if the user makes repeatedly errors|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureTodo|KTouch|Show course descriptions in course selector|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureTodo|KTouch|Show a message when keyboard layout visualizion isn't available due missing data|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> {{FeatureDone|Analitza|New plotting framework|percy.camilo.ta@gmail.com|Percy Camilo Triveño Aucahuasi}}<br /> {{FeatureDone|KAlgebra|Splitted the QML Components from KAlgebraMobile|aleixpol@kde.org|Aleix Pol Gonzalez}}<br /> {{FeatureDone|KAlgebra|New plotting plasmoid graphs, in QtQuick|aleixpol@kde.org|Aleix Pol Gonzalez}}<br /> {{FeatureInProgress|Pairs|Pairs Theme editor|marco.calignano@gmail.com|Marco Calignano}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdegames=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|libkdegames|[http://community.kde.org/KDE_Games/API_cleanup Major cleanup and rewrite] (done, except for the new highscore classes)&lt;br/&gt;&lt;br/&gt;'''Release team:''' please link to the [[Projects/Games/Porting_to_libkdegames_v5|porting instructions]] for third-party developers|stefan.majewsky@googlemail.com|Stefan Majewsky}}<br /> {{FeatureDone|KGoldrunner|Use KGameRenderer and QGraphicsView for all graphics: the gameplay is the same as before.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KGoldrunner|Remove the status bar. All scores and status messages are in the viewport now.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Allow the displayed speed of moves to be adjusted.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Animate multi-stage moves, to make it easier for a human player to follow their progress.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Show multi-stage moves in an order that is easier to follow.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Validate the loading of saved games and report errors.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Rewrite the main AI class and make it use a true Minimax method.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Provide a choice of two AI styles, Kepler and Newton, with the possibility to add more.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Add settings to choose computer player, AI style and skill level for either or both of players 1 and 2.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureDone|KJumpingCube|Add board sizes 3x3 and 4x4, for simplified play.|iandw.au@gmail.com|Ian Wadham}}<br /> {{FeatureInProgress|KSudoku|Add a simple Print facility for KSudoku puzzles.|iandw.au@gmail.com|Ian Wadham}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdegraphics=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|libkipi|[http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/dodonvictor/10002 Porting libkipi to KDE-XML GUI]|dodonvictor@gmail.com|Victor Dodon}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdemultimedia =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|Juk|[http://community.kde.org/Juk#Porting_plan Port Juk away from kde3support]|martin.sandsmark@kde.org|Martin Sandsmark}}<br /> {{FeatureDone|Juk|Add lyrics view|martin.sandsmark@kde.org|Martin Sandsmark}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdenetwork=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdepim =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> {{FeatureInProgress|Facebook resource|Include it in default install|martin.klapetek@gmail.com|Martin Klapetek}}<br /> {{FeatureInProgress|Akregator2|Merge in kdepim|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|Knode|Merge in KMail|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|BackupMail|Extend backup to all kdepim apps|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|Sieve|Rewrite dialogbox|montel@kde.org|Montel Laurent}}<br /> {{FeatureInProgress|libs|Move folderview to kdepimlibs/akonadi|montel@kde.org|Montel Laurent}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdeplasma-addons =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> {{FeatureInProgress|Microblog|replace with QML version|sebas@kde.org|Sebastian Kügler}}<br /> {{FeatureInProgress|StackFolder|Add applet for quick browse the stack of folders|ural.mullabaev@rosalab.ru|Ural Mullabaev}}<br /> {{FeatureInProgress|ComicStrip|Replace with QML version|rshah0385@kireihana.com|Reza Fatahilah Shah}}<br /> {{FeatureInProgress|Calculator|Replace with QML version|luizromario@gmail.com|Luiz Romário Santana Rios}}<br /> {{FeatureDone|QML Wallpapers|Make it possible to have animated wallpapers written in QtQuick technologies.|aleixpol@blue-systems.com|Aleix Pol Gonzalez}}<br /> {{FeatureDone|Dictionary KRunner|Look up words in the dictionary by typing in 'define {word}' in krunner.|Jason@zx2c4.com|Jason A. Donenfeld}}<br /> {{FeatureInProgress|Calculator|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> {{FeatureInProgress|Eyes|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> {{FeatureInProgress|FifteenPuzzle|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> {{FeatureInProgress|Luna|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> {{FeatureInProgress|Timer|replace with QML version|bettio@kde.org|Davide Bettio}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdesdk =<br /> <br /> {| cellspa/cing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> {{FeatureTodo|Okteta|Add a general KPart adapter to Kasten, than finish port of Okteta KPart to Okteta Kasten|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Add global toggle option for the offset display, hex or decimal|kossebau@kde.org|Friedrich W. H. Kossebau}} <br /> {{FeatureTodo|Okteta|Add Kate-like combined dialogs to query for actions on files|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Add Okular like embedded notifications|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add support for import by drop, both url and data|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add support for memory mapping of files and 64-bit addressing|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add support for jobs like io, printing, string search or filter|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|copy again puts also a value or char variant of the data to clipboard|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Improve the titels of the changes to the bytearray to be more descriptive, best using ids to avoid text string|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Make all user interaction in the KastenCore managers plugin-based|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Merge row and column widgets into one|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Store bookmarks|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Store bookmarks and other view settings for next load|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Add custom datatypes to structures tool|alex.richardson@gmx.de|Alex Richardson}}<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> = kdeutils=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> |}<br /> &lt;br&gt;</div>

Sebastian http://techbase.kde.org/Schedules/KDE4/4.10_Feature_Plan 2012-10-07T10:31:49Z

<p>Sebastian: </p> <hr /> <div>This is a list of planned features for the SC 4.10 release. <br /> <br /> See also: <br /> <br /> *[[Schedules/KDE4/4.10 Release Schedule]] <br /> *[[Schedules/KDE4/4.9 Feature Plan]] (previous major release)<br /> <br /> &lt;br&gt; Legend: <br /> <br /> *todo =&amp;gt; not started yet <br /> *in-progress =&amp;gt; started, but not completed yet <br /> *done =&amp;gt; completed<br /> <br /> __TOC__ <br /> <br /> &lt;br&gt;<br /> <br /> = kdelibs =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> |}<br /> &lt;b&gt;NO NEW FEATURES ALLOWED&lt;/b&gt;<br /> &lt;br&gt;<br /> <br /> = kde-runtime =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|kio-mtp|KIO-Slave for MTP|philschmidt@gmx.net|Philipp Schmidt}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kde-workspace =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|ksmserver|Merge the new qml based screen locker|mart@kde.org|Marco Martin}}<br /> <br /> &lt;!-- The following section of entries has been auto generated by ChangelogGenerator. Do not edit!<br /> BEGIN GENERATED SECTION --&gt;<br /> {{FeatureTodo|kwin|windows that are moved to another desktop should be treated as sticky windows ({{bug |213847}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Fix fullscreen state handling: NETWM says it's bound to focus and not stacking order, also see bug #224600 ({{bug |296076}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Lanczos Filter broken after screen size changes ({{bug |296065}})|kwin-bugs-null@kde.org}}<br /> {{FeatureInProgress|kwin|GHNS support for KWin Scripts ({{bug |296774}}, Review 104877)|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|KConf Update Script for KWin 4.9 ({{bug |296775}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Request category for scripted KWin Effects on kde-(look&lt;nowiki&gt;|&lt;/nowiki&gt;app).org ({{bug |297634}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Request category for KWin Scripts on kde-(look&lt;nowiki&gt;|&lt;/nowiki&gt;app).org ({{bug |297635}})|kwin-bugs-null@kde.org}}<br /> {{FeatureInProgress|kwin|GHNS support for Window Switching Layouts ({{bug |297636}}, Review 104894)|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Request category for Window Switcher Layouts on kde-(look&lt;nowiki&gt;|&lt;/nowiki&gt;app).org ({{bug |297637}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Update Documentation for Window Switcher Layouts ({{bug |297638}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|ThumbnailItem allows upscaling of Windows ({{bug |297864}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Window Tab support for QML based Aurorae ({{bug |299138}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Increase ABI version for KDecorations ({{bug |299140}})|kwin-bugs-null@kde.org}}<br /> {{FeatureTodo|kwin|Break NETWM to allow inner xinerama struts ({{bug |299247}})|kwin-bugs-null@kde.org}}<br /> <br /> &lt;!-- END GENERATED SECTION --&gt;<br /> {{FeatureDone|plasma-wallpapers|Color wallpaper: add listview to display thumbnails for background mode|rshah0385@kireihana.com|Reza Fatahilah Shah}}<br /> {{FeatureInProgress|plasma workspace|Port Notifications applet to QML|mart@kde.org|Marco Martin}}<br /> {{FeatureInProgress|plasma workspace|Port Task Manager applets to QML|hein@kde.org|Eike Hein (Sho_)}}<br /> {{FeatureInProgress|plasma workspace|refresh Air Plasma theme|mart@kde.org|Marco Martin}}<br /> {{FeatureInProgress|systemsettings|Replace krandr KCM by libkscreen-based one|dvratil@redhat.com|Dan Vrátil}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kde-baseapps =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureTodo|FolderView|Refactor into PopupApplet and Containment|ignat.semenov@blue-systems.com|Ignat Semenov}}<br /> <br /> {{FeatureTodo|Dolphin|Implement files quick preview feature (named Klook) |evgeniy.augin@osinit.ru|Evgeniy Auzhin}}<br /> <br /> {{FeatureDone|print-manager|New Print manager KCM and applet (plasmoid) replacement, using C++ |dantti12@gmail.com|Daniel Nicoletti}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdeedu =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureTodo|Marble|Have support for &quot;repeatX&quot; in the projection classes|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Satellite Map NG|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Mars &amp; Venus satellite plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}<br /> {{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn / Gerhard Holtkamp}}<br /> {{FeatureTodo|Marble|Help Menu polishing / Support page inclusion|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Toolbar polishing/refactoring|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureTodo|Marble|Solar Eclipse Plugin|rahn@kde.org|Torsten Rahn}}<br /> {{FeatureInProgress|Marble|Worldwide hillshading|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Extended library API (no MarbleWidget dependency for tasks like parsing, routing)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Marble Touch on Plasma Active|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Marble Touch on Android|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Support for loading geolocated photos (e.g. in a Gallery activity in Marble Touch)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Marble|Layer Management (by the user: Toggle layer visibility; maybe move layers from legend and layers in menus to one central place/tab)|earthwings@gentoo.org|Dennis Nienhüser}}<br /> {{FeatureTodo|Rocs|Journal files for projects.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureInProgress|Rocs|Revisit graph export/import functionality to fully support: TGF, DOT, GML, GraphML|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureTodo|Rocs|Printing and image export of graphs.|cola@uni-paderborn.de|Andreas Cord-Landwehr}}<br /> {{FeatureInProgress|KTouch|Ship ktouch/next|sebastiangottfried@web.de|Sebastian Gottfried}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdegames=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|libkdegames|[http://community.kde.org/KDE_Games/API_cleanup Major cleanup and rewrite] (done, except for the new highscore classes)&lt;br/&gt;&lt;br/&gt;'''Release team:''' please link to the [[Projects/Games/Porting_to_libkdegames_v5|porting instructions]] for third-party developers|stefan.majewsky@googlemail.com|Stefan Majewsky}}<br /> <br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdegraphics=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|libkipi|[http://www.google-melange.com/gsoc/proposal/review/google/gsoc2012/dodonvictor/10002 Porting libkipi to KDE-XML GUI]|dodonvictor@gmail.com|Victor Dodon}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdemultimedia =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> {{FeatureInProgress|Juk|[http://community.kde.org/Juk#Porting_plan Port Juk away from kde3support]|martin.sandsmark@kde.org|Martin Sandsmark}}<br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdenetwork=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> |}<br /> &lt;br&gt;<br /> <br /> = kdepim =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> {{FeatureInProgress|Facebook resource|Include it in default install|martin.klapetek@gmail.com|Martin Klapetek}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdeplasma-addons =<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> {{FeatureInProgress|Microblog|replace with QML version|sebas@kde.org|Sebastian Kügler}}<br /> {{FeatureInProgress|StackFolder|Add applet for quick browse the stack of folders|ural.mullabaev@rosalab.ru|Ural Mullabaev}}<br /> {{FeatureInProgress|ComicStrip|Replace with QML version|rshah0385@kireihana.com|Reza Fatahilah Shah}}<br /> |}<br /> &lt;br&gt;<br /> <br /> = kdesdk =<br /> <br /> {| cellspa/cing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> {{FeatureTodo|Okteta|Add a general KPart adapter to Kasten, than finish port of Okteta KPart to Okteta Kasten|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Add global toggle option for the offset display, hex or decimal|kossebau@kde.org|Friedrich W. H. Kossebau}} <br /> {{FeatureTodo|Okteta|Add Kate-like combined dialogs to query for actions on files|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add Kate-like search tool|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Add Okular like embedded notifications|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add support for import by drop, both url and data|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add support for memory mapping of files and 64-bit addressing|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|add support for jobs like io, printing, string search or filter|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|copy again puts also a value or char variant of the data to clipboard|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Improve the titels of the changes to the bytearray to be more descriptive, best using ids to avoid text string|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Make all user interaction in the KastenCore managers plugin-based|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Merge row and column widgets into one|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Store bookmarks|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Store bookmarks and other view settings for next load|kossebau@kde.org|Friedrich W. H. Kossebau}}<br /> {{FeatureTodo|Okteta|Add custom datatypes to structures tool|alex.richardson@gmx.de|Alex Richardson}}<br /> |}<br /> <br /> &lt;br&gt;<br /> <br /> = kdeutils=<br /> <br /> {| cellspacing=&quot;0&quot; cellpadding=&quot;5&quot; border=&quot;1&quot; style=&quot;border: 1px solid gray; border-collapse: collapse; text-align: left; width: 100%;&quot; class=&quot;sortable&quot;<br /> |- style=&quot;background: rgb(236, 236, 236) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous; white-space: nowrap;&quot;<br /> <br /> ! Status <br /> ! Project <br /> ! Description <br /> ! Contact <br /> <br /> |}<br /> &lt;br&gt;</div>

Sebastian