20,741
edits
Catalog metadata: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 44: | Line 44: | ||
<br/> | <br/> | ||
(Many end users struggle with the aircraft zips, they’re unsure if they need to extract them or not, and whereabouts to copy them, and what paths to set so the aircraft is usable. The package system is designed to avoid those issues) | (Many end users struggle with the aircraft zips, they’re unsure if they need to extract them or not, and whereabouts to copy them, and what paths to set so the aircraft is usable. The package system is designed to avoid those issues) | ||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33586444/ | |||
|title=<nowiki>Re: [Flightgear-devel] FGDATA and Jenkins</nowiki> | |||
|author=<nowiki>James Turner</nowiki> | |||
|date=<nowiki>2015-03-11</nowiki> | |||
}} | |||
}} | |||
{{FGCquote | |||
|The catalog is just an XML file, and the other files needed are the thumbnail images for each package, and the package .zips themselves; the system is deliberately designed to be host-able statically on any web provider. The ‘create_catalog.py’ gives one example of creating a suitable catalog XML file, but any other approach is also valid. | |||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33586444/ | |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33586444/ | ||
|title=<nowiki>Re: [Flightgear-devel] FGDATA and Jenkins</nowiki> | |title=<nowiki>Re: [Flightgear-devel] FGDATA and Jenkins</nowiki> | ||