(53 items)
----------

 #   -  det er noe galt meg config. Noen ganger bygges ikke soundcard.so
        med awe_set funksjoner. Kjør distclean på exported source før jeg
        lager tarball. Dobbeltsjekk tarball, og bygg resten fra den.
 #   -  LC=no_NO messes up the piano widget
 #   -  for at ifeq i Makefiler skal fungere, må Variables.make inkluderes
        for ifeq. Pass samtidig på det med at det er targets i
        python-targets.make.
[-]  -  harmonic-intervall
     #   -  hvis man har slik at man kan velge nytt spørsmål, og velger
            nytt spørsmål uten å ha svaret på det gamle, så blir spørsmålet
            man ikke svarte på ikke registrert i statistikken. Dvs at man
            kan velge nytt spørsmål hvis det kommer noe man ikke kan, og
            dermed jukse.
[-]  -  Packaging
    [-]  -  Debian
         #   -  When 1.0 is released and I start 1.1.x, files should be
                installed into /usr/share/solfege1.1/ and
                /usr/lib/solfege1.1/ so we can have both the stable and
                unstable release installed.
         #   -  Apps/Educational menu policy??
         #   -  debian-menu: Education/Music
         #   -  should probably depend on python, not python-base
         #   -  To get correct built package with diff file, in the dir
                where I unpacked the released tarball, I copy
                solfege-x.y.z.tar.gz to solfege_x.y.z.orig.tar.gz
                
                This way, I can make solfege_x.y.z-2 release with only
                .diff upload, no new tar.gz source
     #   -  Rpm: packages built on clean RH 6.2 and 7.0, mandrake etc...
            Someone with just a little clue can do this. Just make sure you
            have a clean system, and do "make rpm"
[-]  -  misc TODO
    [-]  -  mpd
         #   -  We need to define ALL exceptions that can be raised from
                the parser and from the mpd module, so we know how to
                handle errors in music.
         #   -  The mpd displayer will be a little confused and generate
                bad looking flags for 1/8-notes if the Question.m_clue_end
                variable points to a timepos in the middle of a beam.
         #   -  better TieEngraver. This will require some reorganisation,
                where we have one engraver that takes care of all ties
                between two chords.
        [-]  -  Better error messages:
             #   -  [g'8 g],
             #   -  \stemdown instead of \stemDown should say 'unknown
                    keyword' or something instead of Parse error: \
         #   -  get real number-pixmaps from Lilypond. The numbers I use
                for time signatures now are handcrafted
         #   -   "|." bar, maybe also "||"
        [-]  -  Low priority
             #   -  Tuples
    [-]  -  lessonfiles
         #   -  lessonfiles: at least for id-by-name: the file should be
                able to refer to midifiles to be played instead of music
                entered in the actual file. This would be nice if I ever
                connect to an external midi synth to create questions.
         #   -  the include command will break the linenumber in
                errormessages.
    [-]  -  other stuff
         #   -  let harmonic|melodic intervall ask the inputwidget how big
                intervalls it can handle. Only button-input is limited to a
                decim.
         #   -  write a replacement for nNotenameRange that is a non-gui
                class controlling two spin buttons. One other idea is to
                create some fancy widget with GnomeCanvas that work without
                spinbuttons.
         #   -  some classes, like MultipleIntervallConfigWidget is *very*
                ugly.
         #   -  Check error code when trying to use an external midi
                playing program.
         #   -  The LessonfileManager parses all lesson files at startup.
                This is no real problem now, but with increasing number of
                lesson files, this has to be fixed.
         #   -  --help should also list solfege's command line options, not
                only the gtk/gnome options.
[-]  -  Bugs
     #   -  Find out if the redraw problem in GuitarWidget is a gnomecanvas
            bug, or just me not understanding how to use it.
[-]  -  Tasks without programming skills
     #   -  Banner ads: gnucash uses 125x125 and 470x62 pixels
     #   -  Solfege need an icon to use when starting the program from
            menus or from the gnome panel
     #   -  create more lessonfiles
     #   -  write articles about eartraining and music theory to be
            included in Solfege
     #   -  translate the program. Just ask for help on solfege-devel if
            don't know how to do that
[-]  -  Stuff to remember
     #   -  When making polygons on GnomeCanvas, the points has to be
            entered anticlockwise.
     #   -  de_DE is language_COUNTRY
[-]  -  Thoughts about new exercises
     #   -  Solfege display some notes and play the music. The user should
            tell where solfege don't play the same as the notes.
     #   -  Train perception of modulations: Solfege play a simple
            progression with random modulations to new keys. The user sing
            the same pattern in the different keys. tca: this is similar to
            one exercise Marit uses when warming up her choir.
[-]  -  TODO and plans for 1.1.x
     #   -  Make a complete separation between gui and data, so we can have
            several frontends. Most likely I will make a simple frontent
            only supporting the exercises that don't need music displayer,
            probably a command line frontent, or maybe a curses frontend.
     #   -  make a widget that can be used both as a music displayer and to
            display text. Maybe just as simple as a box that contain both a
            html widget and a music displayer. This way we can use the
            music displayer in exercises like chord to show some important
            info instead of adding a flash bar that will be used very
            seldom and eat lots of gui space
     #   -  Python 2.0, gtk 2.0, pygtk 0.7.0? Lets hope the licensing
            problems with python 2.0 is solved.

---=== end  ===---