Add Cloudlog integration

[artekw]

It is posible to add export QSO to Cloudlog ?

[foldynl]

Simply, yes, it is possible but question is. Should this be implemented?

Offline sending of messages can be implemented immediately. On the other hand, I don't see any possibility to implement online sending of message to Cloudlog, because Cloudlog has not implemented the Update/Delete operations. So if you edit or delete QSO in QLog, it will not be updated in Cloudlog.

Another very important question is whether Cloudlog should be included in the QLog menu. If so, where is the boundary of which "online" services should be added and which should not. Over time the QLog "Services" menu can expand to several pages.

Currently, you can use QLog's notifications to send messages to Cloudlog online - if someone implements a bridge between Qlog and Cloudlog. But as I wrote, the problem starts when you try to edit/delete QSO in QLog.

It would be great to have a synergy between QLog and Cloudlog for synchronization, but everything is limited by Cloudlog's API.

[artekw]

You are right about Cloudlog API limitations. But what you think about add some button "Export to Cloudlog" or similar ?

[foldynl]

All ends with a button. It's not about whether it will be a button or menu options; it's about whether the function fits into the concept. Let's take a look: LoTW, ClubLog, QRZ.com, eQSL, and HRDLog services are now implemented. These services offer the following features:

1. They provide additional services to operators, which QLog essentially cannot offer (such as QSL services, QSO confirmation, issuing diplomas, etc.).
2. They are supported by ADIF format. This is crucial for exporting/importing QSOs between applications without losing information about whether the QSO has already been sent to the online service or not = QSO Sent status.

I consider these two points crucial for a service to be integrated into QLog. Comparatively, Cloudlog unfortunately does not provide such services. Actually, it is the second application with the same functionality as QLog provides. Consequently, exporting QSOs from one application to another is what you are looking for and QLog already offers this function.

Unfortunately, the Cloudlog's APIs are so simple that it cannot even be said that QLog would gain anything by implementing an interface for Cloudlog. It's a shame that there is no possibility of a "synchronization API". In this case, I believe that QLog would be the first to implement it, because I have many requests for synchronization.

Therefore, I think that at the moment I do not see a sufficient reason to implement it in QLog. Maybe I'm not seeing something what I should know.

[artekw]

Thanks for the clarification. All that remains is to "synchronize" manually until the Cloudlog API is improved :-)

[foldynl]

sorry, additional question for my curiosity. I would like to understand it more. Why should you use two apps that do the same thing? The only difference is online/offline logging. If I have an online log, I don't need offline applications. I would only need this in special cases when I don't have internet and as far as I know, Cloudlog community is already talking about the possibility of offline logging. So why to have both applications?

[artekw]

I find QLog logging friendly, it has everything on one screen (last qso, cluster dx, etc.). But I want to be able to access my journal when I'm away from QTH. Cloudlog is also a backup. All I need is a "dumb" "Export to Cloudlog" button like Log4OM, but I find this program very slow.
I will try to perform such export on my own using notifications.