KDEEdu/Artikulate/Todo: Difference between revisions

From KDE Community Wiki
(→‎Tasks for Release 0.4: next release is 0.3)
Line 6: Line 6:
* https://bugs.kde.org/show_bug.cgi?id=328418 - missing reload after imported course
* https://bugs.kde.org/show_bug.cgi?id=328418 - missing reload after imported course
=== Release Goals ===
=== Release Goals ===
* count required learner recordings for statistics, instead of clicks on "Retry Later"
* revisit interaction design
* revisit interaction design
** training interactions
** training interactions

Revision as of 11:13, 10 January 2014

Bugs

Tasks for Release 0.3

Blockers

Release Goals

  • count required learner recordings for statistics, instead of clicks on "Retry Later"
  • revisit interaction design
    • training interactions
    • overview screen (previously called start/home screen)
  • use learner profiles
    • profile based "last learned language"
    • save statistics
  • switch to QtGStreamer as main recording backend
    • optionally already allow sound recording with Simon
  • provide at least two language courses
  • complete user documentation
  • use 5-boxes learning approach
  • system wide course installation (aka class mode)
  • testing color schemes
  • port to kqmlgraphplugin
  • minor UI todos
    • training page
      • add scrollbars for long texts (not fitting into bubble)
      • use font settings from configuration dialog
      • use background for progress bar phrase information
    • overview page
      • give info if no course/units are available in language
  • handle corrupt course XML files gracefully in editor

Unspecified Target ToDos

General User Interface

Course Editor

  • broken layout for phrases with several text lines
  • when scrolled down, cannot open phrase for edit
  • enable the user to add new course skeletons
  • kvtml file export

Trainer

  • soundwave diagrams / visual comparison

Core

  • set input volume (change at config dialog has no effect currently)
  • port XML parsing to Xmlstream

Release Steps

  1. write release notes
  2. create tarballs and upload them
  3. notify sysadmins
  4. add links to community wiki page
  5. write notification mail