# \[community\] JGPICOM

**URL:** <https://forum.maboxlinux.org/t/community-jgpicom/2092>\
**Category:** Development & Suggestions\
**Created:** [December 3, 2024, 5:34pm UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092 "2024-12-03T17:34:22Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![muzqs](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/muzqs/32/3702_2.png) [@muzqs](https://forum.maboxlinux.org/u/muzqs)\
**Post date:** [December 9, 2024, 10:14pm UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/21 "2024-12-09T22:14:48Z")

</div>

Sorry couldn’t let. 😵‍💫

This one is a bit like the preview video on gitlab.

```auto
backend = "glx";
frame-opacity = 0.9;
corner-radius = 10;
shadow-radius = 32;
fade-delta = 88;
fading = true;
fade-in-step = 0.099; 
fade-out-step = 0.040; 
no-fading-openclose = false;
no-fading-destroyed-argb = false;
no-ewmh-fullscreen = true;
no-vsync = false;

	
rules = (
  {
    match = "focused";
    opacity = 1.0;
    fade = true;
  },
  {
    match = "!focused";
    opacity = 0.95;
    fade = true;
  },

  {
    match = "window_type = 'utility' || window_type = 'notification'";
    shadow = false;
    opacity = 1.0;
  },

  {
    match = "class_g = 'i3-frame' || class_i = 'i3-frame'";
    opacity = 1.0;
    animations = (
      {
        triggers = ["close", "hide"];
        preset = "slide-out";
        direction = "down";
        duration = 0.1;
      },
      {
        triggers = ["open", "show"];
        preset = "slide-in";
        direction = "down";
        duration = 0.1;
      },
    )
  },

  {
    match = "window_type = 'dock'";
    shadow = true;
    opacity = 1.0;
    animations = (
      {
        triggers = ["close", "hide"];
        preset = "slide-out";
        direction = "up";
        duration = 0.1;
      },
      {
        triggers = ["open", "show"];
        preset = "slide-in";
        direction = "up";
        duration = 0.1;
      },
    )
  },

  {
    match = "class_g = 'Dunst'";
    shadow = false;
    animations = (
      {
        triggers = ["close", "hide"];
        preset = "slide-out";
        direction = "right";
        duration = 0.1;
      },
      {
        triggers = ["open", "show"];
        preset = "slide-in";
        direction = "right";
        duration = 0.1;
      },
    )
  },
  { match = "class_g = 'Screenkey'"; shadow = false; },
  { match = "class_g = 'screenkey'"; shadow = false; },
  { match = " name = 'vistransparent'||
		name = 'cavatransparent'||
		name = 'quakeradio'||
		name ?= 'Glava'||
		name = 'xfce4-notifyd'||   
		name *= 'Conky'||
		name ~= 'Mabox Polaroid Widget'||
		name ?= 'org.nickvision.cavalier' ||
		window_type *= 'dock'||
		window_type *= 'toolbar'||
		window_type *= 'menu'	";
@include "terminator.conf"
},

  {
    match = "window_type = 'dropdown_menu' || window_type = 'popup_menu' || window_type = 'menu' || window_type = 'tooltip'";
    opacity = 1;
    fade = false;
    full-shadow = true;
  },

  {
    match = "class_i = 'rofi' || class_g = 'Rofi'";
    fade = true;
    opacity = 1;
    full-shadow = true;
  }
)

shadow = true;
shadow-offset-x = -15;
shadow-offset-y = -15;
shadow-opacity = 0.80;

animations = (
  {
    triggers = ["geometry"];
    preset = "geometry-change";
    duration = 0.3;
  },
  {
    triggers = ["close", "hide"];
    preset = "disappear"
    duration = 0.3;
  },
  {
    triggers = ["open", "show"];
    preset = "appear";
    duration = 0.3;
  }
)

```

[VIDEO PREVIEW](https://gitlab.com/muzlabz/testlab/-/raw/main/images/testing.webm)

🐦

---

<div class="post-metadata">

**Author:** ![napcok](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/napcok/32/410_2.png) [@napcok](https://forum.maboxlinux.org/u/napcok)\
**Post date:** [December 9, 2024, 10:49pm UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/22 "2024-12-09T22:49:05Z")

</div>

Wow! Your configs are impressive, especially the animation effects 🙂

And unfortunately picom-conf doesn’t handle them well ☹

_I have to give up on experimenting with animations for now, as my priority is to release Mabox Herbolth before the end of 2024. And there’s not much time._

_From the beginning of 2025 I want to start working on Mabox “NEXT”. A fresh start, which will be an opportunity to get rid of all the technological baggage accumulated over the years 🙂 There will also be time to think about how to handle the new features in Picom 😉_

---

<div class="post-metadata">

**Author:** ![muzqs](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/muzqs/32/3702_2.png) [@muzqs](https://forum.maboxlinux.org/u/muzqs)\
**Post date:** [December 10, 2024, 8:39am UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/23 "2024-12-10T08:39:35Z")

</div>

> [@napcok](#):
>
> There will also be time to think about how to handle the new features in Picom

I agree thats indeed a next step. A lot of possabilities.

But also how complex it should be.

Gitlab `testcase` is deleted and migrated to `mabox_jgpicom.`

I need to invest more about the rules and animations etc .

The new year is perfect. No hurry,wurrry.

> **[M bird / mabox\_jgpicom · GitLab](https://gitlab.com/muzlabz/mabox_jgpicom)**
>
> Picom tweaker for Mabox jgmenu

🐦

---

<div class="post-metadata">

**Author:** ![muzqs](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/muzqs/32/3702_2.png) [@muzqs](https://forum.maboxlinux.org/u/muzqs)\
**Post date:** [December 10, 2024, 9:43am UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/24 "2024-12-10T09:43:14Z")

</div>

#### Sorry to distrup. @napcok .

I have to get used to the changes you made.

I can’t get the new `jgpicom-pipe` running in the `jgpicom menu.`

```auto
out+=(" $START,^pipe(jgpicom-pipe)")        

```

I changed it for the time being with directly the use of…

```auto
mabox-compositor --etc

```

UPDATE `mabox_jgpicom`

- `jgpicom` for the moment only `start and stop`. No config choose.

- Use `mabox main menu` to choose config, etc.

- Use `jgpicom` only to change values for some basic visual settings.

[https://gitlab.com/muzlabz/mabox\_jgpicom.git](https://gitlab.com/muzlabz/mabox_jgpicom.git)

🐦

---

<div class="post-metadata">

**Author:** ![napcok](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/napcok/32/410_2.png) [@napcok](https://forum.maboxlinux.org/u/napcok)\
**Post date:** [December 10, 2024, 10:00am UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/25 "2024-12-10T10:00:11Z")

</div>

Try:

```auto
out+=(" $START,^pipe(jgpicom-pipe menu)") 

```

for now.

---

<div class="post-metadata">

**Author:** ![muzqs](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/muzqs/32/3702_2.png) [@muzqs](https://forum.maboxlinux.org/u/muzqs)\
**Post date:** [December 10, 2024, 11:36am UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/26 "2024-12-10T11:36:39Z")

</div>

Update:

> [@napcok](#):
>
> for now.

- added fixed jgpicom-pipe. 😉 for now.
- simplified menu shadows.
- need look at values fading.
- removed tip (W-p) from menu

 ![Mabox_20241210-12-41-25](https://forum.maboxlinux.org/uploads/default/original/2X/2/2b7e8761496e27e2613aa62311cef2227d17c3fb.png)

🐦

---

<div class="post-metadata">

**Author:** ![muzqs](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/muzqs/32/3702_2.png) [@muzqs](https://forum.maboxlinux.org/u/muzqs)\
**Post date:** [December 10, 2024, 12:38pm UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/27 "2024-12-10T12:38:00Z")

</div>

## Jpicom-pipe : Glx / xrender not changing for me in the config.

It changes in the menu though.

```auto
out+=("^sep($RENDERER)")
[["$backend" == "glx"]] && out+=("<big>綠</big> $GLX" "<big>祿</big> $XRENDER,mb-setvar picom_renderer=xrender;mabox-compositor --restart") || out+=("<big>祿</big> $GLX,mb-setvar picom_renderer=glx;mabox-compositor --restart" "<big>綠</big> $XRENDER")

```

Is the `backend` setting a testing case or..

Should this

`mb-setvar picom_renderer=glx`

be

`mb-setvar backend="glx" "$CONFIGFILE"`

BUT.

Maybe i am wrong about this.

mb-setvar is good for `shadow=value "$configfile"`.

The picom config uses `backend = "glx";`. With spaces.

Thats the reason i use :

```auto
sed -i 's/^backend[[:space:]]*= \S*;/backend = "$i";/' "$CONF_FILE"

```

Correct if i am wrong.

🐦

---

<div class="post-metadata">

**Author:** ![napcok](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/napcok/32/410_2.png) [@napcok](https://forum.maboxlinux.org/u/napcok)\
**Post date:** [December 10, 2024, 1:01pm UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/28 "2024-12-10T13:01:56Z")

</div>

Maintenance of rolling distro is not easy…  
I have to deal with configs shipped with Mabox by default - they broke after last picom update.  
The reason is the latest picom v12 refuses to start when backend is not specified in config. Previously that worked (with picom v11).

Now $backend is used in command which starts picom and stored in `~/.config/mabox/mabox.conf`.  
The parameter given in the command line is used instead of what we have in the config. (I’m not 100% sure, but that’s how it should work).

---

<div class="post-metadata">

**Author:** ![muzqs](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/muzqs/32/3702_2.png) [@muzqs](https://forum.maboxlinux.org/u/muzqs)\
**Post date:** [December 10, 2024, 7:02pm UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/29 "2024-12-10T19:02:02Z")

</div>

### Could not not not post this effect 🙀. By accident. I was creating include file and suddenly this happend.

💫 switching workspace. Windows slide up.

---

<div class="post-metadata">

**Author:** ![muzqs](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/muzqs/32/3702_2.png) [@muzqs](https://forum.maboxlinux.org/u/muzqs)\
**Post date:** [December 10, 2024, 7:36pm UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/30 "2024-12-10T19:36:54Z")

</div>

# [Another preview a bit better i think](https://gitlab.com/muzlabz/mabox_jgpicom/-/raw/main/images/slideup2.webm)

🐦

---

<div class="post-metadata">

**Author:** ![muzqs](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/muzqs/32/3702_2.png) [@muzqs](https://forum.maboxlinux.org/u/muzqs)\
**Post date:** [December 11, 2024, 12:59am UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/31 "2024-12-11T00:59:56Z")

</div>

### Another example setup for picom. 📌

Hard to find updated custom configured picom configs.

> The whole folder `picom` is needed.  
> Two files are @included.configs.

Did’t test it yet.

> **[Arch-i3/picom/.config at main · adnope/Arch-i3](https://github.com/adnope/Arch-i3/tree/main/picom/.config)**
>
> My i3wm setup for Arch Linux with i3, polybar, rofi and picom - adnope/Arch-i3

🐦

---

<div class="post-metadata">

**Author:** ![muzqs](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/muzqs/32/3702_2.png) [@muzqs](https://forum.maboxlinux.org/u/muzqs)\
**Post date:** [December 11, 2024, 11:19am UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/32 "2024-12-11T11:19:02Z")

</div>

![Mabox_20241211-12-16-45](https://forum.maboxlinux.org/uploads/default/original/2X/1/17c30ed15d6371dc94bb668379279d3e001c1e62.png)

### Update: _latest_ jgpicom.

- new config (adnope/i3wm)
- readme cleaned

TODO: Disable blur for screenshot

[https://gitlab.com/muzlabz/mabox\_jgpicom.git](https://gitlab.com/muzlabz/mabox_jgpicom.git)

🐦

---

<div class="post-metadata">

**Author:** ![muzqs](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/muzqs/32/3702_2.png) [@muzqs](https://forum.maboxlinux.org/u/muzqs)\
**Post date:** [December 11, 2024, 11:22am UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/33 "2024-12-11T11:22:21Z")

</div>

ASCII FONTS GENERATOR:

[https://patorjk.com/software/taag/#p=display&f=ANSI%20Shadow&t=mabox%20picom Config](https://patorjk.com/software/taag/#p=display&f=ANSI%20Shadow&t=mabox%20picom%0AConfig)

 ![Mabox_20241211-12-21-25](https://forum.maboxlinux.org/uploads/default/original/2X/f/f4bfda30c30959f27f9b47a112301298bc1bbbc5.png)

🐦

---

<div class="post-metadata">

**Author:** ![napcok](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/napcok/32/410_2.png) [@napcok](https://forum.maboxlinux.org/u/napcok)\
**Post date:** [December 11, 2024, 11:32am UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/34 "2024-12-11T11:32:24Z")

</div>

Wow!  
Latest is very impressive 😃

And works very nice on my HW.

---

<div class="post-metadata">

**Author:** ![muzqs](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/muzqs/32/3702_2.png) [@muzqs](https://forum.maboxlinux.org/u/muzqs)\
**Post date:** [December 11, 2024, 4:10pm UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/35 "2024-12-11T16:10:03Z")

</div>

> [@napcok](#):
>
> Wow!  
> Latest is very impressive 😃

I like the latest too. A bit more refind in movement not to jumpie.

🐦

---

<div class="post-metadata">

**Author:** ![muzqs](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/muzqs/32/3702_2.png) [@muzqs](https://forum.maboxlinux.org/u/muzqs)\
**Post date:** [December 11, 2024, 4:12pm UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/36 "2024-12-11T16:12:44Z")

</div>

When you do screenshot select area.

Is the screen transparent or blur.

in case of blur.

download the latest picom-rules. I added slop to the list.

---

<div class="post-metadata">

**Author:** ![muzqs](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/muzqs/32/3702_2.png) [@muzqs](https://forum.maboxlinux.org/u/muzqs)\
**Post date:** [December 11, 2024, 4:13pm UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/37 "2024-12-11T16:13:42Z")

</div>

maybe quicker

{ # system mabox  
match = “class\_g = ‘slop’”;  
opacity = 0.9;  
shadow = false;  
blur-background = false;  
},

to picom-rules.conf

_ps: the latest has more edits done._

---

<div class="post-metadata">

**Author:** ![napcok](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/napcok/32/410_2.png) [@napcok](https://forum.maboxlinux.org/u/napcok)\
**Post date:** [December 11, 2024, 4:46pm UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/38 "2024-12-11T16:46:15Z")

</div>

Thanks 🙂  
I will redownload later…

Here some additions to picom-animations.conf

Different animations for menus (jgmenu based) and for Quake Term F12 😉

```auto
{
	match = "name = 'jgmenu'";
	animations = (
    {
      triggers = ["close", "hide"];
      preset = "disappear";
      duration = 0.1;
      scale = 0.5;
    },
    {
      triggers = ["open", "show"];
      preset = "appear";
      duration = 0.3;
      scale = 0.5;
    }
  )
},
{
	match = "name = 'Quake Term'";
	animations = (
    {
      triggers = ["close", "hide"];
      preset = "fly-out";
      direction = "up";
      duration = 0.2;
    },
    {
      triggers = ["open", "show"];
      preset = "fly-in";
      direction = "up";
      duration = 0.2;
     }
  )
}

```

---

<div class="post-metadata">

**Author:** ![muzqs](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/muzqs/32/3702_2.png) [@muzqs](https://forum.maboxlinux.org/u/muzqs)\
**Post date:** [December 11, 2024, 5:44pm UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/39 "2024-12-11T17:44:50Z")

</div>

Added pyradio to Quake term animation. Nice effect for the quake feeling.

```auto
"name = 'quakeradio'";

```

🐦

---

<div class="post-metadata">

**Author:** ![napcok](https://forum.maboxlinux.org/user_avatar/forum.maboxlinux.org/napcok/32/410_2.png) [@napcok](https://forum.maboxlinux.org/u/napcok)\
**Post date:** [December 17, 2024, 10:37pm UTC](https://forum.maboxlinux.org/t/community-jgpicom/2092/40 "2024-12-17T22:37:29Z")

</div>

I had a chance to play around with your config a bit over the weekend. I changed quite a few things. And overall I’m very happy with the result.

A few conclusions so far…

One sad one…

1. Building a dynamic menu that universally supports the new rule-based format seems impossible - and definitely beyond my skills.

A few positives…  
2. Thanks to @include directives - we can split the config into many parts, where each is responsible for something different 🙂  
For now I have:

- conky.conf
- conky-transp.conf
- jgmenu.conf
- notifications.conf
- picom-animations.conf
- picom-rules.conf
- tint2.conf
- win-inactive.conf

1. Assuming the above or similar convention - it would be easy to build a dynamic menu for changing parameters

2. I think it is possible to recognize in the script building the dynamic menu what type of picom config we are dealing with and present the appropriate possibilities 🙂

I still need some free time (an hour or two) to refine the proposed config. Then I will publish it in some repo so that we can test it and think about how to implement a cool dynamic menu.

[Previous page](https://forum.maboxlinux.org/t/community-jgpicom/2092.md?page=1)

[Next page](https://forum.maboxlinux.org/t/community-jgpicom/2092.md?page=3)
