[Kflog-user] Suggestion for KFlog: Flarm integration (new try)
eggert.ehmke at berlin.de
Thu Aug 4 18:31:44 CEST 2011
I checked in the modifications in the Qt4 subdirectory. I did a checkout on
another PC and compiled and tested again. Please can someone confirm that it
compiles and works as described.
We should wait until I get confirmation from the Flarm guys, though I don't
expect problems from their side. But please don't create an official release
before that happens.
On Thursday 04 August 2011 09:25:02 you wrote:
> Hi Eggert,
> that is a nice idea to add Flram support to KFLog. I added my comments in
> your email text.
> br Axel
> 2011/8/3 Eggert Ehmke <eggert.ehmke at berlin.de>
> > Hello,
> > I started some basic integration of Flarm devices. As a beginning, I
> > implemented an export function that allows to export the flarmcfg.txt
> > file. As
> Maybe you can add a date and time stamp into the first line to see when the
> file was created?
> > a next step the upload of the task data via the serial interface makes
> > sense.
> > Before I start to check in the updates I want to discuss the approach.
> > I added a new plugin for the Flarm device. A file export is not
> > supported
> > up
> > to now by other recorder plugins. But because the format is device
> > specific,
> > it makes sense to have this function in the recorder plugin itself. I
> > implemented it as virtual method that is marked "not supported" by the
> > other
> > plugins. Because it works on local file, no actual recorder connection
> > is
> > required. Because the format of the flarmcfg.txt file is similar to the
> > upload
> > data, we can expect to reuse this function.
> Yes that is a good idea to make it in this manner.
> > Currently the file is written to the home directory of the user. But of
> > course
> > we could write it directly to a mounted sd card.
> We can provide a save dialog to the user, that he can select his preferred
> destination for the Flarm file storage.
> > In the user interface, the new plugin appears as recorder type FLarm.
> > The
> > created lib is libkfrfla. The export function is part of the Declaration
> > screen. It is disabled (but visible) for all other recorders. See
> > attached screen shots. The created flarmcfg.txt (zipped) is also
> > attached.
> > Please comment and let me know if this approach is ok for you.
> I think that would be a good enhancement of KFLog.
> > Regards
> > Eggert
> > _______________________________________________
More information about the Kflog-user