FlightGear wiki - User contributions [en]

FlightGear Newsletter November 2025

2025-12-19T17:01:09Z

Red Leader: Tidy up a few links

{{User:Skybike/Template:Newsletter-header-translate|2025-11}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''

== Development news ==



== Related Software tools and projects ==
=== Julia photoscenery generator ===
==== Photoscenery-GUI ====

[[File:Photoscenery-GUI-20251113-202721.jpg|thumb|Photoscenery-GUI Beta]]

Adriano Bassignana has begun writing the manual for the Photoscenery GUI, which has been published [[Julia photoscenery generator GUI]]. The manual currently contains the essential information for correct installation.

New features in the latest version include:

The tool, which already managed the rational downloading of tiles in various resolutions, now includes additional features accessible via its web interface to increase operational utility. The program's initialization has been modified to enable faster startup.

A new functionality has been introduced to read airports and radio navigation aids from files updated weekly—the same data sources used by FlightGear itself. This resolves the previous issue of airport misalignment between the tool and the simulator.

Route management has been improved. When loading a route for display on the map, the system now simultaneously loads data on local scenery to prevent unnecessary downloads. For users with a fast internet connection, real-time image downloading is possible. A fast, low-resolution preload feature also provides a valid overview of the surrounding area's coverage.

The interface allows users to view radio navigation aids and airports, along with their key information.

The [create route] mode enables users to generate a flight path by clicking on map points, airports, and navigation aids. Created routes can be saved and later imported into FlightGear for use.

Many other features will be documented on the Wiki in the future.

Source code: https://github.com/abassign/Photoscenery-GUI

For more information, see the discussion on the FG Forum: https://forum.flightgear.org/viewtopic.php?f=5&t=39066&start=390

==== Photoscenery-CLI ====

For all users of the Julia photoscenery in terminal in its pre-GUI version, it is a pleasure to report that the previously released "beta 5" version of Adriano Bassignana's Julia/Photoscenery (before development began on the GUI version, ver. 6) continues to work well on Flightgear installations in a Windows 10 (and possibly 11) environment. More info. on that may be found under [https://forum.flightgear.org/viewtopic.php?f=5&t=39066&start=435#p436792 this post] on the FG forum.

=== Framework for Canvas Add-on ===

Roman Ludwicki (PlayeRom on the forum) created a [https://github.com/PlayeRom/flightgear-addon-framework framework] for creating add-ons based on Canvas dialog boxes. After creating numerous add-ons, he realized he needed to separate the common code base. This led to the creation of a separate Framework project that could be attached to any add-on. The framework includes the following features:

# Automatic recognition and loading of add-on Nasal files into the appropriate namespaces (with an exclusion list if necessary).
# Ability to add a menu for restarting add-on Nasal files without having to change repository files.
# Ability to define keys for the multi-key command to restart add-on Nasal files without having to change repository files.
# A mechanism for checking whether there is a new version of your add-on to inform users about it.
# Base classes for Canvas windows that are created and destroyed on demand (Transient dialog), as well as created once during simulator startup (Persistent dialog).
# Ability to create Nasal unit tests and run them using multi-key command.

An example project using the Framework is the [https://github.com/PlayeRom/flightgear-addon-canvas-skeleton Canvas Skeleton] project, which can be used as a basis for creating a new add-on.

You can also see how his other add-ons are written, all based on the Framework (main branches):
# [https://github.com/PlayeRom/flightgear-addon-aerotow-everywhere Aerotow Everywhere]
# [https://github.com/PlayeRom/flightgear-addon-logbook Logbook]
# [https://github.com/PlayeRom/flightgear-addon-which-runway Which Runway]
# [https://github.com/PlayeRom/flightgear-addon-nasal-namespace-browser Nasal Namespace Browser]
# [https://github.com/PlayeRom/flightgear-addon-menu-aggregator Add-on Menu Aggregator]

=== Add-ons Menu Aggregator ===

Roman Ludwicki has created a new "[https://github.com/PlayeRom/flightgear-addon-menu-aggregator Add-ons Menu Aggregator]" add-on. The "Add-ons Menu Aggregator" add-on solves the problem of increasing menu clutter in FlightGear, which occurs after installing multiple add-ons. Each add-on can add its own items to the main menu, causing it to become very large and, at low resolutions, extend beyond the screen. This makes it difficult for users to find functions related to specific add-ons, and the menu itself becomes unreadable.

The "Add-ons Menu Aggregator" automatically aggregates menu entries from all installed add-ons and places them into one common menu item – "Add-ons." Each add-on receives its own submenu here, containing its original items while maintaining full functionality and layout.

{{#ev:youtube|gNH3MBpRxjo|480px||Add-ons Menu Aggregator - Polish audio}}

== In the hangar ==






=== Aircraft reviews ===
==== Laminar 13 Hang Glider for FlightGear ====

===== Flight Test & Personal Tweaks by VonS =====
Having recently become interested in gliding and soaring in FG, VonS thought to go a (simpler) step further and merely strapped a wing to themselves (or themselves to a wing). That of course was also a good opportunity to harmonize further a few of the control inputs on the Laminar 13 for their rig/setup, as well as (subtly) to modify some of the weight shifts, drag and lift values, etc. Representative clip below for those who enjoy hang gliders, both real ones and in the world of FG.

{{#ev:youtube|tHQqhl3Sf5w|||Laminar 13 Hang Glider for FlightGear. Flight Test & Tweaks by Vons |frame}}

If you're interested in seeing the flight test results and accessing the latest tweaks, visit the FG forum page at: https://forum.flightgear.org/viewtopic.php?f=19&t=42893&start=45#p436600

===== Additional Tweaks Information =====

FlightGear users interested in these custom tweaks may also want to check the recent gliders updates (October and November 2025) for the [https://forum.flightgear.org/viewtopic.php?f=4&t=43713&start=105#p435385 ASK 13 tweaks] and [https://forum.flightgear.org/viewtopic.php?f=4&t=43713&start=105#p436217 ASG 29 tweaks]

Review the posts carefully before downloading. Many of these adjustments, including lift, drag, and control harmonization values, were later applied to the Laminar hang glider as subtle improvements.

These tweaks were tested in FG 2020.3.19 and should be compatible with current versions. All mentioned gliders use JSBSim flight dynamics models (FDM).

For YASim-based tweaks by VonS, please contact him directly via PM on the FG forum, as most were not publicly released. Some exceptions are included in recent updates to Emmanuel Baranger's aircraft at the "Helijah FG Hangar."

Links to various modifications can be found at the bottom of the contributor's forum posts [https://forum.flightgear.org/viewtopic.php?f=3&t=43735 "Von S Various Mods"]. For a broader overview, see the VonS Various Mods thread in "Hangar Talk."

VonS began FDM tweaking in the mid-2010s, focusing on early 1900s and WWI aircraft, and has contributed significantly to FlightGear's open-source flexibility. For early aviation examples, see [https://forum.flightgear.org/viewtopic.php?f=4&t=43872&start=15 the Sopwith Camel thread (November 2025)] which also includes detailed technical posts by S&J, Lester-Boffo, Alant, and himself.

== Scenery corner ==




















== Community news ==









== Multiplayer events ==


=== Finished events ===
==== Independence Day Event 2025 ====
To celebrate Poland's Independence Day, the Polish Discord channel organized an Air Show with several performances. Clips are included in the video:

{{#ev:youtube|ekiLpbSXAmU|480px||Independence Day Event 2025}}






== Screenshot of the Month ==

If you want to participate in the screenshot contest, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.

{{Appendix}}



[[Category:FlightGear Newsletter|2025 11]]

British Aerospace Sea Harrier

2025-12-19T16:55:01Z

Red Leader: Fix spelling; remove rotted link to Art Nalls' website

{{:{{PAGENAME}}/info}}
The '''British Aerospace Sea Harrier''' (informally '''Shar''') is a naval short take-off and vertical-landing/vertical take-off and landing jet fighter, reconnaissance and attack aircraft, and a development of the [[Hawker Siddeley Harrier GR1|Hawker Siddeley Harrier]]. It first entered service with the Royal Navy in April 1980 as the Sea Harrier {{abbr|FRS1|Fighter, Reconnaissance, Strike, Mk. 1}} and became informally known as the "Shar" ('''S'''ea '''Har'''rier). Unusual in an era in which most naval and land-based air superiority fighters were large and supersonic, the principal role of the subsonic Sea Harrier was to provide air defence of the fleet from Royal Navy aircraft carriers. Retired in 2006, today there is only one airworthy Sea Harrier in the world. XZ439, a restored former Royal Navy Sea Harrier FA2, is operated in the United States by Art Nalls, a former USMC pilot.

The version currently modelled in [[FlightGear]] is the Sea Harrier {{abbr|FA2|Fighter, Attack, Mk. 2}}, an improved version with the {{wikipedia|Blue Vixen}} radar and the {{wikipedia|AIM-120 AMRAAM}} missile.

== Keyboard controls ==
{| class="keytable"
! Key
! Function
|-
|{{key press|m}}
|Vector thrust upwards
|-
|{{key press|Shift|m}}
|Vector thrust downwards
|-
|{{key press|h}}
|Toggle HUD on/off
|-
|{{key press|j}}
|Decrease air brake
|-
|{{key press|k}}
|Increase air brake
|-
|{{key press|e}}
|Release ordinance/fire gun
|-
|{{key press|w}}
|Cycle stick mode selector
|-
|{{key press|Ctrl|w}}
|Toggle station arming
|-
|{{key press|Ctrl|f}}
|Release countermeasure
|-
|{{key press|1}}/{{key press|2}}/{{key press|3}}/{{key press|4}}/{{key press|5}}/{{key press|6}}/{{key press|7}}
|Select station
|-
|{{key press|Shift|<nowiki>]</nowiki>}}
|Autostart
|-
|{{key press|Shift|c}}
|Toggle canopy
|-
|{{key press|n}}
|Next target
|-
|{{key press|Ctrl|n}}
|Previous target
|}

== Features ==
* A fully working weapons system, including realistic stores and gun behaviour
* Semi-realistic startup
* [[Bombable]] support
* [[Rembrandt]] support
* Full electrical system, including switchable instruments
* [[Aircraft Checklists|Checklists]] and [[Tutorials]] support
* Realistic [[autopilot]]
* Modeled limits
* [[Canvas]] {{abbr|HDD|Head-down Display}}
* Flare/chaff system
* {{abbr|CCIP|Constantly-Computed Impact Point}} bombing system
* {{abbr|RWR|Radar Warning Receiver}}
* Bombable-compatible AI aircraft
* Fuel System
* [[Instant Replay]] support
* Custom failures based on the new [[A Failure Management Framework for FlightGear|custom failures framework]].
* Backwards compatibility (tested on both FG 3.2 and 2.12.0)
* [[Howto:Implement pushback|Pushback]] truck

== Changes for the latest release (2.5.0) ==
* Nasal code style cleaned up
* All XML files encoded in UTF-8 w/o BOM; encoding added in headers
* Throttle and thrust vector levers fixed.
* Canvas HDD properly integrated
* Start Canvas-based radar
* All paths are now relative
* Some changes to the cockpit
* Some more bugfixes
* New splash texture
* License changed back to GNU GPL v2

== Development ==
<big>Last updated 23 June 2016</big>

=== For next release (2.6.0) ===
* Update docs
* Make new FDM
* Unify radar

=== Cockpit ===
* More detailed cockpit (more info required)

=== Model ===
* Better, more detailed model
* British 1,000lb bomb

=== Systems ===
* New radar (possibly using [[Canvas Radar]])
* Autoland system
* Realistic {{abbr|SMS|Stores Management System}}

=== FDM ===
* More realistic (data needed)

=== General ===
* New [[Canvas Widgets|Canvas dialogs]]

== Issues ==
=== FDM ===
* Aircraft swings on the ground.

== See also ==
* [https://forum.flightgear.org/viewtopic.php?f=4&t=24711 Forum topic]
* [https://www.dropbox.com/s/kot5l0x8oi9k5oy/AI%20harrier%20%26%20scenario.zip?dl=0 Bombable-compatible AI aircraft and scenario]

=== External links ===
* {{wikipedia|British Aerospace Sea Harrier|noicon=1}} (Wikipedia)
* [http://www.naval-technology.com/projects/fa2-sea-harrier/ Sea Harrier] (naval-technology.com)

{{British Aerospace}}

{{air-to-air refueling}}

Howto:Add aerotow hitch to an AI-aircraft

2025-12-07T21:06:17Z

Red Leader:

For the visualization of the tow rope, it is advantageous if a hitch position is defined for the AI tow plane.

To set the hitch position for the AI aircraft, add the following code to the top of the <tt>{aircraft}-ai.xml</tt> file:

<syntaxhighlight lang="xml">

<?xml version="1.0"?>
<PropertyList>

<nasal>
<load>
var rplayer = cmdarg();
rplayer.getNode("sim/hitches/aerotow/local-pos-x",1).setValue("x");
rplayer.getNode("sim/hitches/aerotow/local-pos-y",1).setValue("y");
rplayer.getNode("sim/hitches/aerotow/local-pos-z",1).setValue("z");
</load>
<unload>
rplayer.getNode("sim/hitches").remove();
</unload>
</nasal>



</PropertyList>

</syntaxhighlight>

In place of x, y, z, enter appropriate values for the hitch position.
Coordinate system: x forward, y to the left, and z up. The units are meters.

That's it! The tow rope ends at the defined position.

== Related content ==
* [[Soaring]]
* [[Improving Glider Realism]]
* [[Howto:Setup winch and aerotowing for JSBSim-aircraft]]

[[Category:Howto]]
[[Category:Aircraft enhancement]]

Property browser

2024-04-28T16:31:02Z

Red Leader: Apply templates; internal formatting; move Olsen quote and improve citation; typo fix

[[File:Property_Browser.jpg|thumb|270px|The property browser window]]
{{PropertyTree}}

The [[FlightGear]] '''property browser''' is a dialog used to browse, in-simulator, through all properties. Properties are internal, runtime state variables in FlightGear. The property browser cannot only be used to inspect all sorts of internal variables at runtime, but it can also be used to change the values of most properties easily (some being conceptually read-only, i.e. because they're exclusively written-to by a certain subsystem such as the FDM). For instance, you cannot change your frame rate by changing the frame counter obviously.

== Opening the property browser ==
The property browser can be opened while FlightGear is running either:
* By pressing the {{key press|/}} key (forward slash)
* Through the main [[menubar|menu]]: <tt>Debug > Browse Internal Properties</tt> (in older version: <tt>File > Browse Internal Properties</tt>).

Browse around to see the different data fields that are available. Just about everything interesting/useful is published in the property system. The browser allows you to inspect and even change values in the live running copy of FG.

=== Property Key Handler ===

The property key handler provides a better experience for developers when using the property tree and is suited to keyboard operations. See [[Property Key Handler]] for more information.

== Tied properties ==
Some properties are so called ''tied'' properties which are directly mapped to internal C++ variables and they cannot be modified using the property browser, we are currently trying to get rid of tied properties, see [[Howto:Use Property Tree Objects]] for details.

In addition, even some non-tied properties cannot be modified because they are by default constantly written/modified by another subsystem (in C++/Nasal space), possibly updating properties at frame rate, this applies for example to the frame rate counter, which is constantly updated by C++ code - so trying to set it from Nasal would be kind of pointless.

Also certain properties are only read/applied during initialization/re-initialization (startup/reset) of the sim, while others require the corresponding subsystems to be reinitialized.

{{Note|{{cquote|1=
The origin of tied properties was largely to address "hypothetical" performance concerns in the early days. Coders could continue to use native compiled variables and simultaneously expose them to the property system. Early property system skepticism included issues like performance and use of global structures. Those have largely not proven out to be actual issues. So without looking deep into how much effort/change/impact this would require, I think for the most part the whole tied property aspect of the API could go away and the property system API would simplify quite a bit.
|2={{cite web|url=https://sourceforge.net/p/flightgear/mailman/message/37280934/|author=Curtis Olson|title=Re: [Flightgear-devel] Making Simgear properties threadsafe|date=12<sup>th</sup> May 2021}}}}}}

== Tips and tricks ==
Apart from setting a property by clicking it and using the text field and Set button, there is many things that can be done through the property browser:
{| class="wikitable"
! Mouse click while holding on keyboard !! Function !! Comment
|-
| {{key press|Ctrl}}
| on '.' toggle verbose mode
on '..' goto root
on any bool property: toggle true/false value
| Verbose mode is explained below
|-
| {{key press|Shift}}
| on '.' dump properties to console
display property in top left corner of the flightgear screen
| To ''remove the property'', {{key press|Ctrl|Shift}} and click on another property
|-
| {{key press|Alt}}
| toggle trace_write attribute of the selected property
| Since 04/2024 on 'next'; details below in 'verbose mode'
|-
| {{key press|Ctrl|Alt}}
| toggle trace_read attribute of the selected property
| Since 04/2024 on 'next'; details below in 'verbose mode'
|}

== Verbose mode ==
In verbose mode, toggled by ctrl-clicking an "<tt>.</tt>" entry or toggling <code>/sim/gui/dialogs/property-browser/show-flags</code>, some additional information is shown as flags like this

foo = '123.456' (double; AT)

{| class="wikitable"
! Flag !! Meaning !! Comment
|-
| r || Read protected || Showing that a property can not be read.
|-
| w || Write protected || Showing that a property can not be written to.
|-
| R || Trace read operations || rowspan="2" | In <code>--log-level=info</code> create log line with TRACE prefix on write/read operation; set with <code><foo trace-write="y"></code>.
Since 04/2024 on next R and W flag can be set on the fly via the property browser (see above)
|-
| W || Trace write operations
|-
| A || Archive bit set || Makes writeProperties() also save this property in restricted mode ("save flight"), while all others are only saved in full mode.
|-
| U || User archive bit set || Saved into ~/.fgfs/autosave.xml, and restored next time. 
|-
| T || Tied property || Only the C/C++ code that owns a tied property can write to it. Also, listeners will not be triggered.
|-
| L<N> || Number of listeners
|
|-
|=> <path>
|Alias target
|This prop is an alias for <path> (since 04/2024 on 'next')
|-
|}

{{FGCquote
|1= <pre>props.globals.getNode("/sim/aircraft").getAttribute("references")

does now return the reference counter -- the number of co-owners
of the shared pointer. This is really only useful for debugging.
And here's again a summary of all the attribute names:

children ... returns number of children (faster than size(n.getChildren()!)
listeners ... return number of attached listeners
references ... returns number of co-owners (+ 2 for own consumption)
tied ... returns whether a node is "tied" (in which case listeners
might not get triggered)
alias ... whether the node is an alias to another node
read ... whether the node is read-protected
write ... whether the node is write-protected
archive ... whether the "archive" flag is set, which makes the
node saved with "Save Flight" in the menu
trace-read ... whether the node is being traced for read operations
trace-write ... whether the node is being traced for write operations
userarchive ... whether the node will be saved to ~/.fgfs/autosave.xml
on exit
</pre>
|2= {{cite web
| url = http://sourceforge.net/p/flightgear/mailman/message/15645291/
| title = <nowiki>Re: [Flightgear-devel] FlightGear/Plib periodic stutter notes</nowiki>
| author = <nowiki>Melchior FRANZ</nowiki>
| date = Oct 21st, 2007
| added = Oct 21st, 2007
| script_version = 0.25
}}
}}

== Other ways to open the property browser ==
=== Forcing open the browser on startup ===
You can force the browser to open on startup, through the following command:
--prop:browser=/sim/path/that/you/want/to/show

More than one property browser can be opened like this.
--prop:browser=position --prop:browser[1]=orientation

=== Opening the property browser through nasal ===
Calling <code>gui.property_browser(<path>)</code> opens a property browser for <path>. While it can be called more than once, though all the dialogues will be drawn on top of each other in the centre of the screen. Example:

<syntaxhighlight lang="nasal">
settimer(func {
gui.property_browser("/position");
gui.property_browser("/orientation");
}, 0);
</syntaxhighlight>

=== Displaying On-Screen property values through nasal ===
Create a file (let's call it display-props.nas) with instructions such below:

<syntaxhighlight lang="nasal">
# On-screen displays
var enableOSD = func {
var left = screen.display.new(20, 10);
var right = screen.display.new(-300, 10);

left.add("/orientation/heading-deg");
left.add("/environment/wind-from-heading-deg");
left.add("/environment/wind-speed-kt");
right.add("/controls/flight/rudder");
}
enableOSD();
</syntaxhighlight>

Add the path/to/display-props.nas in your aircraft-set.xml or in your $FG_HOME/ inside a Nasal/ folder.

== Related content ==
=== Wiki articles ===
* [[Property Key Handler]]

=== Source code ===
* {{fgdata source|path=gui/dialogs/property-browser.xml}}

[[Category:Menubar]]
[[Category:Property Tree]]

FlightGear wiki:Village pump

2024-01-30T21:58:32Z

Red Leader:

__NEWSECTIONLINK__
{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]|[[/Archive 2015|2015]]|[[/Archive 2016|2016]]|[[/Archive 2017|2017]]|[[/Archive 2018|2018]]|[[/Archive 2019|2019]]|[[/Archive 2020|2020]]|[[/Archive 2021|2021]]|[[/Archive 2022|2022]]}}
{{shortcut|FGW:VP}}

Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].

Please <span class="plainlinks">[{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics]</span> to the '''bottom''' of this page.

Old discussions should be moved to a [[FlightGear wiki:Village pump/Archive YEAR]]. These discussions can then be moved to a relevant talk page if appropriate.

__TOC__

== MediaWiki updated to 1.39.6 ==

We have updated MediaWiki to its latest LTS version 1.39.6 today. Although we've tested the update, chances are that we've missed certain scenarios or features. Please report any issues that you may encounter.

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:31, 30 January 2024 (UTC)

== Embedded YouTube videos broken ==

It seems that the [[mw:Extension:EmbedVideo|EmbedVideo extension]] was removed at some point. Consequently, pages such as [[Howto:Creating FlightGear Promo Videos]] are broken. At present, the best replacements seems to be [[mw:Extension:EmbedVideo_(fork)|a fork]] and [[mw:Extension:YouTube|Extension:YouTube]].

—'''''[[User:Red Leader|<span style="color:red">Red Leader</span>]]''''' ([[User talk:Red Leader|talk]], [[Special:Contributions/Red Leader|contribs]]) 19:21, 30 January 2024 (UTC)

: Hi,
: Thanks for the report. It was introduced by today's update, but should be fixed now.
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 21:21, 30 January 2024 (UTC)

:: Confirmed, thanks. And I’d completely forgotten about {{[[Template:Wikipedia|wikipedia]]}}. 😅
:: '''''[[User:Red Leader|<span style="color:red">Red Leader</span>]]''''' ([[User talk:Red Leader|talk]], [[Special:Contributions/Red Leader|contribs]]) 21:57, 30 January 2024 (UTC)

Template:Archives

2024-01-30T19:24:59Z

Red Leader: Missed a bit

<div style="float: right; clear: right;">
{| style="text-align: center; font-size: 85%; background-color: #f9f9f9; border: 1px solid #aaa; padding: 5px; margin: 1em 0;"
| [[File:Replacement filing cabinet.png|40px|alt=|link=]]<br>'''[[Help:Archiving a talk page|Archives]]'''
|-
| {{{1|{{error|Please add at<br>least one parameter}}}}}{{#if: {{{2|}}} | , {{{2}}} }}
|-
{{#if: {{{3|}}} | {{!}} {{{3}}}{{#if: {{{4|}}} | , {{{4}}} }} }}
|-
{{#if: {{{5|}}} | {{!}} {{{5}}}{{#if: {{{6|}}} | , {{{6}}} }} }}
|-
{{#if: {{{7|}}} | {{!}} {{{7}}}{{#if: {{{8|}}} | , {{{8}}} }} }}
|-
{{#if: {{{9|}}} | {{!}} {{{9}}}{{#if: {{{10|}}} | , {{{10}}} }} }}
|-
{{#if: {{{11|}}} | {{!}} {{{11}}}{{#if: {{{12|}}} | , {{{12}}} }} }}
|}
</div>
<noinclude>
{{-}}
{{Informative template|1=
__NOTOC__
== Usage ==
This template is for containing links to [[Help:Archiving a talk page|archives of talk pages]].

== Goal ==
{{obr}}'''Archives'''{{!}}archive{{!}}''archive 2''{{!}}''archive 3''{{!}}''archive 4''{{!}}''archive 5''{{!}}''archive 6''{{!}}''archive 7''{{!}}''archive 8''{{!}}''archive 9''{{!}}''archive 10''{{!}}''archive 11''{{!}}''archive 12''{{cbr}}

; archive (''1-12'') : Link to archive. Only the first one is mandatory.

== Examples ==
<nowiki>{{Archives|[[/Archive 2014|2014]]}}</nowiki>
{{Archives|[[/Archive 2014|2014]]}}{{-}}

<nowiki>{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]}}</nowiki>
{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]}}{{-}}

== Related templates ==
* {{tl|Talk archive}}
}}

[[Category:Templates]]

</noinclude>

Template:Archives

2024-01-30T19:23:12Z

Red Leader: Looks like we have to expand the options to support the Village Pump.

<div style="float: right; clear: right;">
{| style="text-align: center; font-size: 85%; background-color: #f9f9f9; border: 1px solid #aaa; padding: 5px; margin: 1em 0;"
| [[File:Replacement filing cabinet.png|40px|alt=|link=]]<br>'''[[Help:Archiving a talk page|Archives]]'''
|-
| {{{1|{{error|Please add at<br>least one parameter}}}}}{{#if: {{{2|}}} | , {{{2}}} }}
|-
{{#if: {{{3|}}} | {{!}} {{{3}}}{{#if: {{{4|}}} | , {{{4}}} }} }}
|-
{{#if: {{{5|}}} | {{!}} {{{5}}}{{#if: {{{6|}}} | , {{{6}}} }} }}
|-
{{#if: {{{7|}}} | {{!}} {{{7}}}{{#if: {{{8|}}} | , {{{8}}} }} }}
|-
{{#if: {{{9|}}} | {{!}} {{{9}}}{{#if: {{{10|}}} | , {{{10}}} }} }}
|-
{{#if: {{{11|}}} | {{!}} {{{11}}}{{#if: {{{12|}}} | , {{{12}}} }} }}
|}
</div>
<noinclude>
{{-}}
{{Informative template|1=
__NOTOC__
== Usage ==
This template is for containing links to [[Help:Archiving a talk page|archives of talk pages]].

== Goal ==
{{obr}}'''Archives'''{{!}}archive{{!}}''archive 2''{{!}}''archive 3''{{!}}''archive 4''{{!}}''archive 5''{{!}}''archive 6''{{!}}''archive 7''{{!}}''archive 8''{{!}}''archive 9''{{!}}''archive 10''{{!}}''archive 11''{{!}}''archive 12''{{cbr}}

; archive (''1-10'') : Link to archive. Only the first one is mandatory.

== Examples ==
<nowiki>{{Archives|[[/Archive 2014|2014]]}}</nowiki>
{{Archives|[[/Archive 2014|2014]]}}{{-}}

<nowiki>{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]}}</nowiki>
{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]}}{{-}}

== Related templates ==
* {{tl|Talk archive}}
}}

[[Category:Templates]]

</noinclude>

FlightGear wiki:Village pump

2024-01-30T19:21:11Z

Red Leader: /* Embedded YouTube videos broken */ new section

Grumman F-14 Tomcat Weapons Operations

2024-01-30T19:10:41Z

Red Leader: Switch to interwiki link

This page explains how to operate weapons and the related radar modes for the [[Grumman_F-14_Tomcat|Grumman F-14 Tomcat]].

== Version Warning ==
{{Note|
Be aware that the documentation in this page refers to the development version of the F-14, which is maintained in a [https://github.com/Zaretto/fg-aircraft GitHub repository]. Some features might therefore not be available, if you use the less frequently updated version from [[FGAddon|FGAddon]].
}}

The development of the weapons and radar in the F-14 are related to [https://discord.gg/MBWnqHC4 Operation Red Flag], the premier military aviation organization for the flight simulator FlightGear!

== Weapons Operation ==
NB: Especially for gunning you might want to set SAS Roll to off to prevent the plane from oscillating when using aggressive stick input.

NB: In some new versions of FlightGear, the {{Key press|w}} key is replaced by the {{Key press|m}} key to select weapons.

===M61A1 Vulcan (gun)===
*At startup, the ammunition store is filled with 675 round. There is an option on the '''Fuel and Stores''' dialog in the '''Tomcat Controls''' Menu to allow the gun to be reloaded
*Select HUD A/A Mode on the Display panel, on pilot's right console. A multikey shortcut is also available {{Key press|:}}{{Key press|A}}{{Key press|H}}{{Key press|a}}. Having the HUD in this mode is not mandatory however when the HUD is in the right mode the guidance symbology will assist with target identification and aiming.
*Select Gun mode with the Stick Weapon Mode Selector ({{Key press|w}}). A pipper, the G symbol with a number showing approximately the remaining rounds x 100 and a closure rate scale are displayed in the HUD. The closure rate scale is active only if a target has been locked ({{Key press|y}}) by the radar with TWS AUTO mode (diamond on the HUD).
*Switch Master Arm on cycle with {{Key press|CTRL-w}}, the X on the G symbol means Master Arm off or in training mode.
* Press {{Key press|e}} to fire the gun.

===AIM-9M Sidewinders===
*Select a weapons set using the menu: Tomcat Controls > Fuel and Stores: "FAD light" has 4 sidewinders, "FAD", "FAD heavy" and "Bombcat" have 2 of them.
*Select HUD A/A Mode on the Display panel, on pilot's right console. A multikey shortcut is also available ({{Key press|:}}{{Key press|A}}{{Key press|H}}{{Key press|a}}).
* Select "SW" mode with the Stick Weapon Mode Selector ({{Key press|w}}).
*Switch to the RIO view ({{Key press|Ctrl|v}}).
*Select pylons 1 and 8, down position, on the Armament panel, on RIO's left console. A shortcut toggles these two switches so you can select or deselect all AIM-9 in one keyboard stroke ({{Key press|Ctrl|m}}) without leaving pilot's view. If you have 4 sidewinders, then after shooting the first 2 you need to toggle the pylons 1 and 8 into the up position.
*Switch back to the pilot's view ({{Key press|Ctrl|v}}).
* Switch Master Arm on, you hear the search signal of the seeker head, a low volume buzz sound.
*Now prior to be fired, the AIM-9 must have a lock on a target. Multiplayers, AI aircraft, and AI tankers can be locked (radar lock with {{Key press|y}}). The minimal lock distance is 10 NM, the target must be approximately inside a 80° cone centred on datum line. When locked, the signal buzz volume becomes louder and the 2 red "LOCK" lights at the top of the canopy frame are lit. For best results try to shoot ({{Key press|e}}) at a 3 to 6 NM range and with the target centred on the aircraft velocity vector (when the 2 red "SHOOT" lights at the top of the canopy frame are lit). The missile will explode at the smaller distance possible. However if this distance is above 70 meters, it will continue its trajectory without guidance.

===AIM-7 Sparrow and AIM-54 Phoenix===
*Select a weapons set using the menu: Tomcat Controls > Fuel and Stores: "FAD" has 2 Sparrows and 4 Phoenix, "FAD light" has 4 Sparrows, "FAD heavy" has 6 Phoenix.
*Select A/A Mode, master arm etc. as with Sidewinders.
*Select "SP-PH" mode with the Stick Weapon Mode Selector ({{Key press|w}}).
*Set the appropriate pylons into the up position: 3, 4, 5, 6 for the pylons below the belly, 1 and 8 under the wing in up position for "FAD" (2 Sparrows, the 2 Sidewinders are selected in the down position of 1/8.
*Obtain a radar lock by using {{Key press|y}} the the next target and {{Key press|Ctrl|y}} the the previous target.
*Launching the missiles is the same as for the Sidewinders, but there is no growling sound and the max shooting range are larger: up to 30+ nm for the {{Wikipedia|AIM-7_Sparrow}} and 100+ nm for the {{Wikipedia|AIM-54_Phoenix}}.

===Bombs===
NB: only CCIP mode is implemented - and only dumb low-drag unguided bombs - and only single release.
*Select the right weapons' set using the menu: Tomcat Controls > Fuel and Stores: "Bombcat" has 4 Mk83 bombs.
*Master arm on
*Select A/G Mode
*Select "Off" mode with the Stick Weapon Mode Selector (yes, off - you will still be able to pull the trigger in A/G mode).
*Set the appropriate pylons into the up position: 3, 4, 5, 6.
*No need for locking with the radar. There is a CCIP in the HUD.
*Set wing sweep to manual and 55 deg.
*Make sure you are high above terrain (e.g. 10000 ft) and initiate a steep dive to 40 degs. Deploy speed brakes in order not to get too fast. Make sure wings are levelled, otherwise the bomb will not hit even though the pipper is on the target (there is currently no vertical bomb fall line implemented in the HUD).
*Release the bomb when the target is within the circle around the bottom of the HUD and before you reach 2000 ft above ground.

Find out what is working for you - it is not that simple.

==Radar Scan Modes==
===Key Bindings===
{{Key press|y}}: Next target

{{Key press|Shift|y}}: Cycle azimuth field width

{{Key press|Shift|u}}: Undesignate (very useful for PAL mode)

{{Key press|i}}: Tilt radar up

{{Key press|Shift|i}}: Tilt radar down

{{Key press|Shift|d}}: Cycle number of bars

{{Key press|Ctrl|n}}: Cycle radar scan modes

{{Key press|d}}: Pilot Auto Lockon mode (PAL) [click {{Key press|Ctrl|n}} to exit]

{{Key press|r}}: Single Target Track mode (STT)

{{Key press|Shift|e}} and {{Key press|r}}: Radar range when not in PAL mode.

{{Key press|q}}: Radar standby

===Modes===
Use {{Key press|Ctrl|n}} to cycle between radar scan modes (alternatively press the corresponding buttons on the RIO's front console).

{| class="wikitable"
|-
! Mode !! Notes
|-
| '''PD SEARCH''' || Has the longest RCS sensitivity of the modes. Will only show targets that has above/below a certain closure-rate. Notchable. Will not show targets altitude or heading.
|-
| '''RWS''' || Medium RCS sensitivity. Notchable.
|-
| '''P SEARCH''' || Basically a ground/sea radar. Cannot be notched.
|-
| '''PAL''' || Scans the area around the HUD, fixed at 10nm range. Automatically enters STT for anything it sees. Note that when in this mode, none of the RIO mode push buttons will lit up.
|-
| '''P STT''' || Single target track. Cannot be notched, wont produce closure-rate output.
|-
| '''PD STT''' || Single target track. Can be notched.
|-
| '''TWS MAN''' || Once a target has been scanned twice within some seconds, groundtrack (headings) is displayed on TID. Only has 2 options for bars/az combinations. Has the shortest RCS sensitivity of the modes. Notchable.
|-
| '''TWS AUTO''' || Is disabled / does not work.
|}

==== Missile Notes ====

* AIM-7 needs STT mode.

* AIM-9 needs STT mode or TWS mode with something selected. Or radar in standby, then it will lock onto whatever is at bore.

* AIM-54 need either STT or TWS with something selected (in which case it will go active immediately with reduced range).

====How to Notch====
Notching means flying manoeuvrers to make an aircraft less detectable on radar/evade it. It is sometimes called beaming.

If you are flying against an F-14, keep the F-14 on your 3 or 9 o'clock and make sure that seen from the F-14 point of view that he will see terrain behind you.

====Datalink====

Aircraft on datalink that are inside the radar field will be shown on TID (even if the radar is standby). The backseater needs to take care to enter the datalink channel at the top of the right panel (IFF is taken care of by the pilot at the top of the pilot's right panel).

====Misc====

RWS/TWS MAN/PDSearch/PSearch will able to show 19 targets, MP or not. TWS can show groundtrack on max 10 of them.

Radar elevation, commanded and actual, is shown on gauge left of DDD display. It is in relation to horizon in all modes except PAL.

Each mode remembers its own bars and az settings. So if you switch to 1 bar in RWS, and then switch to PD SEARCH it might have 8 bars, when you switch back to RWS you will have 1 bar again. Radar antennae elevation/azimuth is shared between modes though.

====Moving Radar Azimuth Field Left and Right====

There are no key bindings for moving the radar azimuth field left and right when not 120. To use this, enable it from FG joystick dialog.

====Dual Control====

When connecting as a Radar Intercept Officer (RIO aka. [[wikipedia:weapon systems officer|WSO]]), the pilot will no longer be able to control the radar - it is all done from the dual control RIO MP seat. The RIO is able to control the station switches.

Make sure that you as a RIO do not switch modes and stuff too fast, allow for a short moment for each change you make to propagate to the pilot.

If the RIO selects something and it fails pilot screen will show selection handover fails, the pilot could try to press y to repeat the handover and if successful, and then ask RIO to cycle modes if RIO had commanded STT, to make the pilots radar try to enter STT again.

==Related Information==
{{#ev:youtube|ibHrZyAQ1C4|||A tutorial video explaining how to fire the F-14B's missiles.|frame}}

User:Red Leader

2022-09-02T12:02:49Z

Red Leader: Update external links

__NOTOC__
{{User
|name = Red Leader
|location = United Kingdom
|interests =
* [https://www.flightgear.org/ FlightGear]
* {{Wikipedia|Military aircraft|noicon=1}}
* [https://www.lego.com/ Lego]
|callsign =
* Red-Led
* RLTest1
* RLTest2
|favourite =
* [[Grumman F-14 Tomcat]]
* [[British Aerospace Sea Harrier]]
* [[Dassault Mirage 2000-5]]
* [[Saab JA-37 Viggen]]
}}

My involvement with flight simulators started when I got [https://ysflight.org/ YSFlight], another free flight simulator. Although it was great fun, it wasn’t very realistic, so I wanted something better. After looking at {{wikipedia|Microsoft Flight Simulator X|noicon=1}} and {{Wikipedia|Combat Flight Simulator 3: Battle for Europe|Combat Flight Simulator|noicon=1}}, I found [https://www.flightgear.org/ FlightGear]. Since then I’ve wanted to improve FlightGear and make it better for the end-user.

In late August 2015, I became an administrator on the [[FlightGear Wiki]].

Since Autumn 2018, I have been essentially inactive within the community due to other commitments in my life. I do, however, intend to return to FlightGear one day, and I still keep a very dim view of things going on here. It is best to contact me via private message on the FlightGear forum ({{forum link|text=profile|type=member|u=17099}}); I should be fairly prompt in responding.

== Projects ==
=== Simulator ===
* [[British Aerospace Sea Harrier]] development. {{paused}}
* [[Scripted AI Objects]] development (with {{usr|5H1N0B1}}). {{paused}}
* Starting the [[Canvas HUD]] framework. {{not done}}

=== Wiki ===
* Documenting the [[Nasal]] {{abbr|API|Application Programming Interface}} (see my [[/Nasal documentation proposal|Nasal documentation proposal]]) {{paused}}

== Pages ==
* [[/Sandbox|My sandbox]]
* [[/Nasal documentation proposal|Nasal documentation proposal]]

[[Category:Users]]

User:Red Leader

2021-02-28T16:43:14Z

Red Leader: Use U+2019 for apostrophe instead of U+0027

__NOTOC__
{{User
|name = Red Leader
|location = United Kingdom
|interests =
* [http://www.flightgear.org/ FlightGear]
* {{Wikipedia|Military aircraft|noicon=1}}
* [http://www.lego.com/en-gb/ Lego]
|callsign =
* Red-Led
* RLTest1
* RLTest2
|favourite =
* [[Grumman F-14 Tomcat]]
* [[British Aerospace Sea Harrier]]
* [[Dassault Mirage 2000-5]]
* [[Saab JA-37 Viggen]]
}}

My involvement with flight simulators started when I got [http://www.ysflight.com/ YSFlight], another free flight simulator. Although it was great fun, it wasn’t very realistic, so I wanted something better. After looking at {{wikipedia|Microsoft Flight Simulator X|noicon=1}} and {{Wikipedia|Combat Flight Simulator 3: Battle for Europe|Combat Flight Simulator|noicon=1}}, I found [https://www.flightgear.org/ FlightGear]. Since then I’ve wanted to improve FlightGear and make it better for the end-user.

In late August 2015, I became an administrator on the [[FlightGear Wiki]].

Since Autumn 2018, I have been essentially inactive within the community due to other commitments in my life. I do, however, intend to return to FlightGear one day, and I still keep a very dim view of things going on here. It is best to contact me via private message on the FlightGear forum ({{forum link|text=profile|type=member|u=17099}}); I should be fairly prompt in responding.

== Projects ==
=== Simulator ===
* [[British Aerospace Sea Harrier]] development. {{paused}}
* [[Scripted AI Objects]] development (with {{usr|5H1N0B1}}). {{paused}}
* Starting the [[Canvas HUD]] framework. {{not done}}

=== Wiki ===
* Documenting the [[Nasal]] {{abbr|API|Application Programming Interface}} (see my [[/Nasal documentation proposal|Nasal documentation proposal]]) {{paused}}

== Pages ==
* [[/Sandbox|My sandbox]]
* [[/Nasal documentation proposal|Nasal documentation proposal]]

[[Category:Users]]

User:Red Leader

2021-02-28T13:00:15Z

Red Leader: Remove first heading

__NOTOC__
{{User
|name = Red Leader
|location = United Kingdom
|interests =
* [http://www.flightgear.org/ FlightGear]
* {{Wikipedia|Military aircraft|noicon=1}}
* [http://www.lego.com/en-gb/ Lego]
|callsign =
* Red-Led
* RLTest1
* RLTest2
|favourite =
* [[Grumman F-14 Tomcat]]
* [[British Aerospace Sea Harrier]]
* [[Dassault Mirage 2000-5]]
* [[Saab JA-37 Viggen]]
}}

My involvement with flight simulators started when I got [http://www.ysflight.com/ YSFlight], another free flight simulator. Although it was great fun, it wasn't very realistic, so I wanted something better. After looking at {{wikipedia|Microsoft Flight Simulator X|noicon=1}} and {{Wikipedia|Combat Flight Simulator 3: Battle for Europe|Combat Flight Simulator|noicon=1}}, I found [https://www.flightgear.org/ FlightGear]. Since then I've wanted to improve FlightGear and make it better for the end-user.

In late August 2015, I became an administrator on the [[FlightGear Wiki]].

Since Autumn 2018, I have been essentially inactive within the community due to other commitments in my life. I do, however, intend to return to FlightGear one day, and I still keep a very dim view of things going on here. It is best to contact me via private message on the FlightGear forum ({{forum link|text=profile|type=member|u=17099}}); I should be fairly prompt in responding.

== Projects ==
=== Simulator ===
* [[British Aerospace Sea Harrier]] development. {{paused}}
* [[Scripted AI Objects]] development (with {{usr|5H1N0B1}}). {{paused}}
* Starting the [[Canvas HUD]] framework. {{not done}}

=== Wiki ===
* Documenting the [[Nasal]] {{abbr|API|Application Programming Interface}} (see my [[/Nasal documentation proposal|Nasal documentation proposal]]) {{paused}}

== Pages ==
* [[/Sandbox|My sandbox]]
* [[/Nasal documentation proposal|Nasal documentation proposal]]

[[Category:Users]]

User:Red Leader

2021-02-28T12:59:52Z

Red Leader: Update my current status and edit wikitext formatting

__NOTOC__
{{User
|name = Red Leader
|location = United Kingdom
|interests =
* [http://www.flightgear.org/ FlightGear]
* {{Wikipedia|Military aircraft|noicon=1}}
* [http://www.lego.com/en-gb/ Lego]
|callsign =
* Red-Led
* RLTest1
* RLTest2
|favourite =
* [[Grumman F-14 Tomcat]]
* [[British Aerospace Sea Harrier]]
* [[Dassault Mirage 2000-5]]
* [[Saab JA-37 Viggen]]
}}

== My involvement with flight simulators ==
My involvement with flight simulators started when I got [http://www.ysflight.com/ YSFlight], another free flight simulator. Although it was great fun, it wasn't very realistic, so I wanted something better. After looking at {{wikipedia|Microsoft Flight Simulator X|noicon=1}} and {{Wikipedia|Combat Flight Simulator 3: Battle for Europe|Combat Flight Simulator|noicon=1}}, I found [https://www.flightgear.org/ FlightGear]. Since then I've wanted to improve FlightGear and make it better for the end-user.

In late August 2015, I became an administrator on the [[FlightGear Wiki]].

Since Autumn 2018, I have been essentially inactive within the community due to other commitments in my life. I do, however, intend to return to FlightGear one day, and I still keep a very dim view of things going on here. It is best to contact me via private message on the FlightGear forum ({{forum link|text=profile|type=member|u=17099}}); I should be fairly prompt in responding.

== Projects ==
=== Simulator ===
* [[British Aerospace Sea Harrier]] development. {{paused}}
* [[Scripted AI Objects]] development (with {{usr|5H1N0B1}}). {{paused}}
* Starting the [[Canvas HUD]] framework. {{not done}}

=== Wiki ===
* Documenting the [[Nasal]] {{abbr|API|Application Programming Interface}} (see my [[/Nasal documentation proposal|Nasal documentation proposal]]) {{paused}}

== Pages ==
* [[/Sandbox|My sandbox]]
* [[/Nasal documentation proposal|Nasal documentation proposal]]

[[Category:Users]]

Changelog 2020.3

2020-12-17T20:14:18Z

Red Leader: Grammar correction & apply :Template:Key press

{{changelogs|prev=2020.1|next=2022.1}}

Available in: [[Changelog_2020.3|English]], [[Zh/2020.3|Chinese]]<br />

Please help us translate into other languages!

----<noinclude>
[[Category:Undocumented templates]]
</noinclude>

The FlightGear development team is delighted to announce the v2020.3 LTS release of FlightGear, the free, open-source flight simulator. This is the second Long Term Support release for FlightGear, since the project changed to offering both Long Term Support releases, and more cutting-edge Preview releases. This release represents the culmination of two years of development effort by a worldwide group of volunteers, brought together by a shared ambition to create the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.

Major enhancements since the v2018.3 LTS include:
* a developer preview of the upcoming Compositor graphical rendering framework as a separate pre-built binary,
* enhancements to both the JSBSim and YASim flight dynamics models
* DDS texture caching to reduce load times
* faster loading and more memory efficient buildings
* improved aircraft carrier support

Additionally 30 completely new aircraft have been added to the official hangar, and a further 71 have received major updates.

Founded in 1997, FlightGear features more than 700 aircraft, a worldwide scenery database, a multiplayer environment, detailed sky modelling, a flexible and open aircraft modelling system, varied networking options, multiple display support, a powerful scripting language, and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute.

FlightGear - Fly Free!

----<noinclude>
[[Category:Undocumented templates]]
</noinclude>

== Launcher ==
* Addition of a welcome screen on first launch, providing helpful information to first time users.
* Aircraft can now be marked as Favourites, and filtered, making it easier to see find your favourite aircraft out of the hundreds available.
* The launcher now supports aircraft carriers, including selecting a carrier and setting a start position.
* {{key press|Ctrl|F}} shortcut for when you just want to Fly!
* Improved support for helipads and seaports, including detection of current aircraft type.
* Numerous bugfixes and stability improvements, in particular for the aircraft and addons tabs.

== Graphics ==
* To provide a developer preview, the [[Compositor]] renderer is included as part of this release. It provides a fully XML-configurable multi-pass rendering pipeline that is compatible with ALS and includes clustered shading.
* Support for DDS Texture Cache, improving loading times for texture files.
* Star visibility is configurable based on magnitude of star and atmospheric conditions.
* Use of non-directional point sprites as a fallback for drivers that do not support triangles of point sprites is now supported by setting <code>/rendering/triangle-directional-lights=false</code>.
* A new Tower AGL view has been added. This is similar to Tower View, except that it keeps both the aircraft and the ground immediately below the aircraft in view, zooming and panning smoothly as the aircraft moves. Good for viewing landings.
* Improved airport grass textures
* Implemented tidal movement for littoral areas.
* Updated regional material definitions for California, Asia, Northern Brazil, Iceland, Jan Mayen island.
* Active volcanoes - Katla, Eyjafjallajokull, Surtsey.
* Instanced-based random and OpenStreetMap buildings, improving performance and graphical quality significantly.
* Improvements to the Wingflex Shader.
* Users may enable/disable the pilot model from the View Options dialog.

== JSBSim ==
* Added the ability to set up the starter and acceleration times of a turbine (parameters <code><n1spinup></code>, <code><n2spinup></code>, <code><n1startrate></code>, <code><n2startrate></code>).
* The <code><integrator></code> filter can now be reset to 0.0 by setting its <code><trigger></code> property to a negative value.
* The integration scheme of the <code><integrator></code> filter can now be chosen among <code>rect</code> (Euler), <code>trap</code> (Trapezoidal), <code>ab2</code> (2nd order Adams-BashForth) and <code>ab3</code> (3rd order Adams-Bashforth)
* The following functions can now be used in <code><function></code>: <code>floor</code>, <code>ceil</code> and <code>fmod</code>. Their functionalities are the same than the corresponding C/C++ functions.
* <code><function></code> now checks the number of its arguments.
* New system component linear_actuator
* Export the fuel density to the property tree
* Added cyclic clipping for FCS components
* Added the ability to control the turbine engines spin down factor
* [Backward compatibility breakage] Gyros are now measuring rotation rates instead of rotational accelerations. Gyros that measure rotational accelerations do not exist in the real world.
* Output properties of flight control elements are no longer tied. This saves a lot of spurious warning messages and allows direct references of the same properties among several flight controls.
* Water vapor in the atmosphere is now managed through its mass fraction rather than its partial pressure. The former being the physical quantity that is conserved when pressure and temperature vary.
* Check that there are at least 3 contacts before trying to trim on ground.
* Added optional transmission of the simulation time for FG UDP interface
* The existence of the property that is used for table independent vars is now checked during execution rather than when the XML definition is parsed. This relaxes the order in which filters, table and more generally flight controls need to be declared in the XML definition files.
* Electric engines RPM is now exported in UDP sockets.
* The parameter <code><ignitionn2></code> now affects N2 rather than N1.
* A warning is now given when max < min in a <code><clipto></code> rather than throwing an exception
* Added the ability to log properties in a CSV file with the new fgfs executable argument <code>--jsbsim-output-directive-file</code>

== YASim ==
* Ground friction (stiction) changes
* Support for transonic flow effects.
* Control initial gear state directly by setting <code>/fdm/yasim/respect-external-gear-state=true</code>, rather then YASim settings this depending on whether the aircraft is in the air or on the ground.
* Electric engines are now supported.

== Weather and Environment ==
* Increased turbulence will be encountered near active volcanoes.
* Configurable METAR URL.
* METAR strings are decoded and displayed in a human-readable form in the weather dialog.

== Carriers ==
* Two new carrier-specific starting options are supported in the launcher: <code>carrier-takeoff</code> and <code>carrier-approach</code>.
* A new <code>--carrier-position</code> command-line argument has been added. This can be used to select the aircraft start position on an aircraft carrier. Either a catapult (e.g. <code>cat-1</code>), a parking position (e.g. <code>park-1</code>), on final approach on the FLOLS (<code>flols</code>) or abeam the carrier (<code>abeam</code>).
* MPCarrier can now be detected by the GUI even if not available on startup. To enable this feature set <code>/sim/mp-carriers/auto-attach=true</code>.

== AI ==
* New fgcommands <code>add-aiobject</code> and <code>remove-aiobject</code> for adding/removing objects to the AI subsystem.
* New AI aircraft, including 747 Freighter, CRJ900, SR-71, Saab 340.
* Numerous updates to AI traffic schedules and airline liveries.
* Space Shuttle TAEM and approach at KEDW scenario.
* Accurate Britten-Norman Islander performance data, from an Islander pilot.

== Multiplayer ==
* Connection to VATSIM via swift is now available via the GUI.
* FGCom now supports both COM1 and COM2, as well as volume settings.
* The views defined by the user's aircraft (Pilot view, Helicopter view, Tower view etc) can now be used with multiplayer aircraft. Viewing a particular multiplayer aircraft is done by clicking in the Pilot List dialogue's "view' column (see the "Multiplayer/Pilot List" menu).
* <code>--disable-hold-short</code> option which allows the user to force a start on the runway when multiplayer is enabled. This option should be used with caution - it can give other pilots and ATC a nasty fright to find an aircraft materialize on the runway!
* Support for recording multiplayer data

== Nasal Scripting ==
* Configurable load order for core Nasal modules.
* Improvements and bug fixes to Emesary, the messaging interface.
* Improvements to the core libraries.
* Garbage collection improvements to reduce frame stuttering
* Re-loadable Nasal modules
* Canvas EFIS framework
* New methods in Canvas Image to set colors of pixels in the image.

== Aircraft ==
* FG1000 Glass Panel improvements include user-configurable VFR transponder codes, volume controls, new fascia, UI is now resizeable, support for custom SVG files (e.g. for a G500). The FG1000 is now available on the Cessna 182T, J3 Cub, Diamond DA40.
* Improved glider vario instrument.
* New Aircraft:
** Airbus A320 - airliner
** Alisport Silent2Electro - glider with electric sustainer motor
** Bombardier Q400 DHC8-402 - shorthaul turboprop airliner
** Breguet Atlantic BR 1150 - long-range maritime patrol aircraft
** Cessna 140 - GA aircraft
** Cessna 208B Caravan - short range passenger, freighter and utility aircraft
** Cirrus SR22T - GA aircraft
** Diamond DA40 NG - GA aircraft, including FG1000 glass panel cockpit
** Diamond DA62 Twinstar- Twin engine GA aircraft
** Diamond HK36 Super Dimona - motorglider
** Dornier DO 28 Skyservant - Twin engine STOL utility aircraft
** Douglas TBD Devastator - WWII Torpedo bomber
** Draco Wilga - turboprop taildragger bush plane
** Fokker T.V - twin engine bomber
** Glasfluegel H201B Standard Libelle - glider
** Grumman F11-Tiger - carrier-based fighter
** Grumman HU-16A Albatross - twin engine amphibian
** Petliakov PE-8 (Ant-42/TB-7) - WWII bomber
** Piper PA28-161 Warrior II - GA aircraft
** Pipistrel Alpha Electro - electric training aircraft
** Pipistrel Taurus Electro G2.5 - glider with electric sustainer motor
** Rolladen Schneider LS8sc neo - standard glider with electric sustainer motor
** Robin DR400 Ecoflyer - GA Aircraft
** Scheibe Bergfalke II/55 - training glider
** Schempp-Hirth Arcus S - high performance glider
** Schleicher Ka6(CR) "Rhoensegler" - training glider
** SEPECAT Jaguar GR.1 - jet attack aircraft
** SUMPAC - Human powered airplane
** Supermarine Swift - jet fighter
** Yak 52 - training aircraft
* Major updates to over 70 aircraft. Including 737-100, 737-300, 777, A-26-Invader, AR-234, ASG29, ASK13, ASK21, Aero-Commander, Aichi-D3A, B-17, B-24-Liberator, B-25, Bombardier-415, CH750STOL, CRJ700-family, Cessna-208-Caravan, Cessna Citation II, Cessna-L19, Cirrus-SR22, Concorde, DO-228, DO-335, Diamond-Da40, Diamond-Da42, Dragonfly, Embraer-ERJ-145, F-15, Fairchild-Metroliner, Falcon-50, Fokker-S-11, Fw200, H4-Hercules, Harrier-GR3, Horten-Ho-IX, Hughes-XF11, J3Cub, JA37, JAS39-Gripen, Jaguar, LS4, Lancair-235, Lionceau, Lockheed-NF104A, Lockheed-P38, ME-262, Mirage-2000, MirageIV, Northrop-xb35, PC-12, Piaggio-P166, Piper-PA-28, Potez-630, R44, Ryan-Navion, SIAI-Marchetti-SF.260, Socata-ST10, SpaceShuttle, Starship, Tecnam-P2006T, UH-1, Yak-18T, Zlin-50lx, an24b, bluebird, c182s, dhc1, f-14b, f16.

== Miscellaneous ==
* Updated Chinese, Dutch, French, German, Italian, Polish and Slovak translations.
* Map dialog displays heliports and allows configurable cursor key panning
* Faster Terrasync: Download a tarball of airport information on first start and only check for updates every 24 hours rather than every simulator run.
* GPS fly-by mode
* Sentry.io integration to provide centralized crash reporting.
* Change screenshot filename to have date and time
* New thread safe particle manager -- should reduce random crashes around particles.

=Updates since 2020.1=
Changes since the 2020.1 preview release include:
* Various launcher improvements including a Welcome screen and a keyboard shortcut (Ctrl+F) to Fly!
* Improved regional definitions for California, Iceland and Northern Brazil and better grass textures.
* Implemented tidal movement for littoral areas.
* New AI model for the 747 Freighter, and numerous AI livery and traffic updates.
* Updates to the FG1000 glass panel display including configurable VFR transponder codes, volume controls, a new fascia, resizeable UI and support for custom SVG files.
* A hangar full of new aircraft: HU-16A-Albatross, LS8, Embraer-ERJ-145, Cessna 208B Caravan, PZL 104 wilga 2000 Draco, Scheibe Bergfalke, Taurus, f16, Dornier Do 28 Skyservant, Petliakov Pe 8 (Ant 42/DB 7), Grumman F.11 Tiger
* Updates to a large number of aircraft including CRJ700, Dragonfly, Mirage 2000, Jaguar GR1, H4 Hercules, JA37, Supermarine Swift, A320, Cirrus-SR22, Cessna Citation, J3Cub
* Updated Chinese, Dutch, French, German, Italian, Polish and Slovak translations.
* Faster Terrasync: Download a tarball of airport information on first start and only check for updates every 24 hours rather than every simulator run.
* GPS fly-by mode
* Sentry.io integration to provide centralized crash reporting.
* New thread safe particle manager -- should reduce random crashes around particles.

[[Category:FlightGear changelogs‎]]
[[Zh:2020.3]]

User:Red Leader

2019-02-01T07:35:47Z

Red Leader: Status update

__NOTOC__{{User
|name = Red Leader
|location = United Kingdom
|interests =
* [http://www.flightgear.org/ FlightGear]
* {{Wikipedia|Military aircraft|noicon=1}}
* [http://www.lego.com/en-gb/ Lego]
|callsign =
* Red-Led
* RLTest1
* RLTest2
|favourite =
* [[Grumman F-14 Tomcat]]
* [[British Aerospace Sea Harrier]]
* [[Dassault Mirage 2000-5]]
* [[Saab JA-37 Viggen]]
}}

== My involvement with flight simulators ==
My involvement with flight simulators started when I got [http://www.ysflight.com/ YSFlight], another free flight simulator. Although it was great fun, it wasn't very realistic, so I wanted something better. After looking at [http://www.microsoft.com/games/fsinsider/ Microsoft Flight Simulator] and {{Wikipedia|Combat_Flight_Simulator_3:_Battle_for_Europe|Combat Flight Simulator|noicon=1}}, I found [http://www.flightgear.org/ FlightGear]. Since then I've wanted to improve FlightGear and make it better for the end user.

In late August 2015, I became an administrator on the [[FlightGear Wiki]].

As of January 2019, I am almost inactive on FlightGear due to lack of free time. I don't intend to stop, however, and hopefully will become more active again during Summer 2019.

== Projects ==
=== Simulator ===
* [[British Aerospace Sea Harrier]] development. {{paused}}
* [[Scripted AI Objects]] development (with {{usr|5H1N0B1}}). {{paused}}
* Starting the [[Canvas HUD]] framework. {{not done}}

=== Wiki ===
* Documenting the [[Nasal]] {{abbr|API|Application Programming Interface}} (see my [[User:Red_Leader/Nasal_documentation_proposal|Nasal documentation proposal]]) {{paused}}

== Pages ==
* [[User:Red_Leader/Sandbox|My sandbox]]
* [[User:Red_Leader/Nasal_documentation_proposal|Nasal documentation proposal]]

What is Nasal

2018-12-31T13:04:33Z

Red Leader: https://plausible.org/nasal/ is now a dead link (looks like the server was reinstalled). Provide reference link to the last save from the Wayback Machine

{{Template:Nasal Navigation}}

[[FlightGear]] offers a very powerful functional '''scripting language''' called '''Nasal'''<ref>https://web.archive.org/web/20160817183633/https://plausible.org/nasal/</ref>, which supports reading and writing of internal [[Property Tree Intro|FlightGear properties]], accessing internal data via extension functions, creating GUI dialogs and much more. While "Nasal" may seem like a weird name, just read it as "FlightGear scripting".

== Not another scripting language ==
Nasal uses some of the concepts of ECMA/JavaScript, Python and Perl and implements a simple but complete way of Object Oriented Programming (OOP), Nasal uses an internal garbage collector so that no manual memory management is required by the programmer.

People familiar with other programming languages, and scripting languages like JavaScript in particular, are usually able to learn Nasal rather quickly. FlightGear provides a rich library of simulation-specific and general-purpose functions that can be accessed by Nasal scripts.

Nasal code can be run by [[aircraft]] configuration files, and it can be embedded in various [[XML]] files (dialog files, animation files, bindings for [[joystick]]s, keyboard and cockpit controls, and even in [[Howto:Nasal in scenery object XML files|scenery objects]]). Nasal is platform independent and designed to be thread safe.

{{Template:Appendix}}

User:Red Leader/Git

2018-10-27T16:56:04Z

Red Leader: Add Heading setup

Intended to be a collection of notes on '''getting up and running with Git''' with the eventual aim of producing an article.

== Setup ==
* Download Git for https://git-scm.com/downloads.
* Install Git

British Aerospace Sea Harrier/info

2018-08-23T08:16:32Z

Red Leader: Change download link

<includeonly>{{infobox aircraft
| name = BAe Sea Harrier FA2
| image = External-view-Sea-Harrier.png
| alt = External view of the Sea Harrier
| image2 = Cockpit-Sea-Harrier.png
| alt2 = Cockpit of the Sea Harrier
| type = VTOL aircraft/Military aircraft/Fighter aircraft/Carrier-based aircraft/Attack aircraft
| config = High wing aircraft/Retractable gear aircraft
| propulsion = Single-engine jet
| manufacturer = British Aerospace
| author1 = Andy Ross
| author2 = Steve Havlir
| author3 = {{usr|Red Leader}} (present)
| fdm = YASim
| fgname = harrier
| status-fdm = 2
| status-systems = 3
| status-cockpit = 3
| status-model = 4
| ready = airrefuel/bombable/rembrandt/canvas/checklist/tutorials
| download = https://www.dropbox.com/s/8n9oig9v2xw7b75/harrier%20v2.5.0.zip?dl=0
| forumtid = 24711
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[British Aerospace Sea Harrier]].
[[Category:Aircraft infobox documentation]]
</noinclude>

British Aerospace Sea Harrier

2018-08-23T08:16:04Z

Red Leader: Change AI version & scenario link

{{:{{PAGENAME}}/info}}
The '''British Aerospace Sea Harrier''' (informally '''Shar''') is a naval short take-off and vertical-landing/vertical take-off and landing jet fighter, reconnaissance and attack aircraft, and a development of the [[Hawker Siddeley Harrier GR1|Hawker Siddeley Harrier]]. It first entered service with the Royal Navy in April 1980 as the Sea Harrier {{abbr|FRS1|Fighter, Reconnaissance, Strike, Mk. 1}} and became informally known as the "Shar" ('''S'''ea '''Har'''rier). Unusual in an era in which most naval and land-based air superiority fighters were large and supersonic, the principal role of the subsonic Sea Harrier was to provide air defence of the fleet from Royal Navy aircraft carriers. Retired in 2006, today there is only one airworthy Sea Harrier in the world. XZ439, a restored former Royal Navy Sea Harrier FA2, is operated in the United States by Art Nalls, a former USMC pilot ([http://www.nallsaviation.com/ website]).

The version currently modeled in [[FlightGear]] is the Sea Harrier {{abbr|FA2|Fighter, Attack, Mk. 2}}, an improved version with the {{wikipedia|Blue Vixen}} radar and the {{wikipedia|AIM-120 AMRAAM}} missile.

== Keyboard controls ==
{| class="keytable"
! Key
! Function
|-
|{{key press|m}}
|Vector thrust upwards
|-
|{{key press|Shift|m}}
|Vector thrust downwards
|-
|{{key press|h}}
|Toggle HUD on/off
|-
|{{key press|j}}
|Decrease air brake
|-
|{{key press|k}}
|Increase air brake
|-
|{{key press|e}}
|Release ordinance/fire gun
|-
|{{key press|w}}
|Cycle stick mode selector
|-
|{{key press|Ctrl|w}}
|Toggle station arming
|-
|{{key press|Ctrl|f}}
|Release countermeasure
|-
|{{key press|1}}/{{key press|2}}/{{key press|3}}/{{key press|4}}/{{key press|5}}/{{key press|6}}/{{key press|7}}
|Select station
|-
|{{key press|Shift|<nowiki>]</nowiki>}}
|Autostart
|-
|{{key press|Shift|c}}
|Toggle canopy
|-
|{{key press|n}}
|Next target
|-
|{{key press|Ctrl|n}}
|Previous target
|}

== Features ==
* A fully working weapons system, including realistic stores and gun behaviour
* Semi-realistic startup
* [[Bombable]] support
* [[Rembrandt]] support
* Full electrical system, including switchable instruments
* [[Aircraft Checklists|Checklists]] and [[Tutorials]] support
* Realistic [[autopilot]]
* Modeled limits
* [[Canvas]] {{abbr|HDD|Head-down Display}}
* Flare/chaff system
* {{abbr|CCIP|Constantly-Computed Impact Point}} bombing system
* {{abbr|RWR|Radar Warning Receiver}}
* Bombable-compatible AI aircraft
* Fuel System
* [[Instant Replay]] support
* Custom failures based on the new [[A Failure Management Framework for FlightGear|custom failures framework]].
* Backwards compatibility (tested on both FG 3.2 and 2.12.0)
* [[Howto:Implement pushback|Pushback]] truck

== Changes for the latest release (2.5.0) ==
* Nasal code style cleaned up
* All XML files encoded in UTF-8 w/o BOM; encoding added in headers
* Throttle and thrust vector levers fixed.
* Canvas HDD properly integrated
* Start Canvas-based radar
* All paths are now relative
* Some changes to the cockpit
* Some more bugfixes
* New splash texture
* License changed back to GNU GPL v2

== Development ==
<big>Last updated 23 June 2016</big>

=== For next release (2.6.0) ===
* Update docs
* Make new FDM
* Unify radar

=== Cockpit ===
* More detailed cockpit (more info required)

=== Model ===
* Better, more detailed model
* British 1,000lb bomb

=== Systems ===
* New radar (possibly using [[Canvas Radar]])
* Autoland system
* Realistic {{abbr|SMS|Stores Management System}}

=== FDM ===
* More realistic (data needed)

=== General ===
* New [[Canvas Widgets|Canvas dialogs]]

== Issues ==
=== FDM ===
* Aircraft swings on the ground.

== See also ==
* [https://forum.flightgear.org/viewtopic.php?f=4&t=24711 Forum topic]
* [https://www.dropbox.com/s/kot5l0x8oi9k5oy/AI%20harrier%20%26%20scenario.zip?dl=0 Bombable-compatible AI aircraft and scenario]

=== External links ===
* {{wikipedia|British Aerospace Sea Harrier|noicon=1}} (Wikipedia)
* [http://www.naval-technology.com/projects/fa2-sea-harrier/ Sea Harrier] (naval-technology.com)

{{British Aerospace}}

{{air-to-air refueling}}

User:Red Leader/Git

2018-08-22T18:05:08Z

Red Leader: Start placeholder page

Intended to be a collection of notes on '''getting up and running with Git''' with the eventual aim of producing an article.

Nasal library/clipboard

2018-04-27T13:05:19Z

Red Leader: Doc setText()

{{Nasal Navigation|nocat=1}}
This page contains documentation for the '''<code>clipboard</code> namespace''' in [[Nasal]]. This namespace provides functions for working with text stored in the {{wikipedia|Clipboard (computing)|clipboard}}. The <code>clipboard</code> namespace is implemented in {{flightgear source|src/Scripting/NasalClipboard.cxx|pre=flightgear}}. There are also several files in the <tt>''Scripting''</tt> folder that implement the backend depending on the OS.

{{tip|Copy & paste the examples into your [[Nasal Console]] and execute them to see what they do.|width=70%}}

== Functions ==
=== getText() ===
{{Nasal doc
|syntax = clipboard.getText([type]);
|source = {{flightgear source|src/Scripting/NasalClipboard.cxx|l=69|t=Source}}
|text = Returns the contents of the clipboard as a string.
|param1 = type
|param1text = Optional argument that specifies the source of the text. If <code>clipboard.CLIPBOARD</code> (the default) is given, the contents of the clipboard are returned. If <code>clipboard.SELECTION</code> is given, the contents of the selection buffer are given. Note that only X11 systems properly implement <code>clipboard.SELECTION</code>, but this argument may still be used with <code>[[#setText()|setText()]]</code> (see example 2).
|example1 = var text = clipboard.getText(); # make sure you copy some text first
print("'", text, "'");
|example2 = clipboard.setText("Demo", clipboard.SELECTION);
var text = clipboard.getText(clipboard.SELECTION);
print("'", text, "'"); # prints 'Demo'
}}

=== setText() ===
{{Nasal doc
|syntax = clipboard.setText(text[, type]);
|source = {{flightgear source|src/Scripting/NasalClipboard.cxx|l=54|t=Source}}
|text = Sets the contents of the clipboard. If the operation is successful, 1 (true) is returned, otherwise 0 (false) is returned.
|param1 = text
|param1text = A string that will be put into the clipboard.
|param2 = type
|param2text = Optional argument that specifies into which part of the clipboard the text should be put. If <code>clipboard.CLIPBOARD</code> (the default) is given, it will go to the normal clipboard. If <code>clipboard.SELECTION</code> is given, the text will be added to the selection buffer. Note that only X11 systems properly implement <code>clipboard.SELECTION</code>, but this argument may still be used with <code>[[#setText()|setText()]]</code> (see example 2).
|example1 = clipboard.setText("Demo");
print("'", clipboard.getText(), "'"); # prints 'Demo'
|example2 = clipboard.setText("Demo", clipboard.SELECTION);
print("'", clipboard.getText(clipboard.SELECTION), "'"); # prints 'Demo'
}}

== Constants ==
=== CLIPBOARD ===

=== SELECTION ===

{{Nasal namespaces}}

Nasal library/clipboard

2018-04-27T08:07:48Z

Red Leader: /* getText() */ Source

Nasal library/clipboard

2018-04-27T07:16:00Z

Red Leader: Change Template:Flightgear file to Template:Flightgear source

Nasal library/clipboard

2018-04-27T06:48:15Z

Red Leader: /* getText() */ Link style

Nasal library/clipboard

2018-04-26T18:59:52Z

Red Leader: /* getText() */

Nasal library/clipboard

2018-04-26T18:59:29Z

Red Leader:

Nasal library/clipboard

2018-04-26T18:57:09Z

Red Leader: /* getText() */ Doc

Nasal library/clipboard

2018-04-26T18:38:17Z

Red Leader: Grammar

Template:Nasal Navigation

2018-04-26T09:43:35Z

Red Leader: Update

<noinclude>{{Informative template|1=
Navigation box for core [[Nasal]] articles.

== Usage ==
Put this at the top of the article:
{{obr}}'''Nasal Navigation'''{{cbr}}

}}

[[Category:Navigation templates]]

</noinclude><includeonly>{{nocat|{{{nocat|}}}|Nasal}}</includeonly>{{forum|30|Nasal Scripting}}
{{sidebar with collapsible headers
| topimage = [[File:Nasallogo3.png]]
| name = Nasal Navigation
| title = [[Nasal|Nasal scripting]]
| contentstyle = text-align: left;
| state = collapsed

| content1 =
* [[What is Nasal]]?
* [[Nasal success stories|Success stories]]
* [[Nasal FAQ]]
* [[Nasal Snippets]]
* [[Howto:Syntax highlighting for Nasal]]

| heading2 = Tools and utilities
| content2style = text-align: center;
| content2 = [[Nasal Console|Console]] • [[Interactive Nasal Console|REPL Console]] • [[Nasal Browser|Browser]]

| heading3 = Getting started
| content3 =
* [[Nasal Best Practices]]
* [[Nasal for C++ programmers]]
* [[Creating new Nasal scripts]]
* [[Nasal Hello World]]
* [[Howto:Create a new Nasal module]]
* [[Using Nasal functions]]
* [[Nasal Variables]]
* [[Nasal Namespaces]]
* [[Howto:Understand Namespaces and Methods|Namespace and Methods]]
* [[Nasal Namespaces in-depth]]
* [[Nasal Conditionals]]
* [[Nasal Loops]]
* [[Numbers in Nasal]]
* [[Nasal Operators]]
* [[Howto:Use vectors and foreach loops to write shorter code]]
* [[Howto:Start using vectors and hashes in Nasal]]
* [[Nasal library]] ([[Nasal library#Core library functions|core]]/[[Nasal library#Extension functions|extension]] functions)
** [[Nasal library/clipboard|<code>clipboard</code> namespace]]
** [[Nasal library/debug|<code>debug</code> namespace]]
** [[Nasal library/geo|<code>geo</code> namespace]]
** [[Nasal library/io|<code>io</code> namespace]]
** [[Nasal library/math|<code>math</code> namespace]]
** [[Nasal library/os.path|<code>os.path</code> namespace]]
** [[Nasal library/props|<code>props</code> namespace]]
* [[Nasal String Manipulation]]
* [[Howto:Write a parser in Nasal]]
* [[Nasal File I/O]]
* [[Nasal Flightplan]]
* [[Object oriented programming in Nasal|OOP Introduction]]
* [[Object Oriented Programming with Nasal]]
* [[Nasal Callbacks Explained]]
* [[Exception handling with Nasal]]
* [[Using listeners and signals with Nasal]]
* [[Developing and debugging Nasal code]]

| heading4 = Advanced Tutorials
| content4 =
* [[Caching Nasal function calls]]
* [[Nasal Unit Testing Framework]] (WIP)
* [[Nasal Meta-Programming]]
* [[A GPX flight logger in Nasal]]
* [[Multiplayer scripting in Nasal]]
* [[Howto:Making HTTP Requests from Nasal]]
* [[Howto:Transmit properties over MP]]
* [[Howto:Terrain sampling in Nasal]]
* [[Howto:Create a new system in Nasal]]
* [[Howto:Load a Nasal file at runtime]]
* [[Howto:Control the route manager in Nasal]]
* [[Howto:Get a number of elevation offsets for a number of objects]]
* [[Howto:Nasal in scenery object XML files]]
* [[Howto:Create animation XML files from Nasal]]
* [[Howto:Port I/O from Nasal]]
* [[Howto:Continuation-passing style programming in Nasal]]
* [[Howto:Start worker threads using listeners in Nasal]]
* [[Howto:Developing a DSL interpreter in Nasal]]
* [[Howto:Nasal Metaprogramming]]
* [[Nasal/JavaScript Subset]]

}}
{{Nasal Internals}}

User:Red Leader/Nasal documentation proposal

2018-04-26T09:42:46Z

Red Leader: Update

Proposal for the documentation of the [[Nasal]] API.
__TOC__
== Documentation pages ==
{| class="wikitable"
|+ Nasal library {{Done}}
! Old page(s) !! New page
|-
|
* [[Nasal library functions]] ([http://wiki.flightgear.org/index.php?title=Nasal_library_functions&oldid=93458 perm])
* [[List of Nasal extension functions]] ([http://wiki.flightgear.org/index.php?title=List_of_Nasal_extension_functions&oldid=72953 perm])
|| [[Nasal library]]
|}

Form: <code><nowiki>[[Nasal library/<namespace>]]</nowiki></code>
{| class="wikitable"
|+ Nasal namespaces {{progressbar|30}}
! Namespace !! New page !! Progress
|-
| <code>'''aircraft'''</code>
| {{N/a|Not started|rowspan{{=}}"2" colspan{{=}}"2"}}
|-
| <code>'''bits'''</code>
|-
| <code>'''clipboard'''</code> || [[Nasal library/debug]] || {{progressbar|10}}
|-
| <code>'''debug'''</code> || [[Nasal library/debug]] || {{done}}
|-
| <code>'''geo'''</code> || [[Nasal library/geo]] || {{done}}
|-
| <code>'''gui'''</code>
| {{N/a|Not started|rowspan{{=}}"2" colspan{{=}}"2"}}
|-
| <code>'''http'''</code>
|-
| <code>'''io'''</code> || [[Nasal library/io]] || {{done}}
|-
| <code>'''math'''</code> || [[Nasal library/math]] || {{done}}
|-
| <code>'''mp_broadcast'''</code>
| {{N/a|Not started|colspan{{=}}"2"}}
|-
| <code>'''os[.path]'''</code> || [[Nasal library/os.path]] || {{done}}
|-
| <code>'''positioned'''</code>
| {{N/a|Not started|colspan{{=}}"2"}}
|-
| <code>'''props'''</code> || [[Nasal library/props‎‎]] || {{done}}
|-
| <code>'''scenery'''</code>
| {{N/a|Not started|rowspan{{=}}"7" colspan{{=}}"2"}}
|-
| <code>'''screen'''</code>
|-
| <code>'''std'''</code> (current page: [[Vector]])
|-
| <code>'''string'''</code>
|-
| <code>'''thread'''</code>
|-
| <code>'''utf8'''</code>
|-
| <code>'''view'''</code>
|}

{| class="wikitable"
|+ Basic Nasal scripting {{Not done}}
! Subject !! Current page(s) !! New page
|-
| Hashes
|
* [[Howto:Start using vectors and hashes in Nasal]]
* [[Object Oriented Programming with Nasal]]
* [[Object oriented programming in Nasal]]
* [[Howto:Understand Namespaces and Methods]]
* [[Nasal Namespaces in-depth]]
| [[Hashes in Nasal]]
|-
| Namespaces
|
* [[Howto:Understand Namespaces and Methods]]
* [[Nasal Namespaces in-depth]]
* [[Nasal Namespaces]]
| [[Namespaces in Nasal]]
|-
| Numbers || {{N/a|Very little}} || [[Numbers in Nasal]]
|-
| Vectors
|
* [[Nasal Variables]]
* [[Howto:Use vectors and foreach loops to write shorter code]]
* [[Howto:Start using vectors and hashes in Nasal]]
| [[Vectors in Nasal]]
|-
| Strings || [[Nasal Hello World]] || [[Strings in Nasal]]
|-
| Conditionals || [[Nasal Conditionals]] || [[Conditionals in Nasal]]
|-
| Operators || [[Nasal Operators]] || [[Operators in Nasal]]
|-
| Loops || [[Nasal Loops]] || [[Loops in Nasal]]
|-
| Functions || [[Using Nasal functions]] || [[Functions in Nasal]]
|-
| Variables || [[Nasal Variables]] || [[Variables in Nasal]]
|}

{| class="wikitable"
|+ Advanced Nasal scripting {{Not done}}
! What? !! Current page(s) !! New page
|-
| Vector slicing || [[Nasal Variables]] || [[Vectors in Nasal]]
|-
| OOP
|
* [[Object Oriented Programming with Nasal]]
* [[Object oriented programming in Nasal]]
| [[Object orientated programming in Nasal]]
|}

{| class="wikitable"
|+ [[Canvas]] {{Abbr|API|Application Programming Interface}} {{Not done}}
! What? !! Current page(s)
|-
| Canvas Element || [[Canvas Element]]
|-
| Canvas Image || [[Canvas Image]]
|-
| Canvas Path || [[Canvas Path]]
|-
| Canvas Map ||
* [[Canvas Map API]] {{FG ver|< 3.0}}
* [[Canvas MapStructure]] {{FG ver|3.0+}}
|-
| Event handling || [[Canvas Event Handling]]
|-
! colspan="2" | [[Canvas GUI]]
|-
| Layout system || [[Canvas Layout System]]
|-
| Widgets
|
* [[Canvas Widget Matrix]]
* [[Canvas GUI]]
* [[Howto:Creating a Canvas GUI Widget]]
|-
| Canvas MessageBox || [[Canvas MessageBox]]
|}

== Navbox ==
{{forum|30|Nasal}}
{{sidebar with collapsible headers
| topimage = [[File:Nasallogo3.png]]
| name = Nasal Navigation
| title = [[Nasal|Nasal scripting]]
| contentstyle = text-align: left;
| state = collapsed

| content1style = text-align: center;
| content1 = [[Nasal success stories|Success stories]] • [[Nasal FAQ|FAQ]]

| heading2 = Tools and utilities
| content2style = text-align: center;
| content2 = [[Nasal Console|Console]] • [[Interactive Nasal Console|REPL Console]] • [[Nasal Browser|Browser]] • [[Howto:Syntax highlighting for Nasal|Syntax highlighting]]

| heading3 = Getting started
| content3 =
* [[Nasal syntax overview|Syntax overview]]
* [[Writing Nasal scripts]]
* [[Nasal Snippets]]
* [[Developing and debugging Nasal code]]

| heading4 = Basic Scripting
| content4style = text-align: center;
| content4 = [[Hashes in Nasal|Hashes]] • [[Variables in Nasal|Variables]] • [[Operators in Nasal|Operators]] • [[Functions in Nasal|Functions]] • [[Namespaces in Nasal|Namespaces]] • [[Strings in Nasal|Strings]] • [[Vectors in Nasal|Vectors]] • [[Conditionals in Nasal|Conditionals]] • [[Numbers in Nasal|Numbers]] • [[Loops in Nasal|Loops]]

| heading5 = Advanced Scripting
| content5 =
* [[Object orientated programming in Nasal|Object orientated programming]]
* [[Nasal Flightplan]]
* [[Callbacks in Nasal]]
* [[Exception handling with Nasal]]
* [[Using listeners and signals with Nasal]]
* [[Caching Nasal function calls]]
* [[Nasal Unit Testing Framework]] (WIP)
* [[Nasal Meta-Programming]]
* [[A GPX flight logger in Nasal]]
* [[Multiplayer scripting in Nasal]]
| heading6 = Howtos
| content6 =
* [[Howto:Write a parser in Nasal]]
* [[Howto:Making HTTP Requests from Nasal]]
* [[Howto:Transmit properties over MP]]
* [[Howto:Terrain sampling in Nasal]]
* [[Howto:Create a new system in Nasal]]
* [[Howto:Load a Nasal file at runtime]]
* [[Howto:Control the route manager in Nasal]]
* [[Howto:Get a number of elevation offsets for a number of objects]]
* [[Howto:Nasal in scenery object XML files]]
* [[Howto:Create animation XML files from Nasal]]
* [[Howto:Port I/O from Nasal]]
* [[Howto:Continuation-passing style programming in Nasal]]
* [[Howto:Start worker threads using listeners in Nasal]]
* [[Howto:Developing a DSL interpreter in Nasal]]
* [[Howto:Nasal Metaprogramming]]
* [[Nasal/JavaScript Subset]]
| heading7 = Reference
| content7 =
* [[Nasal library]] ([[Nasal library#Core library functions|core]]/[[Nasal library#Extension functions|extension]] functions)
** [[Nasal library/geo|<code>geo</code> namespace]]
** [[Nasal library/io|<code>io</code> namespace]]
** [[Nasal library/math|<code>math</code> namespace]]
** [[Nasal library/props|<code>props</code> namespace]]
* [[Nasal String Manipulation]]
}}
{{Nasal Internals}}
{{-}}

== Misc ==
* Merge [[Nasal scripting language]] and [[What is Nasal]] into [[Nasal]]

[[Category:Nasal namespace documentation]]

Nasal library/clipboard

2018-04-26T08:19:38Z

Red Leader: /* CLIPBAORD */ Spelling

User:Red Leader/Nasal documentation proposal

2018-04-26T08:19:18Z

Red Leader: Add category

Proposal for the documentation of the [[Nasal]] API.
__TOC__
== Documentation pages ==
{| class="wikitable"
|+ Nasal library {{Done}}
! Old page(s) !! New page
|-
|
* [[Nasal library functions]] ([http://wiki.flightgear.org/index.php?title=Nasal_library_functions&oldid=93458 perm])
* [[List of Nasal extension functions]] ([http://wiki.flightgear.org/index.php?title=List_of_Nasal_extension_functions&oldid=72953 perm])
|| [[Nasal library]]
|}

Form: <code><nowiki>[[Nasal library/<namespace>]]</nowiki></code>
{| class="wikitable"
|+ Nasal namespaces {{progressbar|30}}
! Namespace !! New page !! Progress
|-
| <code>'''aircraft'''</code>
| {{N/a|Not started|rowspan{{=}}"3" colspan{{=}}"2"}}
|-
| <code>'''bits'''</code>
|-
| <code>'''clipboard'''</code>
|-
| <code>'''debug'''</code> || [[Nasal library/debug]] || {{done}}
|-
| <code>'''geo'''</code> || [[Nasal library/geo]] || {{done}}
|-
| <code>'''gui'''</code>
| {{N/a|Not started|rowspan{{=}}"2" colspan{{=}}"2"}}
|-
| <code>'''http'''</code>
|-
| <code>'''io'''</code> || [[Nasal library/io]] || {{done}}
|-
| <code>'''math'''</code> || [[Nasal library/math]] || {{done}}
|-
| <code>'''mp_broadcast'''</code>
| {{N/a|Not started|colspan{{=}}"2"}}
|-
| <code>'''os[.path]'''</code> || [[Nasal library/os.path]] || {{done}}
|-
| <code>'''positioned'''</code>
| {{N/a|Not started|colspan{{=}}"2"}}
|-
| <code>'''props'''</code> || [[Nasal library/props‎‎]] || {{done}}
|-
| <code>'''scenery'''</code>
| {{N/a|Not started|rowspan{{=}}"7" colspan{{=}}"2"}}
|-
| <code>'''screen'''</code>
|-
| <code>'''std'''</code> (current page: [[Vector]])
|-
| <code>'''string'''</code>
|-
| <code>'''thread'''</code>
|-
| <code>'''utf8'''</code>
|-
| <code>'''view'''</code>
|}

{| class="wikitable"
|+ Basic Nasal scripting {{Not done}}
! Subject !! Current page(s) !! New page
|-
| Hashes
|
* [[Howto:Start using vectors and hashes in Nasal]]
* [[Object Oriented Programming with Nasal]]
* [[Object oriented programming in Nasal]]
* [[Howto:Understand Namespaces and Methods]]
* [[Nasal Namespaces in-depth]]
| [[Hashes in Nasal]]
|-
| Namespaces
|
* [[Howto:Understand Namespaces and Methods]]
* [[Nasal Namespaces in-depth]]
* [[Nasal Namespaces]]
| [[Namespaces in Nasal]]
|-
| Numbers || {{N/a|Very little}} || [[Numbers in Nasal]]
|-
| Vectors
|
* [[Nasal Variables]]
* [[Howto:Use vectors and foreach loops to write shorter code]]
* [[Howto:Start using vectors and hashes in Nasal]]
| [[Vectors in Nasal]]
|-
| Strings || [[Nasal Hello World]] || [[Strings in Nasal]]
|-
| Conditionals || [[Nasal Conditionals]] || [[Conditionals in Nasal]]
|-
| Operators || [[Nasal Operators]] || [[Operators in Nasal]]
|-
| Loops || [[Nasal Loops]] || [[Loops in Nasal]]
|-
| Functions || [[Using Nasal functions]] || [[Functions in Nasal]]
|-
| Variables || [[Nasal Variables]] || [[Variables in Nasal]]
|}

{| class="wikitable"
|+ Advanced Nasal scripting {{Not done}}
! What? !! Current page(s) !! New page
|-
| Vector slicing || [[Nasal Variables]] || [[Vectors in Nasal]]
|-
| OOP
|
* [[Object Oriented Programming with Nasal]]
* [[Object oriented programming in Nasal]]
| [[Object orientated programming in Nasal]]
|}

{| class="wikitable"
|+ [[Canvas]] {{Abbr|API|Application Programming Interface}} {{Not done}}
! What? !! Current page(s)
|-
| Canvas Element || [[Canvas Element]]
|-
| Canvas Image || [[Canvas Image]]
|-
| Canvas Path || [[Canvas Path]]
|-
| Canvas Map ||
* [[Canvas Map API]] {{FG ver|< 3.0}}
* [[Canvas MapStructure]] {{FG ver|3.0+}}
|-
| Event handling || [[Canvas Event Handling]]
|-
! colspan="2" | [[Canvas GUI]]
|-
| Layout system || [[Canvas Layout System]]
|-
| Widgets
|
* [[Canvas Widget Matrix]]
* [[Canvas GUI]]
* [[Howto:Creating a Canvas GUI Widget]]
|-
| Canvas MessageBox || [[Canvas MessageBox]]
|}

== Navbox ==
{{forum|30|Nasal}}
{{sidebar with collapsible headers
| topimage = [[File:Nasallogo3.png]]
| name = Nasal Navigation
| title = [[Nasal|Nasal scripting]]
| contentstyle = text-align: left;
| state = collapsed

| content1style = text-align: center;
| content1 = [[Nasal success stories|Success stories]] • [[Nasal FAQ|FAQ]]

| heading2 = Tools and utilities
| content2style = text-align: center;
| content2 = [[Nasal Console|Console]] • [[Interactive Nasal Console|REPL Console]] • [[Nasal Browser|Browser]] • [[Howto:Syntax highlighting for Nasal|Syntax highlighting]]

| heading3 = Getting started
| content3 =
* [[Nasal syntax overview|Syntax overview]]
* [[Writing Nasal scripts]]
* [[Nasal Snippets]]
* [[Developing and debugging Nasal code]]

| heading4 = Basic Scripting
| content4style = text-align: center;
| content4 = [[Hashes in Nasal|Hashes]] • [[Variables in Nasal|Variables]] • [[Operators in Nasal|Operators]] • [[Functions in Nasal|Functions]] • [[Namespaces in Nasal|Namespaces]] • [[Strings in Nasal|Strings]] • [[Vectors in Nasal|Vectors]] • [[Conditionals in Nasal|Conditionals]] • [[Numbers in Nasal|Numbers]] • [[Loops in Nasal|Loops]]

| heading5 = Advanced Scripting
| content5 =
* [[Object orientated programming in Nasal|Object orientated programming]]
* [[Nasal Flightplan]]
* [[Callbacks in Nasal]]
* [[Exception handling with Nasal]]
* [[Using listeners and signals with Nasal]]
* [[Caching Nasal function calls]]
* [[Nasal Unit Testing Framework]] (WIP)
* [[Nasal Meta-Programming]]
* [[A GPX flight logger in Nasal]]
* [[Multiplayer scripting in Nasal]]
| heading6 = Howtos
| content6 =
* [[Howto:Write a parser in Nasal]]
* [[Howto:Making HTTP Requests from Nasal]]
* [[Howto:Transmit properties over MP]]
* [[Howto:Terrain sampling in Nasal]]
* [[Howto:Create a new system in Nasal]]
* [[Howto:Load a Nasal file at runtime]]
* [[Howto:Control the route manager in Nasal]]
* [[Howto:Get a number of elevation offsets for a number of objects]]
* [[Howto:Nasal in scenery object XML files]]
* [[Howto:Create animation XML files from Nasal]]
* [[Howto:Port I/O from Nasal]]
* [[Howto:Continuation-passing style programming in Nasal]]
* [[Howto:Start worker threads using listeners in Nasal]]
* [[Howto:Developing a DSL interpreter in Nasal]]
* [[Howto:Nasal Metaprogramming]]
* [[Nasal/JavaScript Subset]]
| heading7 = Reference
| content7 =
* [[Nasal library]] ([[Nasal library#Core library functions|core]]/[[Nasal library#Extension functions|extension]] functions)
** [[Nasal library/geo|<code>geo</code> namespace]]
** [[Nasal library/io|<code>io</code> namespace]]
** [[Nasal library/math|<code>math</code> namespace]]
** [[Nasal library/props|<code>props</code> namespace]]
* [[Nasal String Manipulation]]
}}
{{Nasal Internals}}
{{-}}

== Misc ==
* Merge [[Nasal scripting language]] and [[What is Nasal]] into [[Nasal]]

[[Category:Nasal namespace documentation]]

Template:Nasal namespaces

2018-04-26T08:18:19Z

Red Leader: Update

{{navbox
|name = Nasal namespaces
|title = [[Nasal Namespaces|Nasal namespaces]]

|above = [[Nasal library|Global namespace (globals)]]
|list1 = [[Nasal library/clipboard|clipboard]] • [[Nasal library/debug|debug]] • [[Nasal library/geo|geo]] • [[Nasal library/io|io]] • [[Nasal library/math|math]] • [[Nasal library/os.path|os.path]] • [[Nasal library/props|props]]

}}<includeonly>{{main other|[[Category:Nasal namespace documentation]]}}</includeonly><noinclude>
{{Informative template|1=
__NOTOC__
== Goal ==
This navigation template enables easy navigation between different [[Nasal Namespaces|Nasal namespaces]].

Adding this template to a page in the article namespace will automatically add [[:Category:Nasal namespace documentation]] to that page.

== Usage ==
Put this line before the categories and the language links at the bottom of the article.
{{obr}}'''Nasal namespaces'''{{cbr}}

}}

[[Category:Navigation templates]]
</noinclude>

Nasal library/clipboard

2018-04-26T08:17:33Z

Red Leader: In the beginning...

User:Red Leader/Nasal documentation proposal

2018-04-22T20:12:57Z

Red Leader: /* Documentation pages */

Proposal for the documentation of the [[Nasal]] API.
__TOC__
== Documentation pages ==
{| class="wikitable"
|+ Nasal library {{Done}}
! Old page(s) !! New page
|-
|
* [[Nasal library functions]] ([http://wiki.flightgear.org/index.php?title=Nasal_library_functions&oldid=93458 perm])
* [[List of Nasal extension functions]] ([http://wiki.flightgear.org/index.php?title=List_of_Nasal_extension_functions&oldid=72953 perm])
|| [[Nasal library]]
|}

Form: <code><nowiki>[[Nasal library/<namespace>]]</nowiki></code>
{| class="wikitable"
|+ Nasal namespaces {{progressbar|30}}
! Namespace !! New page !! Progress
|-
| <code>'''aircraft'''</code>
| {{N/a|Not started|rowspan{{=}}"3" colspan{{=}}"2"}}
|-
| <code>'''bits'''</code>
|-
| <code>'''clipboard'''</code>
|-
| <code>'''debug'''</code> || [[Nasal library/debug]] || {{done}}
|-
| <code>'''geo'''</code> || [[Nasal library/geo]] || {{done}}
|-
| <code>'''gui'''</code>
| {{N/a|Not started|rowspan{{=}}"2" colspan{{=}}"2"}}
|-
| <code>'''http'''</code>
|-
| <code>'''io'''</code> || [[Nasal library/io]] || {{done}}
|-
| <code>'''math'''</code> || [[Nasal library/math]] || {{done}}
|-
| <code>'''mp_broadcast'''</code>
| {{N/a|Not started|colspan{{=}}"2"}}
|-
| <code>'''os[.path]'''</code> || [[Nasal library/os.path]] || {{done}}
|-
| <code>'''positioned'''</code>
| {{N/a|Not started|colspan{{=}}"2"}}
|-
| <code>'''props'''</code> || [[Nasal library/props‎‎]] || {{done}}
|-
| <code>'''scenery'''</code>
| {{N/a|Not started|rowspan{{=}}"7" colspan{{=}}"2"}}
|-
| <code>'''screen'''</code>
|-
| <code>'''std'''</code> (current page: [[Vector]])
|-
| <code>'''string'''</code>
|-
| <code>'''thread'''</code>
|-
| <code>'''utf8'''</code>
|-
| <code>'''view'''</code>
|}

{| class="wikitable"
|+ Basic Nasal scripting {{Not done}}
! Subject !! Current page(s) !! New page
|-
| Hashes
|
* [[Howto:Start using vectors and hashes in Nasal]]
* [[Object Oriented Programming with Nasal]]
* [[Object oriented programming in Nasal]]
* [[Howto:Understand Namespaces and Methods]]
* [[Nasal Namespaces in-depth]]
| [[Hashes in Nasal]]
|-
| Namespaces
|
* [[Howto:Understand Namespaces and Methods]]
* [[Nasal Namespaces in-depth]]
* [[Nasal Namespaces]]
| [[Namespaces in Nasal]]
|-
| Numbers || {{N/a|Very little}} || [[Numbers in Nasal]]
|-
| Vectors
|
* [[Nasal Variables]]
* [[Howto:Use vectors and foreach loops to write shorter code]]
* [[Howto:Start using vectors and hashes in Nasal]]
| [[Vectors in Nasal]]
|-
| Strings || [[Nasal Hello World]] || [[Strings in Nasal]]
|-
| Conditionals || [[Nasal Conditionals]] || [[Conditionals in Nasal]]
|-
| Operators || [[Nasal Operators]] || [[Operators in Nasal]]
|-
| Loops || [[Nasal Loops]] || [[Loops in Nasal]]
|-
| Functions || [[Using Nasal functions]] || [[Functions in Nasal]]
|-
| Variables || [[Nasal Variables]] || [[Variables in Nasal]]
|}

{| class="wikitable"
|+ Advanced Nasal scripting {{Not done}}
! What? !! Current page(s) !! New page
|-
| Vector slicing || [[Nasal Variables]] || [[Vectors in Nasal]]
|-
| OOP
|
* [[Object Oriented Programming with Nasal]]
* [[Object oriented programming in Nasal]]
| [[Object orientated programming in Nasal]]
|}

{| class="wikitable"
|+ [[Canvas]] {{Abbr|API|Application Programming Interface}} {{Not done}}
! What? !! Current page(s)
|-
| Canvas Element || [[Canvas Element]]
|-
| Canvas Image || [[Canvas Image]]
|-
| Canvas Path || [[Canvas Path]]
|-
| Canvas Map ||
* [[Canvas Map API]] {{FG ver|< 3.0}}
* [[Canvas MapStructure]] {{FG ver|3.0+}}
|-
| Event handling || [[Canvas Event Handling]]
|-
! colspan="2" | [[Canvas GUI]]
|-
| Layout system || [[Canvas Layout System]]
|-
| Widgets
|
* [[Canvas Widget Matrix]]
* [[Canvas GUI]]
* [[Howto:Creating a Canvas GUI Widget]]
|-
| Canvas MessageBox || [[Canvas MessageBox]]
|}

== Navbox ==
{{forum|30|Nasal}}
{{sidebar with collapsible headers
| topimage = [[File:Nasallogo3.png]]
| name = Nasal Navigation
| title = [[Nasal|Nasal scripting]]
| contentstyle = text-align: left;
| state = collapsed

| content1style = text-align: center;
| content1 = [[Nasal success stories|Success stories]] • [[Nasal FAQ|FAQ]]

| heading2 = Tools and utilities
| content2style = text-align: center;
| content2 = [[Nasal Console|Console]] • [[Interactive Nasal Console|REPL Console]] • [[Nasal Browser|Browser]] • [[Howto:Syntax highlighting for Nasal|Syntax highlighting]]

| heading3 = Getting started
| content3 =
* [[Nasal syntax overview|Syntax overview]]
* [[Writing Nasal scripts]]
* [[Nasal Snippets]]
* [[Developing and debugging Nasal code]]

| heading4 = Basic Scripting
| content4style = text-align: center;
| content4 = [[Hashes in Nasal|Hashes]] • [[Variables in Nasal|Variables]] • [[Operators in Nasal|Operators]] • [[Functions in Nasal|Functions]] • [[Namespaces in Nasal|Namespaces]] • [[Strings in Nasal|Strings]] • [[Vectors in Nasal|Vectors]] • [[Conditionals in Nasal|Conditionals]] • [[Numbers in Nasal|Numbers]] • [[Loops in Nasal|Loops]]

| heading5 = Advanced Scripting
| content5 =
* [[Object orientated programming in Nasal|Object orientated programming]]
* [[Nasal Flightplan]]
* [[Callbacks in Nasal]]
* [[Exception handling with Nasal]]
* [[Using listeners and signals with Nasal]]
* [[Caching Nasal function calls]]
* [[Nasal Unit Testing Framework]] (WIP)
* [[Nasal Meta-Programming]]
* [[A GPX flight logger in Nasal]]
* [[Multiplayer scripting in Nasal]]
| heading6 = Howtos
| content6 =
* [[Howto:Write a parser in Nasal]]
* [[Howto:Making HTTP Requests from Nasal]]
* [[Howto:Transmit properties over MP]]
* [[Howto:Terrain sampling in Nasal]]
* [[Howto:Create a new system in Nasal]]
* [[Howto:Load a Nasal file at runtime]]
* [[Howto:Control the route manager in Nasal]]
* [[Howto:Get a number of elevation offsets for a number of objects]]
* [[Howto:Nasal in scenery object XML files]]
* [[Howto:Create animation XML files from Nasal]]
* [[Howto:Port I/O from Nasal]]
* [[Howto:Continuation-passing style programming in Nasal]]
* [[Howto:Start worker threads using listeners in Nasal]]
* [[Howto:Developing a DSL interpreter in Nasal]]
* [[Howto:Nasal Metaprogramming]]
* [[Nasal/JavaScript Subset]]
| heading7 = Reference
| content7 =
* [[Nasal library]] ([[Nasal library#Core library functions|core]]/[[Nasal library#Extension functions|extension]] functions)
** [[Nasal library/geo|<code>geo</code> namespace]]
** [[Nasal library/io|<code>io</code> namespace]]
** [[Nasal library/math|<code>math</code> namespace]]
** [[Nasal library/props|<code>props</code> namespace]]
* [[Nasal String Manipulation]]
}}
{{Nasal Internals}}
{{-}}

== Misc ==
* Merge [[Nasal scripting language]] and [[What is Nasal]] into [[Nasal]]

Nasal library/os.path

2018-04-22T20:12:16Z

Red Leader: Finish

{{Nasal Navigation|nocat=1}}
This page contains documentation for the '''<code>os.path</code> namespace''' in [[Nasal]]. This namespace implements tools (from SGPath) for manipulating file paths. Everything in the <code>os.path</code> namespace is sourced from {{flightgear file|src/Scripting/NasalSGPath.cxx}}

{{tip|Copy & paste the examples into your [[Nasal Console]] and execute them to see what they do.|width=70%}}

{{note|Everything here was added to FlightGear 3.0. (released [[FlightGear History#Release timeline|February 2014]])|width=70%}}

== Class ==
=== os.path ===
{{Nasal doc
|mode = class
|text = A pseudo-class (actually a Nasal ghost). This is the main class that stores and allows manipulation of file paths. This is also integrated into the <code>os.path</code>.
}}
==== new() ====
{{Nasal doc
|syntax = os.path.new([path]);
|text = Constructor function. Returns a new <code>os.path</code> instance. Note that the path must not violate the rules for allowed paths.
|param1 = path
|param1text = Optional string specifying the filepath. If not given, the path will default to [[$FG_ROOT]]
|example1 = var path = os.path.new("C:/Windows"); # Windows filepath
# var path = os.path.new("/usr/bin/"); # Unix filepath
print(path.realpath);
}}
==== set() ====
{{Nasal doc
|syntax = os.path.set([path]);
|text = Sets the filepath. Note that the path must not violate the rules for allowed paths.
|param1 = path
|param1text = Optional string specifying the filepath. If not given, the path will be set to [[$FG_ROOT]]
|example1 = var path = os.path.new("C:/Windows");
# var path = os.path.new("/usr/bin/"); # alternative Unix filepath
print(path.realpath);
path.set("C:/Windows/Program Files");
# path.set("/usr/"); # alternative Unix filepath
print(path.realpath); # prints new path
}}
==== append() ====
{{Nasal doc
|syntax = os.path.append([path]);
|text = Appends a new part to the filepath.
|param1 = path
|param1text = Optional string specifying the new part to add to the filepath. If not given, the resultant path will not change.
|example1 = var path = os.path.new("C:/Windows");
# var path = os.path.new("/usr/"); # alternative Unix filepath
print(path.realpath);
path.append("Program Files");
# path.append("bin"); # alternative Unix filepath
print(path.realpath); # prints "C:/Windows/Program Files" or "/usr/bin"
}}
==== concat() ====
{{Nasal doc
|syntax = os.path.concat([path]);
|text = Appends a new part to the filepath.
|param1 = path
|param1text = Optional string specifying part to concat to the existing filepath. Note that this will simply add the string to the end of the path without adding a separator. If not given, the resultant path will not change.
|example1 = var path = os.path.new("C:/Windows");
# var path = os.path.new("/usr"); # alternative Unix filepath
print(path.realpath);
path.concat("/Program Files");
# path.concat("/bin"); # alternative Unix filepath
print(path.realpath); # prints "C:/Windows/Program Files" or "/usr/bin"
}}
==== exists() ====
{{Nasal doc
|syntax = os.path.exists();
|text = Returns 1 (true) if the path exists and 0 (false) if it does not.
|example1 = var path = os.path.new("C:/Windows");
# var path = os.path.new("/usr"); # alternative Unix filepath
print(path.exists()); # prints 1 (true)
path.set("C:/Window");
# path.set("/r"); # alternative Unix filepath
print(path.exists()); # prints 0 (false)
}}
==== canRead() ====
{{Nasal doc
|syntax = os.path.canRead();
|text = Returns 1 (true) if the path can be read (from Nasal) and 0 (false) if it cannot. This follows the rules for allowed paths.
|example1 = var path = os.path.new("C:/Windows");
# var path = os.path.new("/usr"); # alternative Unix filepath
print(path.canRead()); # prints 0 (false)
path.set(getprop("sim/fg-home"));
print(path.canRead()); # prints 1 (true)
}}
==== canWrite() ====
{{Nasal doc
|syntax = os.path.canWrite();
|text = Returns 1 (true) if the path can be written to (from Nasal) and 0 (false) if it cannot. This follows the rules for allowed paths.
|example1 = var path = os.path.new("C:/Windows");
# var path = os.path.new("/usr"); # alternative Unix filepath
print(path.canWrite()); # prints 0 (false)
path.set(getprop("sim/fg-home") ~ "/txt.log");
print(path.canWrite()); # prints 1 (true)
}}
==== isFile() ====
{{Nasal doc
|syntax = os.path.isFile();
|text = Returns 1 (true) if the path points to a file and 0 (false) if it points to a directory. Note that the path must also exist.
|example1 = var path = os.path.new(getprop("sim/fg-root"));
print(path.isFile()); # prints 0 (false)
path.append("Nasal/io.nas");
print(path.isFile()); # prints 1 (true)
}}
==== isDir() ====
{{Nasal doc
|syntax = os.path.isDir();
|text = Returns 1 (true) if the path points to a directory and 0 (false) if it points to a file. Note that the path must also exist.
|example1 = var path = os.path.new(getprop("sim/fg-root"));
print(path.isDir()); # prints 1 (true)
path.append("Nasal/io.nas");
print(path.isDir()); # prints 0 (false)
}}
==== isRelative() ====
{{Nasal doc
|syntax = os.path.isRelative();
|text = Returns 1 (true) if the path is relative and 0 (false) if it is not.
|example1 = var path = os.path.new(getprop("sim/fg-root"));
path.set("./Nasal");
print(path.isRelative()); # prints 1 (true)
}}
==== isAbsolute() ====
{{Nasal doc
|syntax = os.path.isAbsolute();
|text = Returns 1 (true) if the path is an absolute path and 0 (false) if it is not.
|example1 = var path = os.path.new(getprop("sim/fg-root"));
print(path.isAbsolute()); # prints 1 (true)
}}
==== isNull() ====
{{Nasal doc
|syntax = os.path.isNull();
|text = Returns 1 (true) if the path is null and 0 (false) if it is not.
|example1 = var path = os.path.new();
print(path.isNull());
}}
==== create_dir() ====
{{Nasal doc
|syntax = os.path.create_dir();
|text = Creates the parent of the path as a directory. This will only work if the path is absolute and considered as writable by {{func link|fgValidatePath()|link=https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/Main/util.cxx#l142}} (typically okay under [[$FG_HOME]]/Export).
|example1 = var path = os.path.new(getprop("/sim/fg-home") ~ "/Export/test/demo.txt");
path.create_dir(); # Creates $FG_HOME/Export/test/
}}
==== remove() ====
{{Nasal doc
|syntax = os.path.remove();
|text = Removes the last element of the path from the file directory. This will only work if the path is absolute and deletion of the file is permitted by the file permissions (typically okay under [[$FG_HOME]]/Export). Note that on Windows, deletion of read-only files are never permitted.
|example1 = var path = os.path.new(getprop("/sim/fg-home") ~ "/Export/demo.txt");
var file = io.open(path.realpath, "w");
io.write(file, 'Hello, World' ~ "\n");
io.close(file);
print(path.exists()); # prints "1"

path.remove();
print(path.exists()); # prints "0"
|example2 = var path = os.path.new(getprop("/sim/fg-home") ~ "/Export/test");
path.create_dir();
path.remove(); # folder "/test" is removed
}}
==== rename() ====
{{Nasal doc
|syntax = os.path.rename(new_name);
|text = Renames the last element of the path from the file directory. This will only work if the path is absolute, the old path is both readable and writable, the new path is writable.
|example1 = var path = os.path.new(getprop("/sim/fg-home") ~ "/Export/demo.txt");
var file = io.open(path.realpath, "w");
io.write(file, 'Hello, World' ~ "\n");
io.close(file);
path.rename(getprop("/sim/fg-home") ~ "/Export/demo1.txt");
print(path.realpath); # prints $FG_HOME/Export/demo1.txt
}}
==== realpath ====
{{Nasal doc
|syntax = os.path.realpath;
|text = A string variable that gives the full file path. This should only be used when the path is an absolute path. If the path is relative, it will simply be appended to the FlightGear folder (the level up from [[$FG_ROOT]]).
|example1 = var path = os.path.new(getprop("/sim/fg-home"));
print(path.realpath); # prints the absolute path of $FG_HOME
}}
==== file ====
{{Nasal doc
|syntax = os.path.file;
|text = A string variable that gives the last part of the filepath.
|example1 = var path = os.path.new(getprop("/sim/fg-home"));
print(path.file); # prints "flightgear.org"
}}
==== dir ====
{{Nasal doc
|syntax = os.path.dir;
|text = A string variable that gives all of the filepath except the last element (see <code>os.path.file</code> above).
|example1 = var path = os.path.new("Program Files/temp/text.txt");
print(path.dir); # prints "Program Files/temp"
}}
==== base ====
{{Nasal doc
|syntax = os.path.base;
|text = A string variable that gives all of the filepath except the extension of the file. If the filepath points to a folder, it has the same value as [[#realpath|realpath]].
|example1 = var path = os.path.new("Program Files/temp/text.txt");
print(path.base); # prints "Program Files/temp/text"
}}
==== file_base ====
{{Nasal doc
|syntax = os.path.file_base;
|text = A string variable that gives the file name without the extension. If the filepath points to a folder, it will simply be the folder name.
|example1 = var path = os.path.new("Program Files/temp/text.txt");
print(path.file_base); # prints "text"
}}
==== extension ====
{{Nasal doc
|syntax = os.path.extension;
|text = A string variable that gives the file's extension. If the filepath points to a folder, it will be an empty string.
|example1 = var path = os.path.new("Program Files/temp/text.txt");
print(path.extension); # prints "txt"
}}
==== lower_extension ====
{{Nasal doc
|syntax = os.path.lower_extension;
|text = A string variable that gives the file's extension, but converted to lowercase. If the filepath points to a folder, it will be an empty string.
|example1 = var path = os.path.new("Program Files/temp/text.TXT");
print(path.lower_extension); # prints "txt"
}}
==== complete_lower_extension ====
{{Nasal doc
|syntax = os.path.complete_lower_extension;
|text = This is to be used when a file has a double extension (e.g., <code>.tar.gz</code>). It also converts it to lowercase. If the filepath points to a folder, it will be an empty string.
|example1 = var path = os.path.new("Program Files/temp/text.TAR.GZ");
print(path.complete_lower_extension); # prints "tar.gz"
}}
==== str ====
{{Nasal doc
|syntax = os.path.str;
|text = A string giving the path that the instance points too.
This is to be used when a file has a double extension (e.g., <code>.tar.gz</code>). It also converts it to lowercase. If the filepath points to a folder, it will be an empty string.
|example1 = var path = os.path.new("../temp/text.txt");
print(path.str); # prints "../temp/text.txt"
|example2 = var path = os.path.new(getprop("sim/fg-home"));
print(path.str); # prints the full path to $FG_HOME
}}
==== mtime ====
{{Nasal doc
|syntax = os.path.mtime;
|text = An integer giving the Unix time when the file or folder was last modified.
|example1 = var path = os.path.new(getprop("sim/fg-home"));
print(path.mtime); # prints a Unix time
}}

== Functions ==
=== desktop() ===
{{Nasal doc
|syntax = os.path.desktop();
|text = Creates and returns an <code>os.path</code> pointing to the desktop location.

{{Note|As of April 2018, this function does not work properly and returns the <code>/bin</code> folder.}}
|example1 = var path = os.path.desktop();
print(path.realpath);
}}
=== standardLocation() ===
{{Nasal doc
|syntax = os.path.standardLocation(location);
|text = Creates and returns an <code>os.path</code> pointing to the standard location.

{{Note|As of April 2018, only supplying "HOME" to this function actually works. All the others do not work properly and return the <code>/bin</code> folder.}}
|param1 = location
|param1text = String specifying the standard location to use. May be one of <code>HOME</code>, <code>DESKTOP</code>, <code>DOWNLOADS</code>, <code>DOCUMENTS</code>, or <code>PICTURES</code>.
|example1 = var path = os.path.standardLocation("HOME");
print(path.realpath);
}}

{{Nasal namespaces}}

Nasal library/os.path

2018-04-15T20:30:39Z

Red Leader: More doc

{{Nasal Navigation|nocat=1}}
This page contains documentation for the '''<code>os.path</code> namespace''' in [[Nasal]]. This namespace implements tools (from SGPath) for manipulating file paths. Everything in the <code>os.path</code> namespace is sourced from {{flightgear file|src/Scripting/NasalSGPath.cxx}}

{{tip|Copy & paste the examples into your [[Nasal Console]] and execute them to see what they do.|width=70%}}

{{note|Everything here was added to FlightGear 3.0. (released [[FlightGear History#Release timeline|February 2014]])|width=70%}}

== Class ==
=== os.path ===
{{Nasal doc
|mode = class
|text = A pseudo-class (actually a Nasal ghost). This is the main class that stores and allows manipulation of file paths. This is also integrated into the <code>os.path</code>.
}}
==== new() ====
{{Nasal doc
|syntax = os.path.new([path]);
|text = Constructor function. Returns a new <code>os.path</code> instance. Note that the path must not violate the rules for allowed paths.
|param1 = path
|param1text = Optional string specifying the filepath. If not given, the path will default to [[$FG_ROOT]]
|example1 = var path = os.path.new("C:/Windows"); # Windows filepath
# var path = os.path.new("/usr/bin/"); # Unix filepath
print(path.realpath);
}}
==== set() ====
{{Nasal doc
|syntax = os.path.set([path]);
|text = Sets the filepath. Note that the path must not violate the rules for allowed paths.
|param1 = path
|param1text = Optional string specifying the filepath. If not given, the path will be set to [[$FG_ROOT]]
|example1 = var path = os.path.new("C:/Windows");
# var path = os.path.new("/usr/bin/"); # alternative Unix filepath
print(path.realpath);
path.set("C:/Windows/Program Files");
# path.set("/usr/"); # alternative Unix filepath
print(path.realpath); # prints new path
}}
==== append() ====
{{Nasal doc
|syntax = os.path.append([path]);
|text = Appends a new part to the filepath.
|param1 = path
|param1text = Optional string specifying the new part to add to the filepath. If not given, the resultant path will not change.
|example1 = var path = os.path.new("C:/Windows");
# var path = os.path.new("/usr/"); # alternative Unix filepath
print(path.realpath);
path.append("Program Files");
# path.append("bin"); # alternative Unix filepath
print(path.realpath); # prints "C:/Windows/Program Files" or "/usr/bin"
}}
==== concat() ====
{{Nasal doc
|syntax = os.path.concat([path]);
|text = Appends a new part to the filepath.
|param1 = path
|param1text = Optional string specifying part to concat to the existing filepath. Note that this will simply add the string to the end of the path without adding a separator. If not given, the resultant path will not change.
|example1 = var path = os.path.new("C:/Windows");
# var path = os.path.new("/usr"); # alternative Unix filepath
print(path.realpath);
path.concat("/Program Files");
# path.concat("/bin"); # alternative Unix filepath
print(path.realpath); # prints "C:/Windows/Program Files" or "/usr/bin"
}}
==== exists() ====
{{Nasal doc
|syntax = os.path.exists();
|text = Returns 1 (true) if the path exists and 0 (false) if it does not.
|example1 = var path = os.path.new("C:/Windows");
# var path = os.path.new("/usr"); # alternative Unix filepath
print(path.exists()); # prints 1 (true)
path.set("C:/Window");
# path.set("/r"); # alternative Unix filepath
print(path.exists()); # prints 0 (false)
}}
==== canRead() ====
{{Nasal doc
|syntax = os.path.canRead();
|text = Returns 1 (true) if the path can be read (from Nasal) and 0 (false) if it cannot. This follows the rules for allowed paths.
|example1 = var path = os.path.new("C:/Windows");
# var path = os.path.new("/usr"); # alternative Unix filepath
print(path.canRead()); # prints 0 (false)
path.set(getprop("sim/fg-home"));
print(path.canRead()); # prints 1 (true)
}}
==== canWrite() ====
{{Nasal doc
|syntax = os.path.canWrite();
|text = Returns 1 (true) if the path can be written to (from Nasal) and 0 (false) if it cannot. This follows the rules for allowed paths.
|example1 = var path = os.path.new("C:/Windows");
# var path = os.path.new("/usr"); # alternative Unix filepath
print(path.canWrite()); # prints 0 (false)
path.set(getprop("sim/fg-home") ~ "/txt.log");
print(path.canWrite()); # prints 1 (true)
}}
==== isFile() ====
{{Nasal doc
|syntax = os.path.isFile();
|text = Returns 1 (true) if the path points to a file and 0 (false) if it points to a directory. Note that the path must also exist.
|example1 = var path = os.path.new(getprop("sim/fg-root"));
print(path.isFile()); # prints 0 (false)
path.append("Nasal/io.nas");
print(path.isFile()); # prints 1 (true)
}}
==== isDir() ====
{{Nasal doc
|syntax = os.path.isDir();
|text = Returns 1 (true) if the path points to a directory and 0 (false) if it points to a file. Note that the path must also exist.
|example1 = var path = os.path.new(getprop("sim/fg-root"));
print(path.isDir()); # prints 1 (true)
path.append("Nasal/io.nas");
print(path.isDir()); # prints 0 (false)
}}
==== isRelative() ====
{{Nasal doc
|syntax = os.path.isRelative();
|text = Returns 1 (true) if the path is relative and 0 (false) if it is not.
|example1 = var path = os.path.new(getprop("sim/fg-root"));
path.set("./Nasal");
print(path.isRelative()); # prints 1 (true)
}}
==== isAbsolute() ====
{{Nasal doc
|syntax = os.path.isAbsolute();
|text = Returns 1 (true) if the path is an absolute path and 0 (false) if it is not.
|example1 = var path = os.path.new(getprop("sim/fg-root"));
print(path.isAbsolute()); # prints 1 (true)
}}
==== isNull() ====
{{Nasal doc
|syntax = os.path.isNull();
|text = Returns 1 (true) if the path is null and 0 (false) if it is not.
|example1 = var path = os.path.new();
print(path.isNull());
}}
==== create_dir() ====
{{Nasal doc
|syntax = os.path.create_dir();
|text = Creates the parent of the path as a directory. This will only work if the path is absolute and considered as writable by {{func link|fgValidatePath()|link=https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/Main/util.cxx#l142}} (typically okay under [[$FG_HOME]]/Export).
|example1 = var path = os.path.new(getprop("/sim/fg-home") ~ "/Export/test/demo.txt");
path.create_dir(); # Creates $FG_HOME/Export/test/
}}
==== remove() ====
{{Nasal doc
|syntax = os.path.remove();
|text = Removes the last element of the path from the file directory. This will only work if the path is absolute and deletion of the file is permitted by the file permissions (typically okay under [[$FG_HOME]]/Export). Note that on Windows, deletion of read-only files are never permitted.
|example1 = var path = os.path.new(getprop("/sim/fg-home") ~ "/Export/demo.txt");
var file = io.open(path.realpath, "w");
io.write(file, 'Hello, World' ~ "\n");
io.close(file);
print(path.exists()); # prints "1"

path.remove();
print(path.exists()); # prints "0"
|example2 = var path = os.path.new(getprop("/sim/fg-home") ~ "/Export/test");
path.create_dir();
path.remove(); # folder "/test" is removed
}}
==== rename() ====
{{Nasal doc
|syntax = os.path.rename(new_name);
|text = Renames the last element of the path from the file directory. This will only work if the path is absolute, the old path is both readable and writable, the new path is writable.
|example1 = var path = os.path.new(getprop("/sim/fg-home") ~ "/Export/demo.txt");
var file = io.open(path.realpath, "w");
io.write(file, 'Hello, World' ~ "\n");
io.close(file);
path.rename(getprop("/sim/fg-home") ~ "/Export/demo1.txt");
print(path.realpath); # prints $FG_HOME/Export/demo1.txt
}}
==== realpath ====
{{Nasal doc
|syntax = os.path.realpath;
|text = A string variable that gives the full file path. This should only be used when the path is an absolute path. If the path is relative, it will simply be appended to the FlightGear folder (the level up from [[$FG_ROOT]]).
|example1 = var path = os.path.new(getprop("/sim/fg-home"));
print(path.realpath); # prints the absolute path of $FG_HOME
}}
==== file ====
{{Nasal doc
|syntax = os.path.file;
|text = A string variable that gives the last part of the filepath.
|example1 = var path = os.path.new(getprop("/sim/fg-home"));
print(path.file); # prints "flightgear.org"
}}
==== dir ====
{{Nasal doc
|syntax = os.path.dir;
|text = A string variable that gives all of the filepath except the last element (see <code>os.path.file</code> above).
|example1 = var path = os.path.new("Program Files/temp/text.txt");
print(path.dir); # prints "Program Files/temp"
}}
==== base ====
{{Nasal doc
|syntax = os.path.base;
|text = A string variable that gives all of the filepath except the extension of the file. If the filepath points to a folder, it has the same value as [[#realpath|realpath]].
|example1 = var path = os.path.new("Program Files/temp/text.txt");
print(path.base); # prints "Program Files/temp/text"
}}
==== file_base ====
{{Nasal doc
|syntax = os.path.file_base;
|text = A string variable that gives the file name without the extension. If the filepath points to a folder, it will simply be the folder name.
|example1 = var path = os.path.new("Program Files/temp/text.txt");
print(path.file_base); # prints "text"
}}
==== extension ====
{{Nasal doc
|syntax = os.path.extension;
|text = A string variable that gives the file's extension. If the filepath points to a folder, it will be an empty string.
|example1 = var path = os.path.new("Program Files/temp/text.txt");
print(path.extension); # prints "txt"
}}
==== lower_extension ====
{{Nasal doc
|syntax = os.path.lower_extension;
|text = A string variable that gives the file's extension, but converted to lowercase. If the filepath points to a folder, it will be an empty string.
|example1 = var path = os.path.new("Program Files/temp/text.TXT");
print(path.lower_extension); # prints "txt"
}}
==== complete_lower_extension ====
{{Nasal doc
|syntax = os.path.complete_lower_extension;
|text = This is to be used when a file has a double extension (e.g., <code>.tar.gz</code>). It also converts it to lowercase. If the filepath points to a folder, it will be an empty string.
|example1 = var path = os.path.new("Program Files/temp/text.TAR.GZ");
print(path.complete_lower_extension); # prints "tar.gz"
}}
==== str ====
==== mtime ====

== Functions ==
=== desktop() ===
=== standardLocation() ===

{{Nasal namespaces}}

Nasal library/os.path

2018-04-15T19:53:17Z

Red Leader: /* realpath */ finish

Nasal library/os.path

2018-04-15T19:05:55Z

Red Leader: Start realpath doc

Template:Nasal namespaces

2018-03-19T14:05:06Z

Red Leader: Update with os.path

{{navbox
|name = Nasal namespaces
|title = [[Nasal Namespaces|Nasal namespaces]]

|above = [[Nasal library|Global namespace (globals)]]
|list1 = [[Nasal library/debug|debug]] • [[Nasal library/geo|geo]] • [[Nasal library/io|io]] • [[Nasal library/math|math]] • [[Nasal library/os.path|os.path]] • [[Nasal library/props|props]]

}}<includeonly>{{main other|[[Category:Nasal namespace documentation]]}}</includeonly><noinclude>
{{Informative template|1=
__NOTOC__
== Goal ==
This navigation template enables easy navigation between different [[Nasal Namespaces|Nasal namespaces]].

Adding this template to a page in the article namespace will automatically add [[:Category:Nasal namespace documentation]] to that page.

== Usage ==
Put this line before the categories and the language links at the bottom of the article.
{{obr}}'''Nasal namespaces'''{{cbr}}

}}

[[Category:Navigation templates]]
</noinclude>

Nasal library/os.path

2018-03-18T21:37:55Z

Red Leader: Doc rename()

Nasal library/os.path

2018-03-18T21:06:24Z

Red Leader: Doc remove()

Nasal library/os.path

2018-03-18T20:43:20Z

Red Leader:

Nasal library/os.path

2018-03-18T20:40:07Z

Red Leader: Complete create_dir() doc

Nasal library/os.path

2018-02-18T20:46:03Z

Red Leader: Doc isNull()

Nasal library/os.path

2018-02-18T20:32:14Z

Red Leader: More doc

Nasal library/os.path

2018-02-18T16:16:50Z

Red Leader: Doc canRead() and Write()

Nasal library/os.path

2018-02-17T21:26:57Z

Red Leader: /* exists() */

Nasal library/os.path

2018-02-17T21:26:46Z

Red Leader: /* Class */ Doc exists()

Nasal library/os.path

2018-02-17T21:13:42Z

Red Leader: /* Class */ Doc concat()