User talk:Openflight
Using preview and edit summary
Hello Openflight!
It may make things easier for you if you used the "Show preview" button below the text edit box. ;-)
When doing larger edits also consider adding a short summary of your edit, as that will make it easier to later see what work is done on a page.
Apart from those two points, please go on as usual! :-D
—Johan G (Talk | contribs) 06:21, 15 April 2012 (EDT)
- Thanks! I am a bit new to editing - preview is good to catch errors before publishing.
- Summary of edit - will do. I am having a whale of a time adding to the FG aircraft documentation. Documentation is the weak point of software development, it seems.
- Openflight 06:40, 15 April 2012 (EDT)
- I tend to use the preview a lot. I did not use it either when I first started to use a wiki. ;-)
- I could not agree more about the documentation. It seems programmers want to program, modellers want to model, and only a few wants to document. Goes for other things than aircraft, or this project as well. :-\
File names and categories
Hey,
great to see you uploading images! I'd like to note that you can add spaces to the titles to make it easier to retrieve them in a search. File:L39albatros.jpg for example does not show up under "albatros". It would if it was named like File:L39 Albatros.jpg ;-)
Another way to make your images findable is by adding categories to them. The upload wizard allows you to set categories on the "Describe" tab. An overview of available image categories can be found in Category:Images.
Cheers, Gijs 06:49, 16 April 2012 (EDT)
- Thanks! Lots to learn.
- Openflight 06:52, 16 April 2012 (EDT)
- I just have to add that you of course could add more categories if you believe they will be populated by more files, or for that matter make new subcategories in overpopulated categories, the ones in which you will not find the file you're looking for because of all the files. ;-)
The source field in the file information template
Hello! I noticed that in the file information template on some of the files you uploaded you have written "screenshot" in the source field.
When you have taken the screenshot yourself it is instead intended to contain "{{own}}" (see the documentation for the {{File information}} template).
== Summary == {{File information |Description = |Source = {{own}} (or a link to the source) |Date = |Author = }}
I do know that the intended use of that field is more than a bit ambiguous, so you are forgiven. :-)
—Johan G (Talk | contribs) 05:39, 21 April 2012 (EDT)
SureJohn. Will keep that in mind, I am just uploading stuff now will have to give meaningful descriptions later. (Why does that sound familiar.. )
Screenshot categories
Could you start adding a screenshot category? You can add one in the upload wizard or manually by adding [[Category:Name of the category]]
to the bottom of the file page.
These resources may be helpful (feedback on the first two is welcome, but on their discussion pages):
- FlightGear wiki:FlightGear screenshot categories
- Help:Categories
- Special:CategoryTree/Screenshots of aircraft
- Special:CategoryTree/FlightGear screenshots
Apart from that keep on going. :-)
—Johan G (Talk | contribs) 21:35, 12 October 2015 (EDT)
Got your comments, with next edit will do categories... Openflight (talk) 03:47, 13 October 2015 (EDT)
New articles for aircraft
Hi Openflight! I've noticed that you've created a number of new wiki pages documenting/reviewing aircraft in FGAddon (e.g. Dassault Mirage III, Avro Arrow, Aero Commander 500, Allegro 2000, etc.). I was wondering if you would consider converting these into the standard documentation for the aircraft? That includes filling out all the model information via Template:Infobox aircraft. See Template:Infobox aircraft#Translations - using subpages for how to add this to your articles. A good example to copy would be the current stub article for the Mirage 2000 (http://wiki.flightgear.org/index.php?title=Dassault_Mirage_2000&oldid=102403). Using this, you could then edit Template:Dassault to add the Mirage III. For clarity all the content that is part of a review could be placed in a == Review ==
section. Readers of the wiki are likely to highly appreciate the information provided by the aircraft infobox added to your articles. I've considered doing this before, but haven't been able to do that for all your articles. You can see one of my conversions at Piper PA-32.
Bugman (talk) 09:50, 14 May 2019 (EDT)
- Hi "Bugman",
- I just did a quick add of information, yes I noticed the elaborate templates, will work on converting format to the template like in PA-32
- Openflight (talk) 23:43, 15 May 2019 (EDT)
- Thank you! Just ask if there are issues/complications. Also, I've modified your post to demonstrate some MediaWiki standards. Responses on talk pages are indented using colons. Just edit this section and have a look. Higher and higher levels of response use more and more colons. E.g. this response uses
::
. And talk page posts are signed off using a special MediaWiki syntax of 4 tildes~~~~
. For example, below, I use the combination:: ~~~~
.
- Thank you! Just ask if there are issues/complications. Also, I've modified your post to demonstrate some MediaWiki standards. Responses on talk pages are indented using colons. Just edit this section and have a look. Higher and higher levels of response use more and more colons. E.g. this response uses