[kwin] [Bug 419122] Fullscreen managment

2020-03-22 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=419122

--- Comment #2 from Lionel Chauvin  ---
I think the fullscreen icon need a modification of kwin decorations.
The fake titlebar could be implemented in plasma and the application could ask
for it.
How fullscreen is managed in plasma-mobile ?
How the user makes the controls appear when the application is in fullscreen ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 419123] New: Fullscreen managment

2020-03-22 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=419123

Bug ID: 419123
   Summary: Fullscreen managment
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: megabig...@yahoo.fr
  Target Milestone: ---

RATIONAL

It is hard to discover how to toggle on/off an application in fullscreen mode.

PROPOSAL

For the applications that support fullscreen, an icon is displayed in the
titlebar for toggle on this mode.
In fullscreen mode, a fake title bar appears when the cursor hit the top of the
screen.
This fake titlebar has an icon for toggle off fullscreen mode.

RELATED ISSUES

https://bugs.kde.org/show_bug.cgi?id=413255
https://bugs.kde.org/show_bug.cgi?id=177094

PREVIOUS ART

fullscreen mode on macos:

https://www.youtube.com/watch?time_continue=19=EbkbaQDFQ9U=emb_logo

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 419122] New: Fullscreen managment

2020-03-22 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=419122

Bug ID: 419122
   Summary: Fullscreen managment
   Product: kwin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: core
  Assignee: kwin-bugs-n...@kde.org
  Reporter: megabig...@yahoo.fr
  Target Milestone: ---

RATIONAL

It is hard to discover how to toggle on/off an application fullscreen in
fullscreen mode.

PROPOSAL

For the applications that support fullscreen, an icon is displayed in the
titlebar for toggle on this mode.
In fullscreen mode, a fake title bar appears when the cursor hit the top of the
screen.
This fake titlebar has an icon for toggle off fullscreen mode.

RELATED ISSUES

https://bugs.kde.org/show_bug.cgi?id=413255
https://bugs.kde.org/show_bug.cgi?id=177094

PREVIOUS ART

fullscreen mode on macos:

https://www.youtube.com/watch?time_continue=19=EbkbaQDFQ9U=emb_logo

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 333146] Font Family is localized and hence not understood by GTK applications

2020-02-15 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=333146

--- Comment #11 from Lionel Chauvin  ---
It doesn't work with:
gtk-font-name="Ubuntu Light, 11"

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 333146] Font Family is localized and hence not understood by GTK applications

2020-02-15 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=333146

--- Comment #10 from Lionel Chauvin  ---
Yes, it also work with:
gtk-font-name="Ubuntu Light 11"

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 333146] Font Family is localized and hence not understood by GTK applications

2020-02-15 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=333146

Lionel Chauvin  changed:

   What|Removed |Added

 CC||megabig...@yahoo.fr

--- Comment #8 from Lionel Chauvin  ---
On my system (Kubuntu 19.10, KDE 5.18.0) I configured the following font in
kcm_font:
font: "Ubuntu Light"
style: "Regular"
size: "11"

It automatically adjusts the file ~/.gtkrc-2.0 with the line:
gtk-font-name="Ubuntu Light, Regular 11"
Gtk2 doesn't seems to understand this setting: in Gimp and Inkscape it is
"Ubuntu Light, Bold 11" that is rendered.

It is properly rendered if I manually change the file and remove the comma:
gtk-font-name="Ubuntu Light Regular 11"

Unfortunally this change is lost when I restart my computer.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 405040] New: "Alternatives..." menu-item give wrong impression that I can install an alternative of the clicked task

2019-03-03 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=405040

Bug ID: 405040
   Summary: "Alternatives..." menu-item give wrong impression that
I can install an alternative of the clicked task
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: megabig...@yahoo.fr
CC: plasma-b...@kde.org
  Target Milestone: 1.0

This patch https://phabricator.kde.org/D19472 added a new "Alternatives .."
item that provides a way to install an alternative of task manager.

This feature is cool but is misleading because it gives the impression I can
install an alternative of the clicked task (for instance Konsole).

In order to remove this ambiguity I propose to create a submenu "Task manager
>" with "Configure ..." and "Alternatives ..." items.

-- 
You are receiving this mail because:
You are watching all bug changes.

[yakuake] [Bug 399887] All themes failed to install

2019-01-06 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=399887

Lionel Chauvin  changed:

   What|Removed |Added

 CC||megabig...@yahoo.fr

--- Comment #3 from Lionel Chauvin  ---
This bug is a duplicate of this one:
https://bugs.kde.org/show_bug.cgi?id=395012

I provided a patch 6 month ago but nobody seems to have time to review it:
https://phabricator.kde.org/D13335

-- 
You are receiving this mail because:
You are watching all bug changes.

[yakuake] [Bug 395012] Skins can't be installed from KNS

2018-06-04 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=395012

--- Comment #2 from Lionel Chauvin  ---
Hi, Eike Hein
Can I add you as a reviewer on https://phabricator.kde.org/D13335 ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[yakuake] [Bug 395012] Skins can't be installed from KNS

2018-06-04 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=395012

--- Comment #1 from Lionel Chauvin  ---
Hi, Ein Kein
Can I add you as a reviewer on https://phabricator.kde.org/D13335 ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[yakuake] [Bug 395012] Skins can't be installed from KNS

2018-06-03 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=395012

Lionel Chauvin  changed:

   What|Removed |Added

 Attachment #113055|fix |patch
description||

-- 
You are receiving this mail because:
You are watching all bug changes.

[yakuake] [Bug 395012] New: Skins can't be installed from KNS

2018-06-03 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=395012

Bug ID: 395012
   Summary: Skins can't be installed from KNS
   Product: yakuake
   Version: Git (Frameworks 5)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: megabig...@yahoo.fr
  Target Milestone: ---

Created attachment 113055
  --> https://bugs.kde.org/attachment.cgi?id=113055=edit
fix

When a Skin is downloaded from KNS, Yakuake fails to validate the presence of
title.skin and tabs.skin files.
The skin is then uninstalled even if these files exist.

This is due to this optimization of KNS: https://phabricator.kde.org/D6104
Files are not listed anymore by entry.installedFiles().
They are replaced by paths that end with /*

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 387097] Need ability to read client.maximizeMode since it's currently not a property

2018-03-12 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=387097

Lionel Chauvin <megabig...@yahoo.fr> changed:

   What|Removed |Added

 CC||megabig...@yahoo.fr

--- Comment #1 from Lionel Chauvin <megabig...@yahoo.fr> ---
(In reply to Chris Holland from comment #0)
> I need to know if the client is maximized during workspace.clientAdded for
> my script. New Firefox windows can start maximized, which means my script
> isn't able to hide the titlebar until the user un-maximizes then maximizes
> (triggering client.clientMaximizedStateChanged).

Hi,

client.minimized is exposed but not client.maximized :D

As a workaround, did you try to check if the geometry is equal to the WorkArea
?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 391728] Improve ultrawide screen support: Maximize on the left or right area

2018-03-12 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=391728

--- Comment #5 from Lionel Chauvin <megabig...@yahoo.fr> ---
I am not against add an action in the user's menu. It could help to discover
the shortcut but I don't see how it can help to discover the drag'n drop to the
screen edge.

I already known the existence of Quick Tiling. The drag'n drop is not the way I
would like to interact with my windows. My previous setting had two screens and
I will not be the only one that migrate to an ultrawide screen and to expect
the maxmimize icon to be smarter. So I will continue to use my kwin script,
even if it is a big hack.

Is there a way to trigger an animation from a kwin script ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 391728] Improve ultrawide screen support: Maximize on the left or right area

2018-03-11 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=391728

--- Comment #3 from Lionel Chauvin <megabig...@yahoo.fr> ---
Ok, I understand.
So, what is missing is the ability to add as many icon as needed in the window
decoration in order to properly command the quick tiling.
And the quick tiling must manage several states in order to restore a window to
its previous position.
This will not break more stuff ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 391728] Improve ultrawide screen support: Maximize on the left or right area

2018-03-11 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=391728

Lionel Chauvin <megabig...@yahoo.fr> changed:

   What|Removed |Added

Summary|Improve Ultrawide screen|Improve ultrawide screen
   |support: Maximize on the|support: Maximize on the
   |left or right area  |left or right area

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 391728] New: Improve Ultrawide screen support: Maximize on the left or right area

2018-03-11 Thread Lionel Chauvin
https://bugs.kde.org/show_bug.cgi?id=391728

Bug ID: 391728
   Summary: Improve Ultrawide screen support: Maximize on the left
or right area
   Product: kwin
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: scripting
  Assignee: kwin-bugs-n...@kde.org
  Reporter: megabig...@yahoo.fr
  Target Milestone: ---

Created attachment 111325
  --> https://bugs.kde.org/attachment.cgi?id=111325=edit
a kwin script that change the "maximize" icon behavior

More and more 21/9 widescreen displays hit the market and in my opinion this
screen format is really convenient. A 21/9 screen  has more or less the same
surface as two 4/3 screens put side by side. It is really convenient when you
want to view two documents at the same time. This format also allows to have
really large windows like a video player in cinema format.

Today, when you click on the "maximize" icon, it places the window on the whole
work area. It is also possible to drag and drop a window on the edge of the
screen so that it takes half of it. In my opinion this feature is not very
convenient to use.

I propose a modification of the behavior of the "maximize" icon so that it
chooses automatically the best zone according to the position: the left side,
the right side or the full work area.

To illustrate the behavior I want to achieve I made a video:
https://youtu.be/R7kNSL68zYY

I wrote a KWin script that gets this behavior. You can find it as an attachment
and I invite you to test it. It should work on a 16/9 screen too.

I do not think the scripting system can allow to properly implement this
feature. I am experiencing the following issues:
- There are no shadows when a window is maximized.
- There is no animation when maximizing on one side of the screen

The first problem is due to a choice of KWin to hide shadows that are not
usually needed when a window is maximized. It should be possible to tell him
that we want to display a shadow on the edge that is still visible.

The second problem is due to the fact that "clientMaximizeSet" signal is
already emitted when the script changes the window geometry. The "maximize"
animation is then cut off.

I'm waiting for your comment about this idea and I hope this feature can be
implemented directly in KWin or that the scripting system will be improved to
make it possible.

-- 
You are receiving this mail because:
You are watching all bug changes.