Re: [Flightgear-devel] [patch] Improved Nasal access to?airport

2010-10-11 Thread Martin Spott
James Turner wrote: > Not saying this isn't useful, but I'd rather everything in the app used > the same data source (the FGPositioned 'database' and its query > functions), and then we can change the implementation of that if required > - for example, a caching version which queries the Landcover

Re: [Flightgear-devel] [patch] Improved Nasal access to?airport

2010-10-11 Thread James Turner
On 11 Oct 2010, at 13:36, Martin Spott wrote: > Hehe, I'm still looking for a place to drop those features which are already > availale from our Landcover-DB. This is just the SQL prompt, but it's no > big deal casting this into some CGI - for those people who don't mind having > internet connec

Re: [Flightgear-devel] [patch] Improved Nasal access to?airport

2010-10-11 Thread Martin Spott
Scott Hamilton wrote: > However I really like the idea of getting back an array of airports > within some radius of a centre lat/lon pair, and/or within a bounding > box (2 or 4 lat/lon pairs), and if the same could be done with other > navigation elements in nav.dat it would be most excellent! H

Re: [Flightgear-devel] [patch] Improved Nasal access to airport information

2010-10-11 Thread James Turner
On 11 Oct 2010, at 10:52, Scott Hamilton wrote: > Yes I'd like to second the idea of returning objects (with attributes and > methods for doing interesting things), I'm guessing we don't need to abstract > it too far from what is provided underneath. > > However I really like the idea of getti

Re: [Flightgear-devel] [patch] Improved Nasal access to airport information

2010-10-11 Thread Scott Hamilton
On Mon, 2010-10-11 at 09:28 +0100, James Turner wrote: > On 10 Oct 2010, at 17:21, Torsten Dreyer wrote: > > We need to stop exposing *functions* to Nasal, and start exposing *objects*, > with properties. > > Notably, amongst the airportinfo() structure is a runways hash, which > contain

Re: [Flightgear-devel] [patch] Improved Nasal access to airport information

2010-10-11 Thread James Turner
On 10 Oct 2010, at 17:21, Torsten Dreyer wrote: > Sounds like a good idea. I am working on an extended METAR system > allowing to fetch METAR data for an arbitrary number of stations. This > will allow lateral (not only timed) interpolation of weather. Looks like > these two systems might be a

Re: [Flightgear-devel] [patch] Improved Nasal access to airport information

2010-10-10 Thread Torsten Dreyer
Am 10.10.10 18:06, schrieb Stuart Buchanan: > Hi All, > > I've been working on a small patch to change the existing global Nasal > function airportinfo() to return more than one result. > > With this patch, and optional argument allows the caller to specify > the number of nearest airports to ret

[Flightgear-devel] [patch] Improved Nasal access to airport information

2010-10-10 Thread Stuart Buchanan
Hi All, I've been working on a small patch to change the existing global Nasal function airportinfo() to return more than one result. With this patch, and optional argument allows the caller to specify the number of nearest airports to return. E.g. airportinfo(10), returns the nearest 10 airports