Re: [Klog-devel] Klog-devel Digest, Vol 2, Issue 2

[Andrew Goldie]

On Mon, 05 Oct 2009 23:01:32 address@hidden wrote:
> Send Klog-devel mailing list submissions to
>       address@hidden
>
> To subscribe or unsubscribe via the World Wide Web, visit
>       https://lists.berlios.de/mailman/listinfo/klog-devel
> or, via email, send a message with subject or body 'help' to
>       address@hidden
>
> You can reach the person managing the list at
>       address@hidden
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Klog-devel digest..."
>
>
> Today's Topics:
>
>    1. Load and Save (Andrew Goldie)
>    2. Re: Load and Save (Jaime Robles)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 5 Oct 2009 08:54:37 +1200
> From: Andrew Goldie <address@hidden>
> Subject: [Klog-devel] Load and Save
> To: address@hidden
> Message-ID:
>       <address@hidden
>netsolutions.co.nz>
>
> Content-Type: text/plain;  charset="us-ascii"
>
> Hi Jaime,
>
> Over the weekend I had some fun in the Oceania DX contest and heres what
> happened!
>
> Since I didn't have a contest logging program for Linux I used Klog 0.4.6 -
> the version I added the contest extra code to.
>
> This worked fine for a little while until I shut down Klog and tried to
> load the contest log I had just saved. This didn't work for some weird
> reason. So I thought "easy I'll just edit the code and recompile".
> Unfortunately having upgraded to KUbuntu 9.04 which uses KDE4 the QT3
> libraries weren't there - no problem I just installed them . But I still
> couldn't get klog-0.4.6 to compile - something to do with looking for KDE
> libraries  - probably version 3.x ones.
>
> So to cut a long story short I quickly had to find another contest logging
> program for Linux. I then stumbled across one called QLE
> (http://home.kpn.nl/w.knol18/qle/qle.html - This was written by WIlbert
> Knol who used to belong to our local radio club before he shifted back to
> The Netherlands). After some fairly quick, although that easy,
> configuration I was up and running again.
>
> I mention this because QLE uses a SQLlite database back end to save it's
> data in. Would it be worth considering using a database to store the Klog
> data in as opposed to the QSO class? It would mean some rewriting of the
> code but it would take away the hassle of looking after what could become a
> big in memory QList of QSO's. It would also mean that all QSO's are
> automatically saved when they are created - this would making the saving
> and loading not needed.
>
> What do you think?
>
> Andrew
>
>
> Attention:
> This email may contain information intended for the sole use of
> the original recipient. Please respect this when sharing or
> disclosing this email's contents with any third party. If you
> believe you have received this email in error, please delete it
> and notify the sender or address@hidden as
> soon as possible. The content of this email does not necessarily
> reflect the views of Solnet Solutions Ltd.
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 5 Oct 2009 10:02:34 +0200 (CEST)
> From: "Jaime Robles" <address@hidden>
> Subject: Re: [Klog-devel] Load and Save
> To: address@hidden
> Message-ID:
>       <address@hidden>
> Content-Type: text/plain;charset=iso-8859-1
>
Hi Jaime,

> Hello Andrew,
>
> > Since I didn't have a contest logging program for Linux I used Klog 0.4.6
> > the version I added the contest extra code to.
>
> I think we could think about the contesting features carefully... It may
> worth it as I don't know any contest software for linux that is updated
> and works ok.
> Do you know N1MM? A windows software with a lot of good features.
I have used a couple of other contesting software programs on windows and they 
are very good but unfortunately (or fortunately) my main PC in a Linux one!

>
> > This worked fine for a little while until I shut down Klog and tried to
> > load
> > the contest log I had just saved. This didn't work for some weird reason.
>
> Strange... I am still using klog 0.4.6 for my "stable" hamradio operation.
Yes it was to do with my upgrading to KDE4 and having QT3 stuff unavailable. 
My klog executable was compiled on my previous version of Kubuntu.

>
> > in. Would it be worth considering using a database to store the Klog data
> > in as opposed to the QSO class? It would mean some rewriting of the code
>
> When I started KLog I considered using a DB to save the QSOs.
> The reason for discarding that option was to make KLog as much
> "independant" of other software as possible and avoid all the
> configurations problems for the users as possible.
Yes this is true but I was perhaps thinking of a DB linu sqllite ot Berkley DB 
with is really just a set of libraries available on most Linux boxes. Or this 
could be statically linked to the executable.

I would have still imagined that the database stuff would not be configured or 
seen by the users.
>
> Moreover, another "feature" I am thinking for next releases of KLog (it is
> still in the thinking-phase) of adding MS Windows support to KLog. That
> way we could get many new users among the ham radio community.
> KLog would:
>  1.- be available to more users.
>  2.- be a way to show&promote free software and KDE to MS Windows.
Yes this fairly easy with a straight QT project, I have done it a few times. 
In fact all that has to be done to run is for it to be compiled on a windows 
box and a small DLL included with the exe file.

The problem with KLog is that it includes some KDE and possibly some hamlib 
stuff that will not compile on windows.
>
> > would take away the hassle of looking after what could become a big in
> > memory QList of QSO's.
>
> Today I am working flawlessly or at least without noticing load with a log
> with more than 10.000QSO.
> I have done testings with BIG logs (100K) and it works ok and I don't
> think people works with logs so bigs! X'DDD
>
> >It would also mean that all QSO's are automatically saved
> > when they are created - this would making the saving and loading not
> > needed.
>
> Here you are right and I have to agree.
> However that is the reason of creating a temp file with the log diff. I
> suppose you have seen that now, KLogs creates a temp file with the QSOs
> added between saves so no QSOs are lost in case of an unexpected
> exit/crash.
>
> Maybe we should rework this way of autosaving if you think it is not
> working well.
>
I see that you are using a QTreeWdiget as the main display widget, can I ask 
why you chose that over a QTableWidget which has a few more functions that 
would make some stuff a little bit easier?
>
> Anyway, did you noticed any problem with berlios.de connection this
> weekend? I tried to connect to update the SVN and I was not able to do it.
> I also tried to connect to developer.berlios.de without success...
Yes I did, I thought my account was broken!




Attention:
This email may contain information intended for the sole use of
the original recipient. Please respect this when sharing or
disclosing this email's contents with any third party. If you
believe you have received this email in error, please delete it
and notify the sender or address@hidden as
soon as possible. The content of this email does not necessarily
reflect the views of Solnet Solutions Ltd.