On വെ, Oct 25, 2019 at 11:47, sadiq@sadiqpk.org wrote:
The compilation error happens because the symbol `enable_javascript_markup`
property isn't present in vala vapi files, which means that valac-vapi has to be
updated, currently the version in buster is 0.42. For a grep of `enable_javascript`,
I get the following:
$ grep enable_javascript /usr/share/vala-0.42/vapi/webkit2gtk-4.0.vapi
public bool get_enable_javascript ();
public void set_enable_javascript (bool enabled);
public bool enable_javascript { get; set construct; }
And for the same, with vala 0.46 on testing:
$ grep enable_javascript /usr/share/vala-0.46/vapi/webkit2gtk-4.0.vapi
public bool get_enable_javascript ();
public bool get_enable_javascript_markup ();
public void set_enable_javascript (bool enabled);
public void set_enable_javascript_markup (bool enabled);
public bool enable_javascript { get; set construct; }
public bool enable_javascript_markup { get; set construct; }
Which means that the symbol isn't currently present in the valac-0.42-vapi
I'm not so familiar with gtk/vala, but quite comfortable with backporting.
I can backport vala, but isn't having to use a new vala version to use a new webkitgtk a design bug? Can't we include vala bindings of webkitgtk in a separate package or part of webkitgtk? Or is webkitgtk considered part of vala itself?
A minimal vala example for testing:
using WebKit;
// valac --pkg webkit2gtk-4.0 --thread test.vala
public static int main (string[] args) {
var test = new WebKit.Settings();
test.enable_javascript = true;
test.enable_javascript_markup = true;
return 0;
}
Regards
Mohammed Sadiq