Edit "Oms To Do"
UserPreferences
MoinMoin Wiki
LividWiki
RecentChanges
TitleIndex
WordIndex
Help
Reduce editor size
|
HelpOnFormatting
This is the list of things that '''will''' be implemented in OpenMediaSystem. Contents: [[TableOfContents]] = Milestones = == oms 0.1.5 Release == * stable codebase (everybody please help) * clean up code and directories * work out basic development rules * sane audio/video sync * dynamic plugin configuration via XML * binary packages (RPM and Debian) == oms 0.2.0 Release == * Extras * dvd menus * fast forward/rewind playback * time elapsed display * Video Output * Fullscreen Playback * stable libvo API for oms * binary packages (RPM and Debian) * sane oms GUI * as few liboms calls as possible = Test Suites = Tests, tests, and more tests. It would be good to have an automated test suite. Would make it much easier to verify changes don't break things. "Write the tests first, then code till they work" philosophy. * [http://www.extremeprogramming.org/] * [http://www.refactoring.org/] * wiki:Wiki/ExtremeProgrammingRoadmap For instance... checkin some '''known''' to be valid simple streams and write tests to parse/decode them and verify the results. The buffer code can have single, multi-thread tests. What is a good way to automatically test for mem leaks? Using mtrace now (can be found on recent glibc distributions) <dent@linuxvideo.org>
config = 0.000 total = 0.390 imports = 0.370