TODO.txt
1
Stuff that needs to be done and wishlist:
3
These are in no particular order.
4
5
6
7
8
Some might be dupes, some might be done already, some might be bad ideas.
From http://icculus.org/pipermail/physfs/2009-March/000698.html ...
9
10
11
12
13
- Add an API to find the "pref path" ... this is the directory where an
app's configuration data is supposed to go...which is usually somewhere
under the user directory, but not always. As it is platform-dependent,
platform-version dependent and sometimes even user-dependent, this should be
handled by the library and not the app.
14
- Archives formats provided by the implementation.
15
16
17
18
19
20
- Write support for various archives. I haven't decided how to do this yet,
but I'd like to.
- Replace the existing error strings with something more flexible...right now,
you have to pick a translation at compile time, which isn't too useful. It
might be nice to have real error codes for apps instead of just error
messages for humans, too.
21
- Add an API to expose a file's extended attributes to the application?
22
23
- Deprecate PHYSFS_setSaneConfig(). It really should have been in the extras
directory.
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
- Clean up the sources to match my ever-changing coding style. :)
From http://icculus.org/pipermail/physfs/2010-January/000821.html ...
- Using error codes instead of error messages
- Plugin system for the archive handlers
From http://icculus.org/pipermail/physfs/2010-January/000826.html ...
- Lua bindings
From http://icculus.org/pipermail/physfs/2010-January/000833.html ...
- SWIG bindings
From old TODO.txt...
45
46
- Other archivers: perhaps tar(.gz|.bz2), RPM, ARJ, etc. These are less
47
48
important, since streaming archives aren't of much value to games (which
is why zipfiles are king: random access), but it could have uses for, say,
49
50
an installer/updater.
- Reduce malloc() pressure all over the place. We fragment memory like mad.
51
- profile string list interpolation.
52
53
- We have two different ways to find dir entries in zip.c.
- Do symlinks in zip archiver work when they point to dirs?
54
- Enable more warnings?
55
- Use __cdecl in physfs.h?
56
- Look for FIXMEs (many marked with "!!!" in comments).
57
58
59
- Find some way to relax or remove the security model for external tools.
- OSX shouldn't use ~/.app for userdir.
- fscanf and fprintf support in extras dir.
60
61
62
- Why do we call it openArchive and dirClose?
- Sanity check byte order at runtime.
- Memory locking?
63
64
65
- Find a better name than dvoid and fvoid.
- General code audit.
- Multiple write dirs with mount points?
66
67
- Replace code from SDL...
- Should file enumeration return an error or set error state?
68
- Need "getmountpoint" command in test_physfs.c ...
69
- Write up a simple HOWTO on embedding physicsfs in another project.
70
71
72
73
74
75
76
77
78
79
Other stuff I thought of...
- moar asserts!
- constify!
- Does iPhone work?
- Fix CMake vs Doxygen.
- Doxygen replacement? (manpages suck.)
- Fix coding standards to match.
- See if we can ditch some #include lines...
80
81
82
83
- We lost Vista symlink support when removing isSymLink(). Pull it back from
revision control.
- PHYSFS_exists() fails if you mountIo with a NULL filename. We need to decide
how this API should work.
84
85
86
87
88
89
90
91
92
93
- ZIP64 support?
- LZMA support in zip archiver?
- bzip2 support in zip archiver?
- rewrite 7zip archiver.
- ryanify iso9660 code.
- Examine Chris Nelles's errorcode stuff.
- Move archiver_qpak.c code to archiver_unpacked.c?
- Cache basedir/userdir results (do we do this already?)
Probably other stuff. Requests and recommendations are welcome.
95
// end of TODO.txt ...