TODO.txt 2.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
  1. Stuff that needs to be done and wishlist:
  2. These are in no particular order.
  3. Some might be dupes, some might be done already.
  4. UNICODE:
  5. - Windows: Can use Unicode, but might only allow "codepages" ... Use
  6. GetProcAddress() to find Unicode entry points on WinNT-based
  7. systems, otherwise try to use a sane codepage.
  8. - OS/2: Codepages. No full Unicode in the filesystem, but we can probably make
  9. a conversion effort.
  10. Stuff:
  11. - Other archivers: perhaps tar(.gz|.bz2), RPM, ARJ, etc. These are less
  12. important, since streaming archives aren't of much value to games (which
  13. is why zipfiles are king: random access), but it could have uses for, say,
  14. an installer/updater.
  15. - Reduce malloc() pressure all over the place. We fragment memory like mad.
  16. - profile string list interpolation.
  17. - We have two different ways to find dir entries in zip.c.
  18. - Do symlinks in zip archiver work when they point to dirs?
  19. - Enable more warnings?
  20. - Use __cdecl in physfs.h?
  21. - Look for FIXMEs (many marked with "!!!" in comments).
  22. - Find some way to relax or remove the security model for external tools.
  23. - OSX shouldn't use ~/.app for userdir.
  24. - fscanf and fprintf support in extras dir.
  25. - Why do we call it openArchive and dirClose?
  26. - Sanity check byte order at runtime.
  27. - Memory locking?
  28. - Find a better name than dvoid and fvoid.
  29. - Can windows.c and pocketpc.c get merged?
  30. - There's so much cut-and-paste between archivers...can this be reduced?
  31. - General code audit.
  32. - Multiple write dirs with mount points?
  33. - Deprecate PHYSFS_setSaneConfig and move it to extras?
  34. - Why is physfsrwops.c cut-and-pasted into the ruby bindings?
  35. - Replace code from SDL...
  36. - Should file enumeration return an error or set error state?
  37. - Need "getmountpoint" command in test_physfs.c ...
  38. - Look for calloc() calls that aren't going through the allocation hooks.
  39. - Write up a simple HOWTO on embedding physicsfs in another project.
  40. - Archivers need abstracted i/o to read from memory or files (archives in archives?)
  41. - Probably other stuff. Requests and recommendations are welcome.
  42. // end of TODO.txt ...