Resources

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
Line 14: Line 14:
 
* Specialized source code formats that contain, or refer to, resource data
 
* Specialized source code formats that contain, or refer to, resource data
  
== Formats ==
+
== Resource formats ==
 
* [[AMOS AmBs]]
 
* [[AMOS AmBs]]
 
* [[AMOS Memory Bank]] (.abk)
 
* [[AMOS Memory Bank]] (.abk)
Line 28: Line 28:
 
* [[Windows resource]] (.res)
 
* [[Windows resource]] (.res)
 
* [[Xcode Core Data Model]] (.xcdatamodel, .xcdatamodeld)
 
* [[Xcode Core Data Model]] (.xcdatamodel, .xcdatamodeld)
 +
 +
== Hybrid source code formats ==
 +
These formats are valid source code in some programming language (often [[C]]), and can also be read by some resource editors and viewers.
 +
* [[DEGAS Elite icon]]
 +
* [[XBM]]
 +
* [[XPM]]
  
 
[[Category:Executables]]
 
[[Category:Executables]]
 
[[Category:Development]]
 
[[Category:Development]]

Revision as of 14:07, 27 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

Resource formats

Hybrid source code formats

These formats are valid source code in some programming language (often C), and can also be read by some resource editors and viewers.

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox