| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
| |
This rewrite is more or less necessary for:
- colour-managed browser thumbnails,
- asynchronous image loading,
- turning fiv-io into a reusable library.
Little CMS has a fairly terrible API in this regard.
|
| |
|
|
|
|
| |
Also make it apparent that CMM profiles are pointer types.
This isn't all that pretty, but it's a necessary first step.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
With the shift from cairo_surface_t, we've lost our ability
to directly render vector surfaces, but it doesn't matter.
|
| |
|
|
| |
This commit temporarily breaks multi-page images and animations.
|
| | |
|
| | |
|
| |
|
|
| |
Make use of LibRaw 0.21.0's extended thumbnail API.
|
| |
|
|
| |
Don't go over the same data twice.
|
| | |
|
| |
|
|
|
|
| |
Unless there is a writer, this may block forever.
And if there is one, we're somewhat likely to break something.
|
| |
|
|
|
| |
The sanitizer would scream, and LibRaw would rather confusingly
return I/O errors.
|
| |
|
|
|
| |
LibRaw started returning the largest possible thumbnail,
which in the case of NEFs may be a nearly full-scale image.
|
| |
|
|
|
| |
In particular, this handles screenshots from Rigol oscilloscopes,
which reuse the same name series with the same file modification time.
|
| |
|
|
|
|
|
|
|
|
|
| |
This makes use of our image processing capabilities in order to
turn arbitrary image files into normalized thumbnails,
upload them to a temporary host, and pass the resulting URI
to a search provider.
In future, fiv should ideally run the upload itself,
so that its status and any errors are obvious to the user,
as well as to get rid of the script's dependency on jq.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implement a process-local VFS to enable grouping together arbitrary
URIs passed via program arguments, DnD, or the file open dialog.
This VFS contains FivCollectionFile objects, which act as "simple"
proxies over arbitrary GFiles. Their true URIs may be retrieved
through the "standard::target-uri" attribute, in a similar way to
GVfs's "recent" and "trash" backends.
(The main reason we proxy rather than just hackishly return foreign
GFiles from the VFS is that loading them would switch the current
directory, and break iteration as a result.
We could also keep the collection outside of GVfs, but that would
result in considerable special-casing, and the author wouldn't gain
intimate knowledge of GIO.)
There is no perceived need to keep old collections when opening
new ones, so we simply change and reload the contents when needed.
Similarly, there is no intention to make the VFS writeable.
The process-locality of this and other URI schemes has proven to be
rather annoying when passing files to other applications,
however most of the resulting complexity appears to be essential
rather than accidental.
Note that the GTK+ file chooser widget is retarded, and doesn't
recognize URIs that lack the authority part in the location bar.
|
| |
|
|
|
|
|
|
| |
Linux has st_mtim (and an st_mtime macro),
macOS has st_mtimespec (and an st_mtime macro),
Windows has just st_mtime.
GFileInfo would be another option, though it seems unnecessary.
|
| | |
|
| |
|
|
| |
Otherwise the UI would become unresponsive during loading.
|
| |
|
|
|
| |
Only use LibRaw for now, which probably has the most impact
using the least amount of effort.
|
| |
|
|
| |
Use gchar when memory is allocated through GLib.
|
| |
|
|
| |
Thumbnails can be properly loaded using Wuffs now.
|
| | |
|
| |
|
|
|
| |
Saves a syscall, generalizes fiv_thumbnail_lookup(),
wastes a tiny bit of memory per entry.
|
| |
|
|
|
|
|
|
| |
They fell back to gdk-pixbuf, then misrendered in the thumbnailer,
and crashed the program when loaded directly.
The second best we can do is scale them down, right after tiling,
which is a complex feature to add.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
And speed up thumbnailing of animated images while at it.
Also, fix thumbnailing SVGs with external links.
|
| | |
|
| | |
|
| |
|
|
| |
They're not loaded as image surfaces.
|
| | |
|
| | |
|
| |
|
|
| |
Now we're able to make use of GVfs, with some caveats.
|
| | |
|
| | |
|
|
|
And clean up identifiers.
|
