Tag Archives: Desarrollo - Page 2

Kontest 0.0.2-alpha (Qt4 backport) windows installer

I think I have it.

I have fixed the bug in the windows installer package of Kontest.

The package showed an error “Driver not loaded” just when the database was created so, thanks to Google I found the fix in the great stackoverflow.

So, in a few words, just add a sqldrivers folder and copy the qsqlite4.dll file in it before creating the package and you will have it!

I have done some (just a few, to be honest!) tests in a clean windows virtual host and it worked like a charm so I hope it is OK for most of the systems out there.

You can find the file http://sourceforge.net/projects/kontest/files/ in the same place as the previous days.

As always, thank you for testing and sending the bug reports!


Kontest 0.0.1-alpha or KLog 1-alpha: New alpha release

I have rewritten completely KLog into a new software, Kontest. The name is something still to be defined so if you have any preference, please tell me what you think! Today it is called Kontest, because I wanted to give KLog contest capabilities.

Today, let me call KLog to the previous software and Kontest to the new one, so we can understand each other. 🙂

What’s new with Kontest?

My first intention was to provide all the functionalities of KLog into Kontest, before releasing, to try to avoid the maintenance of two different software packages, however, there are some differences:

  • The main difference between KLog and Kontest is that Kontest can be run in Linux, OSX and Windows.
  • Kontest uses an sqlite database and can be executed in memory or in a file, providing speed or security of your data, you choose!
  • Kontest has an improved GUI, with some more fields to manage data.

What about the contest capabilities?
Even ifKontest has been designed to allow an “easy” integration of new contest from the developer point of view although today it is not supporting ANY contest…

My intention was to provide all the KLog functionalities first, and once the day-to-day logging is working as KLog, I will start working on the contest capabilities.

What can I do now?

  • First of all, remember that this is an ALPHA release so it may (I should use will) have many bugs. Don’t trust this software to be your only logging software (yet) and know that you can loose your data!! I am just releasing this version because I believe in the RERO development philosophy.
  • Join the mailing list. We will use the KLog’s mailing list. So please, subscribe and send all the bugs and suggestions you have.
  • Help with the development. You can join me to create the best multiplatform hamradio logging software we can.

So, how can I download Kontest?

Today, you can only download Kontest from Sourceforge.

Check the following link for the downloads:


That’s all.

Again, don’t hesitate to report any bug and/or suggestion you may have.

I hope you will enjoy Kontest!

KLog 0.6.1 – released: Another bugfix release

As I told you some months ago, I keep rewriting a new software… but my free time is close to zero 🙁 sometimes code some lines but my time in radio is mostly spent in the radio 🙂

However… yesterday I was DXing in 50Mhz and I noticed that the bearing was not correct and the coding-virus made me fix the bug ASAP.

So … here is the data of this new release:

Download KLog 0.6.1 from:

The Debian package has been already uploaded to the Debian servers.

This releases has the following Changelog:

June – 2013 – 0.6.1

  • Bug fixed: Locator was not properly calculated due to a sign difference management from KLog and CTY.DAT.
  • GUI updated: The cursor position management of the QRZ box has been improved to ease the operation.

As always, KLog is available in English, Spanish, Portuguese, Brazilian Portuguese, German, Serbian, Galician and Swedish.

Thanks for your help and I hope you find KLog useful.

KLog 0.6.0 released… 10 years of KLog and some news…

KLog is now 10 years old!! Wow time goes really fast! 🙂

Last release of KLog was one year ago… and this release is not adding many things… Bug fix as last one.
However… does it mean that KLog is dead?
Not it is not. 🙂

During this time I have been rewriting ALL KLog and now, the new software can be compiled for Windows and (probably) OSX (although I have still not tested OSX).
Of course… the new code will be released for Linux, as today !!
The idea behind this is making available the free software I am doing for more hams.

Read more »

KLog 0.5.9 released

Christmas holidays is always a great time for some coding 🙂 so I found some time to fix two bugs (this one and that one) that were reported just after the announce of KLog-0.5.8 … and as Eric S. Raymond says in The Cathedral and The Bazaar, I release early, release often Read more »

KLog 0.5.8 released

I am  happy to announce that the release of 0.5.8 version of KLog is available.

Download KLog 0.5.8 from: https://jaime.robles.es/download/klog-0.5.8.tar.gz

or from the new site of KLog in Savannah :

The Debian package will be uploaded to the Debian servers during the following days. Read more »

KLog 0.5.7 released

It’s time for another KLog release.

KLog 0.5.7 is not a very big release… but it comes with some additions that may be nice for some of you. As I was announcing in my previous post about KLog.

I have added a very basic function capable to export all the needed QSO that has not been QSLed to a file… that can be imported to a label software to create the labels for the QSLs. I will continue working in the label generation feature of KLog for next releases.

The Changelog for this release reads as follows:

November-2010 0.5.7
– New feature: Added the Export needed QSL that allows to create an ADIF file with all the QSO with new ones and new bands still not confirmed that has not been QSLed.
The objective is to export it to a QSL or label printing software (until KLog implements that feature).
– Updated translations: SV by SM4ABE.
– GUI improved: Added sliders to be able to move panels.
– GUI improved: Changing the band combobox changes the TX Freq box and viceversa.
– Minor fix: The PROGRAMVERSION tag in log was not properly formated.

You can download KLog 0.5.7 from the mainsite.
You can also have more information in the main page of KLog or following the KLog’s tag in this blog.

KLog is free and open software and you can join the KLog’s team if you wish to help the development.
Please, send me all the bug reports and suggestions you have to improve KLog!

I hope you will like KLog.

KLog updates

It’s been a long time since I published new information about KLog in this blog but KLog’s development has not been quiet.

Since the bug warning of KLog 0.5.3 I have released once each two months.

KLog 0.5.4 came during March as you can see in the announce of KLog 0.5.4.

It was mainly a bug-fixing release as you can see the the changelog:

March-2010 0.5.4
- Small fix to initialize a variable before using it.(realTimeLog in klog.cpp)
- Fixed a bug that caused KLog to crash of no cty.dat file was found (bug #016917)(TNX KA6MAL)

During April I released KLog 0.5.5 with a two interesting features (yes, the changelog shows three but for the user it would seem as just two):

April-2010 0.5.5
- New feature: If cty.dat file is not found, KLog offers to download from the web.
- New feature: New tool to update the update the cty.dat file from the web.
- New feature: QRZ font color changes to red if has been worked previously. (Proposed by KE7TDY)

I think it will improve the easy of use of KLog. Next phase would be to check if there is a new version of the cty.dat file and propose to download it.

And we get to July, when I released KLog 0.5.6, a minor release in terms of usability, not important KLog’s sources bugs solved, but definitely an important release as it has improved the way it manages how the compilation process manages the hamlib sources, and has ended with KLog in Fedora 🙂

From the Changelog:
July-2010 0.5.6
- Fixed the hamlib compilation scripts (CMakeLists.txt, FindHamlib.cmake). (TNX AB4BD).
- Fixed one bug that causes some architectures not to compile.
- Fixed some permisions and other warnings for Fedora packaging. (TNX N3LRX).

Now I am working in KLog 0.5.7 and I hope it will be ready for release soon. I am working in a new tool of KLog that will export the QSOs that are still needed and we still have not sent the QSL card so that log can be imported in a label printing software to print the labels and send ALL the QSL cards easily.
I will export an ADIF file and maybe a CSV file to be imported into GLabels.

The proper way to go would be to create a label printing feature but it is a longer process and I wanted to speed up my own QSL card process 🙂

While new release is ready: download KLog

KLog 0.5.2 and KLog 0.5.3

During the last weekend I released KLog 0.5.2 and KLog 0.5.3.

Do you think that there is no reason for two releases during the same weekend?

Release early, release often isn’t it enough?

Well, I released KLog 0.5.2 on Friday night with the following Changelog:

February-2010 - 0.5.2
- Fixed a bug that causes a crash when connectiong to DXCluster. (bug #016653)
- Added a very basic Satellite support.
- Removed the Freq LCD and added two new editable widgets: Freq TX and Freq RX. (bug #016609)
- Added again the entity count of /M stations.

The main thing of 0.5.2 is the correction of a bug that caused KLog to crash when special strings arrived from the DXCluster.

Just some hours after 0.5.2, I released KLog 0.5.3 with the following Changelog:

February-2010 0.5.3
- Fixed a bug that caused modified QSO not being updated.
- Fixed a bug in the way the band & mode combobox managed the data.

The reason for that was that I discovered another bug in the modifying procedure of KLog that may cause QSO not to be properly updated.

Anyway, I also updated the Debian package of KLog.

The next steps for KLog includes:

Download KLog from any of these URL:

I am thinking about porting KLog to Windows in order to be able to reach to more users and maybe attract more developers to add more features and accelerate the KLog’s development.

Do you want to help KLog?

Fin de una etapa: Hasta luego KDE-ES.

Hace unos días envié un mensaje a la lista de correo electrónico del grupo de traductores de KDE al español, KDE-ES.

Básicamente y para ahorraros la lectura del mensaje, en él presentaba mi ¿dimisión? ¿renuncia? o no se cómo decirlo, básicamente anunciaba que dejo la coordinación del equipo, exponía algunas de las razones que me han llevado a tomar esta decisión y proponía un plan para elegir al nuevo coordinador así como también presentaba como candidato a Eloy Cuadra, que creo que es una persona preparada, que conoce perfectamente la forma de trabajo del equipo y que lo hará MUY bien.

No me he cansado de traducir… es algo que llevo haciendo, yo diría que por lo menos unos 12 años y probablemente lo siga haciendo pero, entre unas cosas u otras ya no tengo el tiempo para dedicarle a KDE-ES todo lo que necesita (que dicho sea de paso, tampoco es tanto) así que antes de seguir ocupando un puesto sin poder subir las traducciones de los compañeros con la celeridad que requiere, sin atender a los recién llegados todo lo bien y rápido que me gustaría o sin mantener al día mis traducciones del paquete KDEBase, … antes de llegar a ser un lastre para el equipo, prefiero apartarme a un lado y dejar que otra persona coja el relevo y pueda seguir tirando y que KDE-ES siga creciendo y haciendo un trabajo tan bueno como el que ha hecho hasta ahora.

Hay que decir que el grupo de KDE-ES es un grupo de traductores MUY válidos, que trabajan a tope siempre que hace falta y consiguen que los usuarios de habla hispana de KDE dispongan de un sistema en español, con una calidad de las traducciones yo diría que bastante buena, superior en muchos casos a las traducciones de muchos programas propietarios y de pago.

Ahora y… desde la distancia se me ocurre una reflexión: Llevo unos o casi 10 años coordinando el equipo… mi cargo de coordinador parece que era vitalicio.

¿Son vitalicios los puestos de coordinador en los proyectos de software libre? Quiero decir… Siempre se ha dicho que en el software libre es la meritocracia la que ofrece, da y quita el liderazgo de los proyectos.

¿Ocurre realmente así? No se si la gente del grupo LibreSoftware habrán hecho algún estudio al respecto 🙂

Resumiendo y para terminar que me lio a hablar, … en unos días KDE-ES tendrá otro coordinador.

Mucha suerte y a seguir currando!

Este sitio web utiliza cookies para que usted tenga la mejor experiencia de usuario. Si continúa navegando está dando su consentimiento para la aceptación de las mencionadas cookies y la aceptación de nuestra política de cookies, pinche el enlace para mayor información.

Aviso de cookies