Resources
From Just Solve the File Format Problem
(Difference between revisions)
m |
Dan Tobias (Talk | contribs) (→Formats) |
||
| Line 24: | Line 24: | ||
* [[Resource script file]] (.rc, .rc2) | * [[Resource script file]] (.rc, .rc2) | ||
* [[STOS memory bank]] (.mbk) | * [[STOS memory bank]] (.mbk) | ||
| + | * [[Strings File]] (OS-X, iOS) (.strings) | ||
* [[VisualBasic form]] (.frm) | * [[VisualBasic form]] (.frm) | ||
* [[Windows resource]] (.res) | * [[Windows resource]] (.res) | ||
Revision as of 22:33, 16 March 2016
Incorporating non-executable data into a progam's source code can be inconvenient. A variety of techniques, and associated resource formats, exist to address this issue.
Resource formats often store user interface elements (dialog boxes, menus, etc.), graphics, or sound. There is usually also a way to store arbitrary custom data.
Formats listed here include:
- Formats that are embedded in executable files
- Stand-alone file formats that are loaded into memory at runtime
- Intermediate file formats used in development
- Specialized source code formats that contain, or refer to, resource data
Formats
- AMOS AmBs
- AMOS Memory Bank (.abk)
- Borland Delphi form (.dfm)
- DFF
- Dynamic-link library (Windows) - Some DLLs are resource-only.
- GEM resource file (Atari) (.rsc)
- Macintosh resource file (Mac OS Classic development) (.rsrc)
- Resource script file (.rc, .rc2)
- STOS memory bank (.mbk)
- Strings File (OS-X, iOS) (.strings)
- VisualBasic form (.frm)
- Windows resource (.res)
- Xcode Core Data Model (.xcdatamodel, .xcdatamodeld)
