Resources

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Formats)
Line 6: Line 6:
 
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.
  
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.
+
Resource formats often store user interface elements (dialog boxes, menus, etc.), graphics, sound, or text. There is usually also a way to store arbitrary custom data.
  
Formats listed here include:
+
Formats listed here may include:
 
* Formats that are embedded in executable files
 
* Formats that are embedded in executable files
 
* Stand-alone file formats that are loaded into memory at runtime
 
* Stand-alone file formats that are loaded into memory at runtime

Revision as of 15:39, 17 March 2016

File Format
Name Resources
Ontology

{{{caption}}}

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, sound, or text. There is usually also a way to store arbitrary custom data.

Formats listed here may 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

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox