ia: Benvenite! In mi blog io scribe in interlingua, italiano e anglese.

it: Benvenuti! Nel mio blog scrivo in interlingua, italiano e inglese.

en: Welcome! In my blog I write in Interlingua, Italian and English.

How to be an awesome member of the Free Software community

No, this is not a tutorial, unfortunately. The main reason being that, while I strive to do my best, I don't consider myself to be an excellent member of the Free Software community, let alone be able to teach others about it. But this morning I got an email from the FSF about a campaign for St. Valentine's day, which reminded me of something I've been planning to do since a long time ago, but never got to it.

Love

I want to publicly send huge thanks to Robin Mills from the Exiv2 project, and not only because I've been fruitfully using his work in three (!) projects of mine (PhotoTeleport, Mappero Geotagger and Imaginario), but also, and especially, for being an extremely pleasant interlocutor. On the web, yes. Whereas most people tend to be more thorny and touchy in their interactions over the internet, Robin has always been friendly and coversational, trying to form a bond with some complete foreigner who just happened to report a bug on Exiv2.

Just adding some bits of information about one's personal events (such as travels) can make an enormous difference on how one's attitude is perceived. Mentioning that you visited the place that is familiar to the bug reporter almost makes one forget of being sitting in front of a computer on the internet, because your mind flies to that place. Considering that even on this personal blog of mine I'm kind of reticent about speaking of my private life, I cannot help appreciating the friendly attitude that Robin reserves for people writing on a bug tracker.

You are a wonderful netizen, Robin. A happy Valentine Day to you and your family. Thank you.

Invoking a C++ function from QML, asynchronously

In the Imaginario code I had written a C++ method to find all files present in a directory tree (for some reason this code is always encoding file paths as QUrl, but feel free to ignore that):

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
QList<QUrl> Utils::findFiles(const QUrl &dirUrl, bool recursive) const
{
    QList<QUrl> files;

    QDir dir(dirUrl.toLocalFile());
    if (Q_UNLIKELY(!dir.exists())) return files;

    auto list = dir.entryInfoList(QDir::NoDotAndDotDot |
                                  QDir::Dirs | QDir::Files,
                                  QDir::Name);
    for (const QFileInfo &info: list) {
        if (info.isDir()) {
            if (recursive) {
                files += findFiles(QUrl::fromLocalFile(info.filePath()), true);
            }
        } else {
            files.append(QUrl::fromLocalFile(info.filePath()));
        }
    }

    return files;
}

The Utils mentioned in this snipped is a QObject-derived class which is registered to QML as

1
2
3
4
5
6
7
8
static QObject *utilsProvider(QQmlEngine *, QJSEngine *)                                               
{                                                                                                      
    return new Utils;                                                                                  
}

...
// In some other part of the code, before entering the main loop:
qmlRegisterSingletonType<Utils>("Imaginario", 1, 0, "Utils", utilsProvider);

This allows me to call the C++ findFiles() method from QML, like this:

1
2
3
4
import Imaginario 1.0

...
    onClicked: importer.addFiles(Utils.findFiles(folder, true))

So far, so good. However, I couldn't help noticing that when the selected folder contains a large number of files, the whole UI freezes until the findUtils() method has returned. So, how can I invoke my C++ method without blocking the UI?

QML offers a WorkerScript element which seems to do exactly what we need, but unfortunately the possibility of invoking C++ code is only there since Qt 5.12 (before that version, worker script could not use import statements), and in any case the requirement to store the script into a separate Javascript file makes the code less readable.

A better option, in my opinion, is to write a C++ method that performs the lengthy task in a thread and invokes a Javascript callback once the job execution is completed. This sounds pretty complex at first, but fortunately Qt's nice APIs make this an almost trivial task. Without modifying our previous findFiles() method, we write a second one which will execute it in a thread, using QtConcurrent::run():

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
void Utils::findFiles(const QUrl &dirUrl,
                      bool recursive,
                      const QJSValue &callback) const
{
    auto *watcher = new QFutureWatcher<QList<QUrl>>(this);
    QObject::connect(watcher, &QFutureWatcher<QList<QUrl>>::finished,
                     this, [this,watcher,callback]() {
        QList<QUrl> files = watcher->result();
        QJSValue cbCopy(callback); // needed as callback is captured as const
        QJSEngine *engine = qjsEngine(this);
        cbCopy.call(QJSValueList { engine->toScriptValue(files) });
        watcher->deleteLater();
    }); 
    watcher->setFuture(QtConcurrent::run(this, &Utils::findFiles, 
                                         dirUrl, recursive));
}

You might be surprised, but this is all what is needed in the C++ side. The changes to the QML side are equally trivial:

1
2
3
4
5
6
7
8
import Imaginario 1.0

...
    onClicked: {
        Utils.findFiles(folder, true, function(files) {
            importer.addFiles(files)
        })
    }

That's it! Line 6 in this last snippet will be invoked once the findFiles() method has completed its execution, and you'll be glad to see that the UI will be responsive throughout the duration of the operation.

QtConcurrent alternatives

QtConcurrent::run() is very simple to use, but it's not without its shortcomings, the biggest of which is that it doesn't support cancelling. This is something I can live with in this particular case, but, if you can't, don't despair: there are other options. The second simplest one is probably the static QThread::create() method, which behaves similarly to QtConcurrent::run() but returns a QThread object which can be requested to terminate, for example with QThread::requestInterruption(). This method exists only since Qt 5.10, and that's why I didn't list it as my first choice; but if you are using such a recent version of Qt, then it's probably the best option, because one doesn't even need to subclass QThread (and there's no need to depend on QtConcurrent). Of course, subclassing QThread is also an option, but this involves a little more typing.

Beware of threading issues

The most tempting solution (and I confess, my first approach to the problem was exactly this) is to invoke the Javascript callback directly from the thread:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
void Utils::findFiles(const QUrl &dirUrl,
                      bool recursive,
                      const QJSValue &callback) const
{
    QtConcurrent::run([=]() {
        const QList<QUrl> files = findFiles(dirUrl, recursive);
        QJSValue cbCopy(callback);
        QJSEngine *engine = qjsEngine(this);
        cbCopy.call(QJSValueList { engine->toScriptValue(files) });
    });
}

However, this will work 95% of the times only, because QJSValue::call() is not thread-safe, and therefor your application will be victim of random crashes. So, we need to write a couple of lines more and invoke the callback from the main thread, like I'm doing before.

The Lego Movie 2, un surprisa positive

Heri io e mi sponsa ha accompaniate mi filios al cinema, pro guardar le film "The Lego Movie 2". Isto es un film de animation tridimensional que, como le titulo suggere, narra le aventuras de nostre amate minifiguras Lego.

Le trailer del version italian del film

Il es possibile que isto sia causate da mi basse expectationes, ma io confessa que le film me placeva multo, e in alicun momentos esseva multo plus profunde de altere filmes mirate a un publico plus adulte. E a iste puncto io vos consilia de stoppar le lectura de iste entrata, si vos plana de guardar le film: io va revelar alicun partes del historia, e si vos non vole que vostre surprisa sia guastate, stoppa de leger me hic.

(A iste puncto uno poterea demandar se qual es le senso de parlar vos de iste film, viste que illo obviemente non es interessante pro vos; ma io non va poner me iste question, e continua.)

Lo que plus me colpava es un drammatic colpo de scena (inexpectate inversion del eventos) que mirabilemente presenta un confusion del conceptos de bon e perfide: in breve, isto occurre quando Emmet, le protagonista, es sur le puncto de liberar su amate Lucy e altere su amicos qui esseva captivate per le folle e perfide habitantes de un planeta lontan. Il es in iste momento, que Lucy comprende que illes non del toto es folle e perfide, ma sinceremente amicabile; illa comprende que illa esseva victima de un mal comprension causate per su prejudicios, e alora illa cerca, inutilemente, de convincer Emmet a abandonar su plano de destruction de iste population extra-terrestre.

Iste momento es terribilemente actual, mesmo in le terminologia usate, quando Emmet accusa Lucy de haber essite le victima de un lavage del cerebro (anglese: brainwashing) que la impedi de vider le realitate, sin realisar que il es proprio ille, le qui ha un vision completemente distorte del realitate e ha totalmente invertite le conceptos de ben e mal.

Iste passage ben describe le problema del incommunicabilitate inter personas qui ha ideas opposite e qui es profundemente convincite que le altere non comprende, e que nos ha le mission de portar le al veritate. Un tema que es sempre actual, e jammais solvite.

Complexivemente, le film es multo agradabile, con multe action, un poco de comicitate, e anque alicun momentos multo toccante emotivemente — benque isto pote esser causate del facto que io, in guardar le film con mi filios, empathisava con illes e projectava super me lor emotiones (o melio: lo que io imaginava esser lor emotiones). Un hora e medie que io non regretta haber passate in le cinema!

Imaginario coming to Windows and MacOS

Good news for the intrepid photographers! Imaginario is now available for Windows and MacOS — in addition to Linux, of course. Don't believe me? Here's a couple of screenshots, then:

Imaginario on Windows

(click on the image to enlarge it)

Imaginario on MacOS

Of course, this does not mean that I'm inviting everyone to start using it: Imaginario is still alpha quality. While it shouldn't just randomly delete your photos, there are many rough edges here and there, so use it with extreme caution.

Still, I'll appreciate if someone having access to these capitalistic operating systems could give a quick try to Imaginario (you can download it from here) and let me know if it starts at all. In case you wish to further explore it, you'll unavodably stumble upon a lot of bugs; you can also let me know about them.