Here it will be shown the most important pending things that appear in the "to do" list of the project. Some of them will be eventually made, and some may never make his way in the features list, as this is just a desirable features list and maybe some of them aren't technically feasible.
GHNS integration: a user should be able to download new scripted tutorials for the applications easily, like it is done with themes, wallpapers... Freedesktop.org Get Hot New Stuff infrastructure and its KDE implementation would be used for this.
Extended information in step text: in a normal application, widgets have some extended information like tooltips and "What's this" help. Dialogs can be linked with a specific section of an application manual. Things like those should can be done also in tutorials, so the user can get more information about some subject.
Eye candy!: current KTutorial implementation just uses a floating widget with a thin frame, but nothing else. Maybe some changes could be done in that area to make it more appealing to the user. KDE 4 is sexy, KTutorial should be too.
However, this is not prioritary at all, but it will likely be easily done as view and model aren't very coupled.
Keep a stable ABI: this feature will have some sense if KTutorial ends having some kind of user base (and it will likely be a requirement to enter in KDELibs, provided it could someday happen ;) ). But a lot of things must happen first, so it has a veeery low priority in the list ;)
Add a "fluent" API: a fluent interface would ease the writing of tutorials, making them more "natural", nearer to a spoken language than a programming language.