<Untitled> (54 items)
----------

 #   -  do s/solfege0.7/solfege1.0/ before the stable release.
 #   -  send bug til bug-texinfo@gnu.org om at vi ikke kan ha en @email i
        en @subsection, men at@code fungerer
[-]  -  Most important TODOs
     #   -  I need someone to fix (or give me a hint on how to fix) the
            sound card code so the percussion channel works also for
            /dev/sequencer for other sound cards than Soundblaster AWE.
            /dev/music (aka /dev/sequencer2) works fine but /dev/sequencer
            is more tricky. SB AWE works by by calling
            AWE_SET_CHANNEL_MODE(devnum, AWE_PLAY_MULTI), but I don't know
            to do this for other soundcards, and don't have the hardware to
            experiment.
 #   -  If no new problems are reported, only lesson files, documentation
        and translations (and the /dev/sequencer percussion fix) will be
        added before the 1.0 release.
 #   -  er det mulig  f opp en messagebox hvis vi har angitt en
        midiplayer som ikke finnes?
 #   -  jeg distribuerer .mo filer. Skal dette gjres?
[-]  -  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.
                
                When 1.2 is released we release that as package solfege,
                with
                Replaces: solfege1.1
                Conlicts: solfege1.1
                (Ask on debian-mentors to check that this is correct
                procedure)
         #   -  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.
    [-]  -  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. This replacement can the be used in
                ConfigWindow to make sure the two spinbuttons telling the
                lowest and highest tone the user can sing are sane.
         #   -  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.
[-]  -  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
            you don't know what to do.
[-]  -  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
     #   -  identify-scale is configured on the practise page, this is not
            consistent with the rest of the program.
     #   -  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 <Untitled> ===---
