735
edits
(Add aerobatic, ultralight, avro tags) |
(Replace quotes with text and references.) |
||
Line 2: | Line 2: | ||
{{Package Management}} | {{Package Management}} | ||
== Status / News == | == Status / News == | ||
Line 14: | Line 12: | ||
* adding metadata tags, for better searching/usability the future | * adding metadata tags, for better searching/usability the future | ||
All of these are intended to help users browsing the aircraft, via the launcher or other methods. James's proposal is to post about this on the forum, and ask for volunteers to pick aircraft, and submit patches / updates to myself and some other willing reviewers (Stuart has also volunteered as reviewer, more people are welcome). Aside form ensuring high quality, we also need to ensure that aircraft maintainers are given the opportunity to update their own aircraft. Any co-volunteers to manage the process, and especially suggestions on how to manage this in a way that is friendly towards aircraft maintainers, but also gives a reasonable chance, that 90% of aircraft in FGaddon have up-to-date metatdata by the next release, are welcome. I’m sure we will have the usual debate on subjectivity of ratings, but, that’s another thing the reviewers will have to deal with. (James Turner suggested there’s some criteria on the wiki from the last time we did this?) (There’s a task on me to link the tagging system into the aircraft search, so that searching on ‘fighter’ or ‘glass-cockpit’ brings up appropriate matches. This tends to work out anyway when aircraft have a long-description text, but it’s still very beneficial to the launcher to have some meta-data about how aircraft are used)<ref>{{cite web | All of these are intended to help users browsing the aircraft, via the launcher or other methods. James's proposal is to post about this on the forum, and ask for volunteers to pick aircraft, and submit patches / updates to myself and some other willing reviewers (Stuart has also volunteered as reviewer, more people are welcome). Aside form ensuring high quality, we also need to ensure that aircraft maintainers are given the opportunity to update their own aircraft. Any co-volunteers to manage the process, and especially suggestions on how to manage this in a way that is friendly towards aircraft maintainers, but also gives a reasonable chance, that 90% of aircraft in FGaddon have up-to-date metatdata by the next release, are welcome. I’m sure we will have the usual debate on subjectivity of ratings, but, that’s another thing the reviewers will have to deal with. (James Turner suggested there’s some criteria on the wiki from the last time we did this?) (There’s a task on me to link the tagging system into the aircraft search, so that searching on ‘fighter’ or ‘glass-cockpit’ brings up appropriate matches. This tends to work out anyway when aircraft have a long-description text, but it’s still very beneficial to the launcher to have some meta-data about how aircraft are used) | ||
<ref>{{cite web | |||
|url = https://sourceforge.net/p/flightgear/mailman/message/35688820/ | |url = https://sourceforge.net/p/flightgear/mailman/message/35688820/ | ||
|title | |title = <nowiki>[Flightgear-devel] Improving FGaddon aircraft meta-data </nowiki> | ||
|author = <nowiki> James Turner </nowiki> | |author = <nowiki> James Turner </nowiki> | ||
|date = Feb 26th, 2017 | |date = Feb 26th, 2017 | ||
Line 23: | Line 22: | ||
}}</ref> | }}</ref> | ||
==Catalogs== | |||
The overall aim is to support a decentralized development system with the only central point being the aircraft package manager for end users. | |||
<ref>{{cite web | |||
|url = http://sourceforge.net/p/flightgear/mailman/message/33413096/ | |||
|title = <nowiki>Re: [Flightgear-devel] FGDATA split without Aircraft. Addon in SVN. (re)Suggesting a Submodule approach. (Re)Proposing a</nowiki> | |||
|author = <nowiki>James Turner</nowiki> | |||
|date = <nowiki>2015-02-13</nowiki> | |||
}}</ref>. Users can simply add a hangar URL for FGUK, Lake of Constance or similar, and browse those aircraft within the launcher. | |||
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. | |||
<ref>{{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] | |||
|author=<nowiki>James Turner</nowiki> | |author=<nowiki>James Turner</nowiki> | ||
|date=<nowiki>2015- | |date=<nowiki>2015-03-11</nowiki> | ||
}}</ref> | |||
}} | |||
fgmeta contains a 'create_catalog.py' script which runs over fgaddon but could be used against another aircraft store containing multiple aircraft to generate a catalog used by the launcher in combination with a webhost to publish aircraft to users. | |||
<ref>{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33550567/ | |||
| title=<nowiki>Re: [Flightgear-devel] FGData size reduction </nowiki> | |||
|title=<nowiki>Re: [Flightgear-devel] FGData size reduction</nowiki> | |||
|author=<nowiki>James Turner</nowiki> | |author=<nowiki>James Turner</nowiki> | ||
|date=<nowiki>2015-03-06</nowiki> | |date=<nowiki>2015-03-06</nowiki> | ||
}}</ref> | |||
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. | |||
<ref>{{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> | ||
|author=<nowiki>James Turner</nowiki> | |author=<nowiki>James Turner</nowiki> | ||
|date=<nowiki>2015-03-11</nowiki> | |date=<nowiki>2015-03-11</nowiki> | ||
}}</ref> | |||
== Supported Tags == | == Supported Tags == |