Project

General

Profile

Feature #1116

feature request: miniview mode with QT or GTK interace

Added by Andrea Antolini 7 months ago. Updated about 1 month ago.

Status:
New
Priority:
Minor
Assignee:
-
Category:
-
Start date:
July 05, 2021
Due date:
% Done:

0%

Estimated time:
Affects version:

Description

Just an idea about to have a sort of "miniview" mode with QT or GTK interface.

See attached imaage as example..

Should be activated/deactivated by a double click on infobar (and/or using a keyboard shortcut) when it is enabled..

Regards
Andrea

audacious_minimode.png (848 KB) audacious_minimode.png miniview Andrea Antolini, July 05, 2021 04:57

History

#1 Updated by Jim Turner 6 months ago

That sounds like a neat idea, but I'd like to propose a slightly different (easier?) way to implement:
Make this part of the window "dockable" to the bottom of the main window, without a titlebar (which should avoid having to duplicate that part or add menu to revert, etc). Then to achieve the requested effect, one could undock it and then minimize/iconify the main window leaving only this window visible. If leaving the main window up, undocking should cause the playlist to fill in the freed space. What do y'all think?

Regards,

Jim

#2 Updated by IFo Hancroft 3 months ago

Here's another way this can be achieved:

Add the following two options under View:
- Hide Playlist
- Hide Controls

There are already options to hide the menu and the status bar, so you will just hide the Menu, Playlist, Controls and Status bar and enable Info Bar, Info Bar Album Art and Info Bar Visualization.

The window's titlebar (the one with the song/player name and close/etc buttons) is in the domain of the window manager, so the player shouldn't have to handle it.

#3 Updated by Jim Turner about 1 month ago

Trying to set up hiding/showing all those other elements seems really complicated (expecially if user has plugin windows docked). I decided to go ahead (this was a good, fun project/prog. exercise for me) and implement this the way I suggested by creating a new "Mini-Audacious" (general) plugin that instantiates the Info Bar into a standalone, dockable window, after which, you can minimize or hide the Qt main-window. A script using "audtool" could invoke+hide main window in one step (but "hiding" seems to cause focus/keyboard bindings to not work) so minimizing pbly. best.

Invoking the plugin (either via double-click on infobar or via Plugins.General settings screen) will automatically hide the classic info bar (and restore it if visible when invoked, when closed). If not hidden (and plugin not docked), main-window remains same size & playlist expands to fill the extra space. Plugin can be docked above or below playlist in main window (but fills window horizontally - some may like this effect). I've also added the playlist (+ volumme control) keyboard bindings (and focus) to plugin window for basic playback manipulation. Esc. closes plugin & Ctrl-Q will close "Audacious". It even seems to work in the skins-Qt interface too. You may have to drag the right-side to expand it the first time you invoke & undock it though (I may need to add a default width perhaps) but Qt generally remembers undocked window-sizes.

Only thing I couldn't do (after much T&E) was properly remove the Qt-supplied titlebar & caused other issues, makes it undockable via dragging, and seems to annoy the window-managers I tried.

Anyway, see my GIT (https://github.com/wildstar84) if you want to give it a try - it's an Audacious fork that I've added many features to over the years and also use for trying things out b4 sending pull-requests to Audacious (see site/notes/FAQ/instructions/latest commit there). You can build it from source+install it w/o affecting Audacious or it's configuration. Email me (in my profile) if you have questions regarding that. If you can try it & everything seems to work ok, let me know & I can pbly. cobble together an Audacious pull-request. For now, it's Qt-only (GTK looks to be more challenging) for now (and I currently use the Qt interface), but I'm liking this idea/feature so far! I seem to recall that Ariadne Conill (I think) created a new interface plugin proposal awhile back for similar reasons, but I can't seem to find any reference to that proposal now.

Regards,

Jim

Also available in: Atom PDF