Migrating from AGSv1 to AGSv2 (help wanted)

[clsty]

What would you like to be added?

Currently we're using AGSv1, which works fine, but AGSv2 is released and maybe we're able to migrate to AGSv2 with acceptable efforts if lucky.

How will it help?

• Enjoy new features from AGSv2
• Fix some issues such as Support non-GNOME Bluetooth based frontends? #922

Useful links

• Migration guide
• Related discussion in Aylur/ags
• Related issue in Aylur/ags
• Related discussion here

How to achieve

• Rename the executable of AGSv1 from ags to agsv1 so that it will not conflict with the ags of AGSv2.
• Create .config/agsv2 and install AGSv2, use killall agsv1 ags ydotool; ags run -d $XDG_CONFIG_HOME/agsv2 & to run AGSv2 for developing while keeping AGSv1 still working.
• (MAIN MISSION) Gradually implement codes inside .config/ags into .config/agsv2.
• Remove .config/ags and AGSv1, rename .config/agsv2 to .config/ags to apply the changes.

[nonetrix]

Plan to migrate to GTK-4 as well out of curiosity? Benifit is mainly GPU acceleration and better CSS support for what that's worth

[clsty]

I've made the preparation for developing for migration to AGSv2.

The AGSv1 executable is now renamed from ags to agsv1.
For a proper update, run (i.e. do not skip) the following steps in install.sh:

• handle-deprecated-dependencies
• install-local-pkgbuild ./arch-packages/illogical-impulse-agsv1 --needed
• rsync -av --delete --exclude /user_options.js .config/ags/ ~/.config/ags/
• rsync -av --delete --exclude /custom --exclude /hyprlock.conf --exclude /hypridle.conf --exclude /hyprland.conf .config/hypr/ ~/.config/hypr/

---

@end-4 I don't know your plan, but I've made the preparation in case you are willing to start developing on AGSv2 someday. As for futher preparation for developing on your computer, my suggestions are as follows:

• Install AUR package aylurs-gtk-shell or aylurs-gtk-shell-git which provides executable ags of AGSv2.
• Set a keybind inside ~/.config/hypr/custom/keybinds.conf such as:

bindr = SuperShift, R, exec, killall agsv1 ags ydotool; ags run -d $XDG_CONFIG_HOME/agsv2 &

Which provides a quick shortcut to switch to or restart AGSv2 (with configs inside ~/.config/agsv2).

[Pharmaracist]

just a question why should we migrate like is it performance issue or just to be updated with aylur stuff and do we need to write the config from scratch or just change some lines and does astal bring any thing new like hot-changing

[clsty]

just a question why should we migrate like is it performance issue or just to be updated with aylur stuff and do we need to write the config from scratch or just change some lines and does astal bring any thing new like hot-changing

I've already listed 2 reasons in the beginning:

• Enjoy new features from AGSv2
• Fix some issues such as Support non-GNOME Bluetooth based frontends? #922

[Pharmaracist]

so do we need to rewrite everything from scratch since i saw that we should ?

[clsty]

so do we need to rewrite everything from scratch since i saw that we should ?

idk, probably. See "Useful links" at the beginning for reference.

[enessmr]

Plan to stay at AGS v1 so it's easier to code?

[clsty]

Plan to stay at AGS v1 so it's easier to code?

That's also an option but AGSv1 could be probably not working in future, since it needs some system packages as dependencies. Though there could be a workaround like using a container or using Nix/Guix...