nemo-action-bar: add configurable action bar

[ClaudiuSchuster]

This adds Nemo Action Bar 2.0.0, an independent OSS Singularity Nemo
extension that places configurable native GTK actions directly above Nemo's
directory view.

Nemo Action Bar screenshot — default action bar in Nemo

Maintainer: @ClaudiuSchuster.
Package: nemo-action-bar.

The extension exposes an allowlisted set of Nemo-native actions through a
compact configurable action bar. It supports JSON configuration for button
order, separators, labels, icons, shortcuts and live reload.

Copy Paths copies selected file/folder paths as newline-separated text, or
copies the current local folder path when nothing is selected. Nemo's own
actions and dialogs handle file operations; the JSON configuration does not
execute arbitrary commands.

Requires Nemo with nemo-python support, GTK 3/GObject Introspection bindings
and Python 3. The contribution uses the existing per-project Debian layout of
this repository and is GPL-2.0-or-later.

Only the nemo-action-bar/ project directory plus the required build-order
and Readme.md entries are added. The social preview and screenshot above are
pinned to the public v2.0.0 source commit.

Validation

• python3 -m py_compile and JSON validation pass for the staged sources.
• dpkg-buildpackage -us -uc -b passes in Ubuntu 24.04.
• Lintian reports no findings for the resulting package.
• bash -n build and shellcheck build pass.
• The packaged payload contains only the Nemo extension, configuration, icon
  and Debian documentation; no Python egg-info payload is installed.
• Live Linux Mint/X11 validation with Nemo 6.6.3 covers the current-folder
  fallback with no selection and selected-folder path copying.
• The project PR #2
  passed its protected checks and was squash-merged into main as
  56f0f5f1.
• The public v2.0.0 GitHub Release
  is published from that exact merge commit and includes the Debian package.

Project source and v2.0.0 changes
· v2.0.0 GitHub Release

[mtwebster]

Hi, this looks nice but it's just another way to access actions are already fairly accessible.

• it permanently takes up extra real estate in the file view
• many items can already be added to Nemo's toolbar
• some buttons require a selection, but their state doesn't suggest this (cut/copy should be greyed out if there's no selection, for example)
• the user is required to edit/create a text file to configure this.

The extension system, unfortunately, doesn't really allow for the capabilities something like this would require to be done properly. This isn't really its intention - the interface receives the current location and decides whether or not to show itself. Along the lines of when you open the trash location from the sidebar, a toolbar appears allowing you to easily empty the trash:

This is an interface to allow the provision of a custom location widget embedded at the top
of the Nemo view. It receives the current location, and can then determine whether or not
the location is appropriate for a widget, and its contents.

[ClaudiuSchuster]

Hi, this looks nice but it's just another way to access actions are already fairly accessible.

• it permanently takes up extra real estate in the file view
• many items can already be added to Nemo's toolbar
• some buttons require a selection, but their state doesn't suggest this (cut/copy should be greyed out if there's no selection, for example)
• the user is required to edit/create a text file to configure this.

The extension system, unfortunately, doesn't really allow for the capabilities something like this would require to be done properly. This isn't really its intention - the interface receives the current location and decides whether or not to show itself. Along the lines of when you open the trash location from the sidebar, a toolbar appears allowing you to easily empty the trash:

This is an interface to allow the provision of a custom location widget embedded at the top
of the Nemo view. It receives the current location, and can then determine whether or not
the location is appropriate for a widget, and its contents.

Hi @mtwebster !

Thanks for the detailed response to this (one of my first) extension application.

Understand fully why this PR gets closed - If someone truly wants it - the package is available as release in our org. repository. - JFYI: This here was one of my smalles/simplest extensions - And to speak open - not much 'care' went into it after the functionality was initialy there, compared to later more complex extensions.

Looking forward to provide more usefull quality stuff 😎🌈🫰

Have a good one.
Claudiu