FLE Import

[DK1MI]

It would be great to have an import function that allows importing files in FLE (Fast Log Entry) format. I myself like to log in Vim with a syntax highlighting plugin for the FLE format but then have to convert it first into ADIF before importing it into Cloudlog.

SOTA hams seem to also use FLE so they have added a FLE import functionality (see https://reflector.sota.org.uk/t/fast-log-entry-syntax-highlighting-for-vim/33645). This format seems to become more popular.

Thanks and 73
Michael, DK1MI

[HB9HIL]

We will take a look at that. :-)

[phl0]

Could you share the fle plugin for vim or point me to the source?

[DK1MI]

Oh nice! I was not aware of this

[magicbug]

SFLE also exists https://github.com/ok2cqr/sfle

It is a web version.

You beat me to it, its always been an item I planned on integrating but like everything one of many things.

[HB9HIL]

@magicbug I will try to implement that with the help of the rest of the dev guys 👍

[magicbug]

For those waiting DF3CB's FLE app is fantastic for post logging if you have been involved with anyone who paper logs

[DK1MI]

That would be fantastic! Thanks for considering the implementation

[AndreasK79]

@DK1MI the latest dev branch now contains the SimpleFLE code. @HB9HIL did a great job with integrating it. Please test and report back.

[DK1MI]

Excellent! Thank you very much for your work on this. Problem is that I am a simple subscriber and am enjoying the hosted solution so I fear I am not able to test the dev branch.

[HB9HIL]

You can wait for the next release 😎👍

[HB9HIL]

Excellent! Thank you very much for your work on this. Problem is that I am a simple subscriber and am enjoying the hosted solution so I fear I am not able to test the dev branch.

@magicbug just released the new Version 2.5. So you will surely be able to test SimpleFLE 😊👍

[HB9HIL]

@DK1MI Were you able to test SimpleFLE? Could you give any feedback?

[DK1MI]

Sadly not. I cannot find the feature in the hosted version.

[HB9HIL]

Should be in QSO -> Simple Fast Log Entry

[pa3hfj]

Well, I saw the announcement and decided to do a test yesterday and I can say that the new functionality is really a nice addition to Cloudlog! It came in handy for the (long postponed :-) ) task of entering the hand-written logs of my XYL into her newly created logbook in my Cloudlog instance. It saves a lot of time, so thanks for the work on this.

I have just two remarks:

• When you put in the frequency of the QSO's the right band is chosen, but the frequency is not entered in the log, just a 0 is to be seen.
• The date stays fixed, also when a different date is entered in the inputbox. This means that if you have to type over a log with a lot of different dates (as was my case) it takes somewhat more work in the way of some mouse clicks for saving the QSO's and revert to the input task.

But overall, a very nice job!

[HB9HIL]

PS: something like day - is not implemented

[pa3hfj]

Thanks for your answer! A nice "feature" of an online logbook is that you can reach it from work ;-) , so here we go:

1. This is a sample line: "1200 pa1test 3.666 54 56 ssb" I also tried putting the frequency and mode on a first seperate line but that makes no difference.
2. It was indeed a mistake. Because the datebox has the form of dd-mm-yyyy I probably used that format also in the inputbox. I tried it now the other way around yyyy-mm-dd and that works as expected! Maybe a small remark could be added to the Syntax Help window.

73, Wijnand PA3HFJ.

[HB9HIL]

Thanks for your reply. The QRG error will be fixed with the next stable release.

[HB9HIL]

@pa3hfj

The new version was just released. The issues should be fixed now. :)

[pa3hfj]

Thank you Fabian, I can confirm the fix!
73, Wijnand PA3HFJ.

(PS: nice mobile shack on your QRZ page! I own a Land Rover Defender for the same purpose)

[UnicycleDumpTruck]

I love the Simple FLE, thank you for implementing it! I paper log for my POTA activations, and my usual workflow involves double checking the call signs in the QRZ callbook (to make sure the call is valid and that the state/location I copied matches the callsign's default) before or as I enter them into the fast log entry. Is there a straightforward way to have the Simple FLE in Cloudlog look up the entered callsign's location from the Callbook in the preview mode, so I know before adding the full list of QSOs if I have busted calls?

[magicbug]

I'm not sure I'd be relying on QRZ as the total knowledge of the truth but certainly could be looked into as an option