[SOLVED] Call for Testers: MATE 1.16 for Slackware 14.2
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
MATE 1.14 has been released and the development is now focused on MATE 1.15 which will eventually be MATE 1.16 release this year (someday around September-November since they are targeting for Ubuntu 16.10 and Fedora 25 release).
My future plan is to provide MATE 1.16 for Slackware 14.2 since it's relatively new and all the deps are still met. MATE 1.16 will bring more GTK+3 porting besides some small new features according to the ROADMAP.
Users who can't wait to try the new MATE 1.16 can start helping by upgrading to MATE 1.15 which i have uploaded to the usual repository. It now lives under "current" directory where i have prepared two options: a mix build between GTK+2 and GTK+3 and full GTK+3 build. I only provided binary packages for x86_64 architecture for now, but building it from master branch will only take 1-2h depending on your machine specs.
Highlight of MATE 1.15 so far:
* Bump all packages to 1.15.x
* Add new deps: libgxps for atril to support XPS file format
* Add new flag for atril to support DVI format (it uses tetex's kpathsea)
* Add new deps: vte3 for mate-terminal (2.91 APIs)
* Add new deps for vte3: vala
* Engrampa, mate-notification-daemon, mate-polkit, mate-terminal and mate-session-manager are now GTK+3 only
* Enable introspection in caja and mate-desktop
* Enable gdict applet in mate-utils
* Enable IPv6, stickynotes, and polkit support in mate-applets
Additional changes for full GTK+3 build:
* Add new deps: libunique3 (replacing libunique)
* Add new deps: glade
* Add new deps: gtksourceview3 (replacing gtksourceview)
* Removed deps: pygtksourceview
* Atril: Use webkit2gtk for ePUB support
You can use slackpkg+ to help you upgrade to this release, but please read the UPGRADE.TXT provided in the directory.
X86? For real? As in: installable on Slackware? What happened with you?
He always said he was going to provide a 32bit version once 14.2 was released... I guess you just forgot about that part and just remembered he didn't provide it for -current.
Your sense of entitlement still never ceases to amaze me (I should get used it it, but for some reason, I always forget just how entitled you feel you are).
Thanks, Willy: I'm still using MSB 1.10 on 14.1, and now that I'm about to upgrade to 14.2 I don't know whether to go to MSB 1.14 or wait a while and go straight to 1.16 I'll test these SlackBuilds if I get the chance.
Quote:
Originally Posted by Darth Vader
@willysr I guess you messed something there, looking at folder name:
Thanks, Willy: I'm still using MSB 1.10 on 14.1, and now that I'm about to upgrade to 14.2 I don't know whether to go to MSB 1.14 or wait a while and go straight to 1.16 I'll test these SlackBuilds if I get the chance.
If you prefer a stable release, go for 1.14
if you don't mind a little bit of challenge, go for 1.15
it doesn't change much (1.14 -> 1.15), so it won't be too much difference, except that some components are now in GTK+3 and there are some new deps along with small improvements on some components
Been testing the GTK3 build for a couple of days. I wanted to note a few things that I have noticed.
* If sound events are enabled, you can get rapid sound events when you open the appearance window. I have a lot of themes and it beeps for like a good 10 seconds at least.
* Also under Appearance, when customizing the theme, the color tabs, no colors show in the options.
* Pop up highlights when hovering over icons or menu do not work unless software compositing manager is enabled.
* Caja, if you switch the location bar to editable, the box is rather small in comparison with the application. It's a problem when dealing with long paths.
Other than that, I really like how the change to gtk3 is going.
A new caja 1.15.2 has been released, but i didn't built it for GTK+3 yet.
This is the changelog, i hope it fixed some of your issues:
Quote:
* GTK+-3 eel: fix color definition pointed out by running distcheck with gtk3
* distcheck: explicitly use currently selected GTK+ version
* GTK+-3 pathbar: always show the sliders
* GTK+-3 pathbar: add slider-button class to sliders
* GTK+-3 pathpar: add image-button class to iconic buttons
* GTK+-3 pathbar: use text-button style class for pathbar buttons
* GTK+-3 pathbar: fix allocation offset for the down slider button
* GTK+-3 pathbar: do not use deprecated gtk_arrow_new
* GTK+-3 pathbar: do not use deprecated gtk_alignment_new
* GTK+-3 pathbar: refresh label size request every time it changes
* drop unneeded includes
* remove some unused includes
* libcaja-private: drop unused CajaIdleQueue code
* eel: fix minor build warning
* libcaja-private: drop some more unused code
* libcaja-private: remove unused CajaMergedDirectory code
* fix minor build warning
* location-bar: don't pack an useless box in the bar
* location-bar: fix deprecated GTK_TYPE_HBOX usage
* navigation-bar: remove useless abstract class
* all: don't use deprecated GMutex/GThread API
* GTK+-3.20 view-as-action: avoid deprecated gtk_combo_box_set_focus_on_click
* editable-label: reduce ifdefine hell
* GTK+-3 eel-editable-label: drop usage of GtkMisc
* GTK+-3 connect-server-dialog: use widget properties instead of GtkAlignment
* GTK+-3 open-with-dialog: use widget properties instead of GtkAlignment
* GTK+-3 searchbar: use widget properties instead of GtkAlignment
* GTK+-3 fm-properties-window: use widget properties instead of GtkAlignment
* GTK+-3 fm-list-view: use widget properties instead of GtkAlignment
* GTK+-3 file-conflict-dialog: use widget properties instead of GtkAlignment
* eel-gtk-extensions: remove eel_gtk_adjustment* functions
* icon-container: don't use eel helper to set adjustment values
* notebook: cleanup an old workaround
* GTK+-3 caja-icon-dnd: avoid deprecated gtk_drag_begin
* Gtk+-3.20 fm-desktop-icon-view: use GdkSeat operations
* Gtk+-3.20 eel-canvas: use GdkSeat operations
* GTK+-3.20 caja-tree-view-drag-dest: use GdkSeat operations
* GTK+-3.20 caja-dnd: use GdkSeat operations
* GTK+-3.20 caja-icon-container: use GdkSeat operations
* Revert "navigation-bar: fix deprecated GTK_TYPE_HBOX usage"
* Revert "navigation-bar: fix typo in previous commit"
stormtracknole: can you post a screenshot for "Pop up highlights when hovering over icons or menu do not work unless software compositing manager is enabled." issue?
stormtracknole: until upstream find a permanent fix for this issue, i will probably disable the "color" tab since it's not usable at this moment. I'm testing the patch from Fedora's maintainer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.