20,741
edits
Catalog metadata: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 28: | Line 28: | ||
|author=<nowiki>James Turner</nowiki> | |author=<nowiki>James Turner</nowiki> | ||
|date=<nowiki>2015-03-06</nowiki> | |date=<nowiki>2015-03-06</nowiki> | ||
}} | |||
}} | |||
{{FGCquote | |||
|For all other aircraft, the intention for both these nightly builds and official releases is to use the aircraft catalog + package system, which is based around HTTP rather than an SCM system. I’m working at the moment on integrating the client parts into the launcher GUI. | |||
|{{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 | |||
|This is the way to decentralise aircraft deployment and discovery - ‘we’ (the project) will provide an official hangar of course but the idea is any end-user can add the hangar URL for FGUK, Lake of Constance or similar, and get those aircraft. Most importantly we can improve the end-user browsing and discovery experience by enforcing some required meta-data, images and similar in the catalogs, and we can manage the install process so that users don’t get confused about where to move an aircraft file.<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) | |||
|{{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> | |||
}} | }} | ||
}} | }} | ||