yad 14 (mx23 testing)

[dolphin_oracle]

taking this out of the package team coordination thread.


yad 14 is in mx test repo, at least for mx23.

In my experience, certain graphical elements in existing scripts that use yad dialogs break. in the antiX persistence scripts button icons are not visible and the former pre-canned yad OK and cancel buttons now just display "gtk-ok" and "gtk-cancel" respectively.

other scripts, like User Installed Packages, appear Ok at least at first look.

So before any migration of yad 14 into main repos (and even then IMO not before mx25), any existing scripts that utilize yad for dialogs will require updating and checking to make sure they still work with the newer libraries. That would include the persistence maintenance scripts, apt-notifier in its current state, mx-idesktool, and many smaller scripts utilized mostly by the fluxbox release.


possibly updating /usr/local/lib/antiX/antiX-common.sh will solve some of this. But all scripts utilizing yad would still need reviewed.

[dolphin_oracle]

taking this out of the package team coordination thread.


yad 14 is in mx test repo, at least for mx23.

In my experience, certain graphical elements in existing scripts that use yad dialogs break. in the antiX persistence scripts button icons are not visible and the former pre-canned yad OK and cancel buttons now just display "gtk-ok" and "gtk-cancel" respectively.

other scripts, like User Installed Packages, appear Ok at least at first look.

So before any migration of yad 14 into main repos (and even then IMO not before mx25), any existing scripts that utilize yad for dialogs will require updating and checking to make sure they still work with the newer libraries. That would include the persistence maintenance scripts, apt-notifier in its current state, mx-idesktool, and many smaller scripts utilized mostly by the fluxbox release.


possibly updating /usr/local/lib/antiX/antiX-common.sh will solve some of this. But all scripts utilizing yad would still need reviewed.

updating antiX-common seems to clear up the button issue. the issue is that somewhere between 0.40 and 14.X, the canned button names were renamed, and they are not backward compatible. So if you use the old canned items, likely their names are different now. for instance, gtk-ok is now yad-ok, and so forth.

[AVLinux]

Hmmm,

I use it for a lot of AVL stuff too, pretty much all my custom utilities and some file actions, better get to work I guess...

[anticapitalista]

Could you also check RAM usage compared to the older (present) version.
If I remember correctly, there is a significant difference ie new yad uses more RAM

[dolphin_oracle]

Could you also check RAM usage compared to the older (present) version.
If I remember correctly, there is a significant difference ie new yad uses more RAM

this is the yad command for the General vs. personal chooser generated when running "sudo live-remaster". ps_mem.py used for the info.

yad 0.40 - 8.2 MiB
yad 14.x - 8.4 MiB

[AVLinux]

Hi,

Not sure if this will affect @Melber but the color picker has changed, formerly a '--color' switch gave a dialog with a picker button and now there is no picker button unless you specify '--picker' in your options. Not a big deal but it could break the Papirus Folders app?

*EDIT it does affect Papirus Folders, when it launches the color picker there is no longer the button to select a color from the Desktop..

[Melber]

...
In my experience, certain graphical elements in existing scripts that use yad dialogs break. in the antiX persistence scripts button icons are not visible and the former pre-canned yad OK and cancel buttons now just display "gtk-ok" and "gtk-cancel" respectively.
...

Is it mainly button labels that need checking, or do you know of any other yad 14 weirdness, eg. dialog geometry, text formatting etc?

...other scripts, like User Installed Packages, appear Ok at least at first look....

How about papirus-folder-colors?

...
So before any migration of yad 14 into main repos (and even then IMO not before mx25), any existing scripts that utilize yad for dialogs will require updating and checking to make sure they still work with the newer libraries. That would include ... many smaller scripts utilized mostly by the fluxbox release.

Yep lots of stuff in MX-Fluxbox needs to be checked. Please don't move yad 14 into main repos before MX25.

[AVLinux]

@Melber

See above, Folders is affected

[dolphin_oracle]

@anticapitalista

possible mitigation for antiX-style-default.sh (posting for future reference as I'm not on my usual pc at the moment and I don't want to lose it).

Code: Select all

#--image=gtk-dialog-question
#--image=gtk-dialog-info

yad_version=$(yad --version |cut  -d"." -f1)
#echo "yad_version is " $yad_version

BUTTON_OK="gtk-ok"
BUTTON_CANCEL="gtk-cancel"
BUTTON_NO="gtk-no"
BUTTON_YES="gtk-yes"

if [ $(($yad_version)) -gt 1 ]; then
	BUTTON_OK="yad-ok"
	BUTTON_CANCEL="yad-cancel"
	BUTTON_NO="yad-no"
	BUTTON_YES="yad-yes"
fi

YAD_DEVICE_OPTS="
    --width=680 --height=400
    --button=$BUTTON_OK:0
    --button=$BUTTON_CANCEL:1"

YAD_YES_NO_OPTS="
    --button=$BUTTON_YES:0
    --button=$BUTTON_NO:1"

YAD_ERROR_OPTS="
    --image=gtk-dialog-error
    --button=$BUTTON_OK:0"

YAD_EXIT_OPTS="
    --button=$BUTTON_OK:0"

YAD_INFO_OPTS="
    --button=$BUTTON_OK:0"

YAD_BG_INFO_OPTS="
    --button=$BUTTON_CANCEL"

YAD_MULTI_OPTS="
    --button=$BUTTON_OK:0
    --button=$BUTTON_CANCEL:1"
    

provides the right button definition depending on version of yad. well, between 14 and 0.40 anyway.

[Melber]

@Melber
See above, Folders is affected

Ninja'd. Yep, there's my answer.
The question now is: Are we definitely going to move to yad 14?