[feature request] auto resizing panel

[ghost]

an auto resizing panel with task manager,
so it can be used as a dock.without loosing the icon size when more applications are opened.something like gnomes dash to dock plugin

[tsujan]

In general, "auto-resize" means changing width (height, for vertical panels) to fit to contents, whatever they are, like the notification area. A good auto-resizing implementation also adds a way to scroll the contents in case they are too wide. Possible but not easy.

[antis81]

As far as I understand the documentation a (configurable) "padding" property can help as a first step to better understand the panel layout and define anchor points (-> #1940). In QWidget wording the term "padding" translates to QWidget::contentsMargins(). The schematic drawing from QML's Frame/Control further helps to outline a "predictable" behavior.

@tsujan Apart from some minor open points #1940 is pretty much functional (and independent apart from *.ui file -> other story…). Also to make this interesting for contributors it is quite relevant to split the issue into independent chunks so that we can make this a reality.

FYI:

• The (local) LXQtPanelWidget::geometry() plays a key role in this context and provides the "frame" where panel plugins can happily reside.
• The issue lxqt issue 1553 relates to this one - maybe some others. However as @tsujan mentioned there this describes the current behavior of the application/task plugin (plugin-tray ??) and is in the first place unrelated to "growing" the panel based on its contents.

[stefonarch]

What is needed really here instead IMO is

• plugin-taskbar is autoexpanding like tray is
• panel can be centered and autoexpanding on both sides
• buttons can be pinned in taskbar (merge quicklaunch with it), afaik @gfgit mentioned that with the new taskbar plugin structure this would be achievable)

[antis81]

stefonarch: Icon and font sizes simply ignore their surrounding area (plugin widget). This produces those side effects (icon/font too big/small; appears cut-off). This is "undefined behaviour"…

(also the other way round: especially for text it is desired that the plugin widget grows according to it's content)

see comment in padding PR