On 25 Jun 2013, at 22:48, Stuart Buchanan <stuar...@gmail.com> wrote:

> Declaring that the Feb 2014 release will be 3.0 now will give everyone plenty 
> of
> notice, and might encourage efforts to fix bugs in the next 6 months.  I'm 
> aware
> that my FG development time is more limited these days, and given activity on
> this list I suspect I'm not alone, so this time might be quite useful.

I think I sensible step in that case is to keep 3.0 as backward compatible (in 
terms of Aircraft APIs) with 2.12 as possible, which mostly means my resisting 
the urge to clean up legacy stuff :)

Obviously it's tricky to offer a 100% guarantee, but I don't have anything 
planned for 3.0 that will require aircraft changes - I'm sure new technologies 
such as state machines, knob/slider animations and tooltips will mature and 
gain some new features but hopefully aircraft developers will be able to work 
against 2.12 with confidence that things will work the same in 3.0

It's a bit tricky because I haven't had much feedback from aircraft developers 
about the new APIs (since they aren't in 2.10), but once 2.12 ships we would 
want to keep them compatible, so fingers crossed the current design is sensible 


This SF.net email is sponsored by Windows:

Build for Windows Store.

Flightgear-devel mailing list

Reply via email to