Gnome Commander

@[email protected]
26 Followers
0 Following
46 Posts
Gnome Commander is a dual-panel file manager. Wladimir Palant @WPalant posting here on behalf of the development team.
Project websitehttps://gnome.pages.gitlab.gnome.org/gnome-commander/
Gnome CommanderJun 14

In order to make viewer’s keyboard shortcuts configurable and Quick View feature realistic I find myself refactoring main window actions, >2k lines of code – again, I’ve already done that four months ago. This is unfortunately an annoyingly common occurrence lately. Prior to Gnome Commander 2.0 release the goal was to make things work *somehow*. Now the goal is getting maintainable and extensible code. And that means revisiting pretty much everything once again.

#GnomeCommander

Gnome CommanderJun 14

Just landed on the development branch: tabbed interface for the internal viewer. Instead of opening ever new windows the internal viewer now keeps everything neatly organized in one window, one tab per file.

The viewer is now a component which can be reused elsewhere. The idea is to implement a Quick View feature: a viewer showing up in a panel, displaying whichever file is selected in the opposite panel. This still requires some refactoring of the panels however.

#GnomeCommander

Gnome CommanderJun 13

RE: https://floss.social/@gcmd/116676361358232158

Gnome Commander 2.0.3 is out, fixing eight annoyances this time. Most importantly, keyboard input focus will no longer be in nirvana after clicking toolbar buttons, and overlong file list contents will be ellipsized rather than cut off. The remaining six issues are evenly split between the Search dialog and the internal viewer.

https://gitlab.gnome.org/GNOME/gnome-commander/-/releases/2.0.3

#GnomeCommander #OpenSource #Linux #FileManager

Show threadGnome CommanderJun 8
@reflex It’s ok for *some* use cases. This just isn’t the one Flatpak was meant for… 🤷
Show threadGnome CommanderJun 7
@reflex As you’ve probably noticed, Flatpak support isn’t going to happen any time soon. But at least I’ve solved the issue with libvte – the latest portable build runs on Zirconium out of the box (at the cost of almost trippling the build size), no more “stealing” the library from another application required.
Show threadGnome CommanderJun 7
Concerning those system libraries: libvte has been an issue for the portable builds so far, the other required libraries being pretty much universally available. So I’ve now managed to package libvte with the portable builds, this should significantly increase the chances of the portable builds just working out of the box.
Show threadGnome CommanderJun 6
@tragivictoria @reflex I now have a better idea of why Flatpak is such a pain: https://gitlab.gnome.org/GNOME/gnome-commander/-/work_items/93#note_2781693 😅
Flatpak build (#93) · Issues · GNOME / gnome-commander · GitLab

Please, consider supporting Flatpak and publishing GNOME Commander on Flathub.

GitLab
Show threadGnome CommanderJun 5

And the portable builds just got a little bit… well, more portable. Our plugins depend on some Python modules, and these modules are now being packaged into the portable builds. So plugins now work out of the box without requiring any changes to the system.

We still depend on system libraries however (essentially Gtk and libvte). It seems that libvte in particular might not be pre-installed. The builds now contain a README file explaining this and listing the distribution packages to install.

Gnome CommanderJun 5

We finally have zero compile warnings, zero clippy warnings and zero documentation warnings in the codebase! 🎉

And to celebrate the occasion CI checks for these warnings have just been added, making sure it will stay this way.

Show threadGnome CommanderJun 3
Either way, we now have this framework which is currently used for the Keyboard Shortcuts dialog but will hopefully be used consistently throughout the codebase at some point. It’s great that Relm4 demonstrates how it can be done better, and I hope that the project will see continued development.