Size of file in bytes in Nautilus

We have one now :slight_smile:

It uses GThreadPool, so calculations are made in parallel and the extension is non-blocking.

@antoniof

This is the first time I use the new NautilusPropertiesModel and NautilusPropertiesItem objects. I have two thoughts:

  1. If a file is particularly big I wanted to show the “Calculating…” content until the calculator thread terminates the computing and finally replace it with the checksum, but NautilusPropertiesItem:value is construct-only, and so the only thing I can do with big files is showing an empty window until the checksums are ready. Do you think it could be possible to remove G_PARAM_CONSTRUCT_ONLY from NautilusPropertiesItem:value and update the API accordingly?

(With very big files the window gets populated after a few seconds)

  1. In my opinion this is linked to what I was saying in this post, i.e. that it is not needed to move the extension API to a separate process: when something works better asynchronously – like this case of checksums – developers already know how to start new threads/processes, and will do that on their own.

My two cents

―madmurphy