User talk:Bugman
The collapsible script template
Noticed the {{collapsible script}} template. That will probably come in handy in many places.
I had no idea that there was such a thing as {{#tag: }}
. That may be useful later when I have played around with it.
Hmm, I see the template defaults to Dec Vadic's Imperial Arem Star. lol ;-)
—Johan G (Talk | contribs) 18:12, 16 October 2015 (EDT)
- There are quite a few places in the wiki cluttered up by long scripts or code segments. I guess it is mainly Nasal, though some other parts could benefit from other templates using collapsible NavFrame elements. The
{{#tag: }}
concept is quite useful for programmatically adding tags in templates, avoiding the initial HTML parsing, but it isn't perfect. Anyway, I can see it spreading on the wiki already :) As for the template default, I hope no one is curious and tries it out!
- Let me add that
{{#tag: }}
allows for transclusion within any HTML tag, which is normally not possible.
- The newsletter template discussion was moved to FlightGear wiki:Village pump#Newsletter templates (perm).
German FGAddon translation
Hi Edward,
are you still working on the German translation of the FGAddon article? If not, should I go ahead with the translation?
Cheers
Dg-505 (talk) 05:32, 7 April 2016 (EDT)
- Hi! I'm on holiday and have been distracted by other work. Go for it!
- Bugman (talk) 23:52, 11 April 2016 (EDT)
Lockheed P-38 Lightning
thanks for renaming that file... i can't believe that i misspelled that like that... sometimes the fingers think they know what the brain is trying to write :lol: Wkitty42 (talk) 11:16, 1 June 2016 (EDT)
- No problems! I often have the same problem :) Anyway, if you need any pages or files moved, just say.
The <aircraft>/info template
Hi,
It seems the new template for the aircraft info box or <aircraft>/info page doesn't show '_' (underscore) in the --aircraft= field. The old info box template did so it is probably a bug? AndersG (talk) 15:21, 23 June 2016 (EDT)
- Thanks for spotting that! I can see that that is a problem with the #titleparts function: "All underscores are automatically replaced with spaces". That is rather annoying. I might then create fgname1 to fgname10 as an alternative, as the number of
*-set.xml
files with underscores is very low.
The so caled "Emilianh H's hangar"
Hi,
While I appreciate your efforts, I would also appreciate it if this labeling would be possibly omitted, also not directly linked to.
I would also had appreciated some sort of preliminary discussion/warning prior to such labeling/linking if it would have taken place.
Thanks for your understanding
I4dnf (talk) 10:07, 15 July 2016 (EDT)
- No problems. I'm just experimenting with this, to allow for automated link creation for the new aircraft infobox template (see User:Bugman/Infobox Aircraft). This also includes the important note that the aircraft is {{non-GPL}}. Note that in the end, all wiki aircraft pages will be identified by hangar when available. But for the
| hangar = emilianh
parameter value, the heading "Emilian H's Hangar" has been removed. See User:Bugman/Infobox Aircraft#IAR 80.
- Thanks, however unfortunatley link to "website" still shows. How about "Aircraft by $Name" instead of "$Name's hangar" ? what happens if $Name has n aircraft hosted in m places?
- Regards,
- I don't quite follow, but we should be able to expand on the User:Bugman/Infobox Aircraft to match all aircraft author's needs. That is the aim of this new template to replace {{infobox aircraft}}. Click on the 'Edit' link, and then search for
emilianh
to see all the customisations I have made. We can change this to anything, to help automate the infobox creation. I thought I'd use your aircraft as a testing example for improving GitLab support in User:Bugman/Infobox Aircraft and Category:Repository link templates.
- I don't quite follow, but we should be able to expand on the User:Bugman/Infobox Aircraft to match all aircraft author's needs. That is the aim of this new template to replace {{infobox aircraft}}. Click on the 'Edit' link, and then search for
- The User:Bugman/Infobox Aircraft still displays the website and the devel-repo links. I, personally, for my aircraft, would prefer it if those were not ever shown, and only the download link was available. However I now noticed that on the actual IAR 80 page it is properly hidden.
- As for the second part of my previous question, what happens if I had say the iar80 hosted on github, the l10 on gitlab, and some other aircraft hosted on somesite.somwhere.else, to what does the "hangar" point to?
- I understand that in this particular case you were using it to improve an example gitlab based "hangar".
- Regards, I4dnf (talk) 10:55, 15 July 2016 (EDT)
- That is because you removed the
hangar
andaircraft
parameters from IAR 80/info, and addeddownload
, removing most of the automated aspects of the template. How the| hangar = emilianh
parameter value automates the template creation is totally up to the aircraft author - and it is directly coded into the template. I have created most of these in the User:Bugman/Infobox Aircraft testing template with direct author feedback. So for excluding the website and devel-repo links, that would simply require removing those lines in User:Bugman/Infobox Aircraft, where theemilianh
hangar parameter is found. Feel free to customise User:Bugman/Infobox Aircraft for the| hangar = emilianh
parameter as you wish. You'll see the result in the User:Bugman/Infobox Aircraft#IAR 80 when previewing the changes. You can also changeemilianh
to any value you wish.
- That is because you removed the