Bug 327630 - Request for Tab Groups with bookmarks
Summary: Request for Tab Groups with bookmarks
Status: RESOLVED INTENTIONAL
Alias: None
Product: kwin
Classification: Plasma
Component: window-tabbing (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-15 00:52 UTC by andy_90254
Modified: 2016-08-29 06:45 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andy_90254 2013-11-15 00:52:32 UTC
I love the "Attach as tab to" feature.  Couple of things.... 1) it only seems to be available with the Oxygen theme.  2) and more importantly... I would like to request the following enhancement.  Right now I attach several "notes" (usually Everpad since Knotes is too buggy to be usable) to my softphone (sflphone) using the "Attach as tab to" feature.  It takes some time to seek out and attach the right set of notes.  The problem is that I have to reattach this same group of notes on a semi-regular basis - for example if I have to shut something down like either the computer or the softphone, or everpad crashes or whatever.  

Here's what I would like to see - a way to bookmark a group of tabs independently... in a manner similar to the way chrome and/or firefox does grouped tabbing.  That way, I only need to reference a single bookmark to have all my tabs attach where I want them.  Even better, a self-recovery so that when I reopen whatever crashed the tabs reassert themselves.  Both options would of course be best.

Reproducible: Always
Comment 1 Thomas Lübking 2013-11-15 01:00:12 UTC
"kcmshell4 kwinrules", 3rd tab "arragement and access", "autogroup by id"?
Comment 2 andy_90254 2013-11-15 10:58:15 UTC
Thank you for your response.  After some research I was able to determine that right-clicking on the top bar of a window gets you, via "More Actions", to the Window Manager settings.  

From there you go to the very last item on the left hand side menu and click on "Window Rules".  From there, you can select either "Application Settings for XXX" or "Window Settings for XXX". Where XXX is the application that's running that you want to have tabbed groups for.  Select either one, and then select "Modify".  

Alternatively you can also get to these windows simply by right clicking as explained above and then to "More Actions", and then selecting "Special Application Settings..." or "Special Window Settings..."

Selecting either of these then lets you access the "3rd tab" you mention above, which then leads you to "autogroup by id".

Is this what you mean?

Once at that point, there is a dropdown menu with 3 choices.  "Do Not affect", "Force" and "Force Temporarily".  Do I want "Force" ???

Thank you
Comment 3 Thomas Lübking 2013-11-15 13:41:57 UTC
> Do I want "Force" ???
Yupp.

Dialog is always the same, just the preselection for the matching windows differ. ("kcmshell4 kwinrules" requires you to detect a window, resp. enter all criterias yourself)
Comment 4 andy_90254 2013-11-15 19:58:22 UTC
There is a text box at that point, as if it is asking for an ID.  I don't know what to put in that box.
Comment 5 Thomas Lübking 2013-11-15 20:41:52 UTC
Some unique string "everphone" or whatever, but it has to be the very same for all windows you want to be grouped by this "bookmark name"
Comment 6 andy_90254 2013-12-08 21:47:25 UTC
I have now had some opportunity to test this feature and it is inconsistent.  Sometimes it works, and sometimes it doesn't.  At first it seemed to work, but now it doesn't - consistently.  I have confirmed that all desired tabs have the same unique string as you've specified, but once one of the tabs is closed either by crash or on purpose, restarting it no longer makes it join the group.  I'm forced to "attach as tab" each time.

Also I haven't found a way to change the order of the tabs (I have a preferred order it would be really nice if it kept the same order all the time) - obviously not as important as getting it to work at all, but still a desired feature.

Thank you
Comment 7 Thomas Lübking 2013-12-08 21:59:41 UTC
if the rule is not applied that simply means it doesn't match in that conditon.
Either the new window has different title/class/role/whatever and you ruled to strict or the window initially lands on a different activity (do you have more than one activitiy configured?)
Comment 8 andy_90254 2013-12-09 03:28:23 UTC
I don't understand what you mean by "activity".

When I open these windows, nothing has changed other than perhaps the internal data.  For example, as previously mentioned I'm using "everpad" to take notes.  So, those notes - the data stored within the application - might change but I have not changed any of the window manager settings.

In the case of sflphone, the application might be updated by the "nightly" build, but the name remains the same it's still the same application.  Everpad may or may not be getting updates, I'm not sure.

So I don't know if any of that would be affecting the tab group??
Comment 9 Thomas Lübking 2013-12-09 20:54:53 UTC
> what you mean by "activity".
qdbus org.kde.kactivitymanagerd /ActivityManager/Activities ListActivities

Attach ~/.kde/share/config/kwinrulesrc and the outputs of "xprop" and "xwininfo" on the windows you want to autotab. (The cursor turns into a cross for the commands and when you click the window, a bunch of attributes is printed to the calling konsole - you may want to redirect it into everpad.xprop etc.)
Comment 10 andy_90254 2013-12-12 19:45:53 UTC
A reboot seems to have resolved the issue for now.  I'll get back to you with the requested data when the problem reoccurs.  Thanks for your help!
Comment 11 Martin Flöser 2016-08-29 06:45:06 UTC
Unfortunately the rework in decorations in KWin 5 resulted in the window tabbing feature to be lost. We still want to bring this feature back, but after several versions it still hasn't emerged yet. Given that I think it is time to adjust the status of this bug report. The new implementation would be different anyway and it's questionable whether this report would still apply to it.