I'll take the liberty of replying to you all at once...

On 11/26/03 at 11:02 AM James Turner wrote:
>Right, being able to include an aerial photo as Jon suggested, or a 
>plan (as is available from the CAA, for major Uk airports), would 
>obviously greatly ease taxi-way creation.

I've almost finished getting a 5 arc-second orange grid overlay working,
which is the same as used on the CAA aerodrome charts available online (UK
aip).  I was also going to add functionality to call wget to get the
Terrasever US aerial photos and use them as background - Terraserver terms
of use specifically allows any use whatsoever of the images.  I agree
though that fgsd is ultimately the way forward in this area.

Frederic BOUVIER wrote:
>This is something I would like to do, as time permit, or someone else do. 
>It shouldn't be very difficult to draw OpenGL rectangles over the existing

>framework. It would benefit of having map or chart as an underlying 
>overlay and placement aid.

>James Turner wrote:
>I might see if i can get FGSD running on OS-X too, and then see how 
>much work would be involved in moving some functionality around.
>

Yep, in the long run it would be useful to have the whole taxi-editing,
scenery editing, and facilities editing all wrapped up in fgsd, which seems
to be emerging as the de-facto, most sophisticated, FG scenery editor.  In
the short term its easier for me (and quicker to get the taxiway editing
functionality going) to bang away at my own code, especially as a lot of it
was already written in mfc ages ago, and porting to wxWindows turned out to
be quite easy (I've got a generic undo/redo buffer already written in mfc
to go in at some point), and some of the stuff I've learnt (such as how to
eliminate the flicker) has been useful in some non-FlightGear wxWindows
apps I'm also working on.  Once FLTK 2.0 is released I'll have a good play
with fgsd, in the meantime I'll try and code the functionality as
generically as possible to make it easier for others to port if they want
to.  The only upside I can think of for the wxWindows version over an fgsd
addition is that it doesn't need hardware openGL support to run smoothly,
but realistically even most laptops should handle that these days.

> James Turner wrote something about the Mac

It's great that you've got it going on the Mac - feel free to send me the
patches, and there's plenty of other Scottish airfields!!

> and James Turner wrote:
>but I don't really want to invest brain-space learning WxWindows 
>if I can avoid it. Not that I'm a fan of FLTK either ...

How can you not be a fan of wxWindows? - the chap who started it lives in
Edinburgh, and it uses 'colour' instead of 'color' ;-)

On 11/26/03 at 10:45 AM Jon Stockill wrote:
>On Wed, 26 Nov 2003, James Turner wrote:
>> One thing I'd really like is the ability to place some generic,
>> rectangular buildings objects down, on the airports. Obviously this
>
>Agreed - even if it just output a bunch of points that could be added
>directly to the stg files.
>
>While we're coming up with ideas to keep David busy - Is there any way to
>set the priority of the taxiway segments, where several meet it'd be nice
>to be able to change the stacking - I'm guessing that genapts just
>processes them in order, so being able to bump a section to the end of the
>list should cause it to be drawn on top.

It should be easy to output some points for the stg files, possibly with
the correct format and with a placeholder for the name - I'll have a look
at that.

Up/down list - hmm, genapts rendering order had completely never occurred
to me.  I'll have a look at that - should be possible to have a pop-up list
of taxiways, with the ability to move one up or down the order.

>Jon Stockill wrote:
>btw, I still needed to insert an extra space between the lat & lon to 
>keep genapts happy.

Yes, you're right, I'll fix that in the next one.  You could try replacing
setw(10) with setw(11) in line 332 of airport.cpp - that should do the
trick.

And remember chaps, pressing 'w' will completely and silently overwrite
your ICAO.dat file, so keep it backed up somewhere other than the working
copy!!!

(Putting the .dat file handling into the file open/save dialog should be
easy - I'll have a look)

Cheers - Dave




_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to