Well... unfortunatly though it might be called "open source" the source code of LK8000 version 1.23b is not available anywhere... The latest source code on the LK8000 page is of 1.22b and since the LK8000 project doesn't use any source code control system at all it is not possible to download it from anywhere else.
If you have the source code feel free to send it to us, but without the code it is kinda hard to look at the code ;) Have you taken a look at the WELT2000 database?! Might be what you are looking for... Turbo -------- Original-Nachricht -------- > Datum: Tue, 21 Dec 2010 14:02:36 +0000 > Von: Martin Gregorie <[email protected]> > An: Tobias Bieniek <[email protected]> > Betreff: Re: [Xcsoar-user] Data files used in XCSoar: airfield data > On Tue, 2010-12-21 at 13:51 +0100, Tobias Bieniek wrote: > > Yes, the behavior hasn't changed yet. If you have good ideas for a > > better dialog layout or behavior please sketch them and create a > > ticket on trac. > > > After I hit 'send' I fed the same extended data to LK8000 1.23b. It > wraps the comment into the box and also wraps long lines in the Airfield > file onto its full page display. In both cases the line break is on > whitespace rather than breaking a word. Apart line wrapping its > behaviour, on the turnpoint detail pages anyway, is the same as XCSoar. > > So, rather than raising a ticket I'd just suggest you look at the LK8000 > code in this area. > > > BTW the seeyou file format contains also frequency information which > > isn't yet displayed... > > > I'm with you on this point: never alter the format of standard files. > > I've never seen the SeeYou file format. At present I'm putting that info > in the Airfields file along with runway information and anything else > thats useful if you have a choice of landout fields. > > Currently I favour building a database of landout fields with a lot more > data elements, e.g. repeating 'runway' and 'frequency' groups togethed > with access and landing charge warnings would be useful. The same schema > would also work for turnpoints though I don't see why we'd need that in > the UK and don't know the situation elsewhere. Programs consist of a > maintenance program for the main database together with a set of > conversion modules to generate TP and airfield files for specific > navigation programs/devices. The database schema and programs could be > open sourced together with a data interchange format, which could be > XML, if the database should turn out to be relational. > > The CAD world does this by keeping drawings in proprietary files > (AutoCAD uses DWG files) and uses DXF files to transfer drawings between > CAD systems. In this case I don't see there being different database > formats, just that a flat file would be easier to publish so pilots can > generate files to suit whatever is in their cockpits. > > Martin > > -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt auch mit gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl ------------------------------------------------------------------------------ Forrester recently released a report on the Return on Investment (ROI) of Google Apps. They found a 300% ROI, 38%-56% cost savings, and break-even within 7 months. Over 3 million businesses have gone Google with Google Apps: an online email calendar, and document program that's accessible from your browser. Read the Forrester report: http://p.sf.net/sfu/googleapps-sfnew _______________________________________________ Xcsoar-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcsoar-user
