Resources
From Just Solve the File Format Problem
(Difference between revisions)
(Created page with "{{FormatInfo |formattype=electronic |thiscat=Resources }} Incorporating non-executable data into a progam's source code can be inconvenient. A variety of techniques, and a...") |
Dan Tobias (Talk | contribs) |
||
| Line 2: | Line 2: | ||
|formattype=electronic | |formattype=electronic | ||
|thiscat=Resources | |thiscat=Resources | ||
| + | |image=Resources.jpg | ||
}} | }} | ||
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. | 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. | ||
Revision as of 01:22, 7 January 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 into executable files
- Stand-alone file formats that are loaded into memory at runtime
- Intermediate file formats
- Specialized source code formats that contain, or refer to, resource data
Formats
- AMOS AmBs
- AMOS Memory Bank
- Borland Delphi form
- DFF
- Dynamic-link library (Windows) - Resource-only DLLs are not uncommon.
- GEM resource file (Atari) (.rsc)
- Macintosh resource file (Mac OS Classic development) (.rsrc)
- Resource script file (.rc, .rc2)
- STOS memory bank
- VisualBasic form (.frm)
- Windows resource
- Xcode Core Data Model (.xcdatamodel, .xcdatamodeld)
