view TODO @ 337:75e3fb8d706d

Improved bootstrap script
author Matti Hamalainen <ccr@tnsp.org>
date Thu, 22 Sep 2005 02:21:03 +0000
parents 171b428ee806
children 7b6ec6ee418d
line wrap: on
line source

XMMS-SID - SIDPlay input plugin for X MultiMedia System (XMMS)
==============================================================

For XMMS-SID v0.8
-----------------
RC1:
- explain --disable-themetune in README
- fix NEWS

- XS_STIL_MAXENTRY and related problems. remove
  hardcoded limit. best would be to unify STIL/SLDB/
  t_xs_tuneinfo since xs_tuneinfo is dynamic. this
  would also imply towards usefulness of XSIDB
  (see below)

  possibly just increase XS_STIL_MAXENTRY to
  work around problems for now. rewriting the STIL/SLDB
  junk would mean too much work for 0.8.

- Subtune INFO selector does not have text when the
  fileinfo window is first opened, why?
- Tabify filter configuration and add separate tabs
  for SIDPlay1 and 2 filter configs (Also separate reset
  buttons for each)
- Fix remaining bugs, if any.

0.8.0 FINAL:
- Clean up and re-indent the code
- Check documentation (README, FAQ)


For XMMS-SID v0.9/1.0
---------------------
- Fileinfo "follows play" -option. If enabled, information
  in fileinfo window is set / updated whenever tune/sub-tune
  changes.

- Editing facilities in fileinfo dialog?
  * song length
  * SID header editing
  * STIL editing is probably not sensible

- XSIDB, see xsidb.txt

  XMMS-SID could check XSIDB first and then fall back to
  STILdb and songlength db, maybe adding information to
  XSIDB if something is found.

  1) read STILdb
  2) read SLDB, combining data
  3) save as XSIDB

  Possibly it would be good to check the MD5sum always
  and if no match, ignore the LENGTH information?

  Problems:
  - preserving field formatting (COMMENT fields especially)
    from STIL ... is it worth it?


- Convenience functionality?
  retrieve latest HVSC and song-length databases automatically?
  use 'curl' or 'wget' binary or use libcurl and implement
  getting of those in plugin itself. example:

  0) If enabled:

  1) Get "http://www.tnsp.org/xs-files/LATEST", and
     "http://www.tnsp.org/xs-files/LATEST.sig".
     Contents might be something similar to:

HVSC		5.8		http://...
sldb		5.8		http://...
stable		0.8.0		http://www.tnsp.org/xs-files/xmms-sid-0.8.0.tar.gz
devel		0.9.0alpha0	http://www.tnsp.org/xs-files/xmms-sid-0.9.0alpha0.tar.gz

  2) Verify signature. Tell user about xmms-sid updates and
     ask user if he wants the HVSC/sldb updates.

  3) If yes, download updates and verify: my gpg signatures for hvscupdate.zip
     etc could be on tnsp.org, just get the packages themselves from
     original distribution sites.

  4) Unzip, install, etc... is there source for hvsc update tool? if not,
     it may have to be reimplemented. blah.

  security issues:
  - how to prevent dns-spoofing or other attempts
    to distribute invalid data?
  - if forged data is got: exploitation of further vulnerabilities
    in xmms-sid or unzip/tar may be possible
  - only good way would be PGP/GnuPG signing of packages, but
    that might be quite hard to implement...

    examine libgcrypt and libgpgme to see how it's done. preferable
    libgcrypt alone should be used, less depencies is better...
    but if it's too hard without gpgme, use it too.


Crazy ideas:
- Song "pre-rendering" support+position selector
  work like it "should". Option for those who have the
  CPU power (or patience) and enough RAM to spare for
  the whole song. (probably not feasible, dunno.)


For XMMS-SID2
-------------
Port to XMMS2.