puppylinux-woof-CE / woof-CE

woof - the Puppy builder
GNU General Public License v2.0
389 stars 278 forks source link

slackware-15 too old already for wlroots/wayland #3372

Open 01micko opened 2 years ago

01micko commented 2 years ago

I've been developing labwc/sfwbar for a while now and the current 'stable' labwc/wlroots is way too buggy for a prime time puppy release, #3030 #3322 notably . The latest and greatest base is needed and in the case of slackware that is -current.

I'm typing on it now

Everything pretty much works! Sound crashes on GUI restart - I know the cause. Most videos play, can view images (except mtpaint isn't working) , pMusic works (slackware native ffmpeg). It's actually pleasing that this is the first boot! Haven't saved session yet (usb install).

Hopefully I can offer PRs next wekend.

20220904_19h39m50s_grim

dimkr commented 2 years ago

Even before labwc support in woof-CE is in perfect shape, a slackware64-current configuration would be nice to have, so we can track future issues like new wlroots versions (same rationale as having weekly builds of sid64) 👍🏿

01micko commented 2 years ago

Even before labwc support in woof-CE is in perfect shape, a slackware64-current configuration would be nice to have, so we can track future issues like new wlroots versions (same rationale as having weekly builds of sid64) 👍🏿

..and just rebooted and restored this session :smiley_cat:

Absolutely. -current is where the action is and I should setup a wslacko repo to track breaking changes.

Time is my enemy however (like most of us :roll_eyes: )

dimkr commented 2 years ago

Time is my enemy however (like most of us 🙄 )

I can help with that. Maybe copying slackware64/15.0 to slackware64/current and adding it to the weekly rotation is a good first step.

01micko commented 2 years ago

I can help with that. Maybe copying slackware64/15.0 to slackware64/current and adding it to the weekly rotation is a good first step.

Maybe. Some stuff is quite broken though. For example,

01micko commented 2 years ago

Progress:

01micko commented 2 years ago

Added

Still need to fine tune some of these petbuilds

01micko commented 2 years ago

The -current wayland build is now 548MB xz compressed with all of the above. Testing shortly.

01micko commented 2 years ago

Almost in a usable state! :sweat_smile:

https://user-images.githubusercontent.com/1019119/189509943-dcdadf37-3155-4549-baf8-b827a43bb29d.mp4

01micko commented 2 years ago

The above video and post was made on a 2012 mackbook. Everything pretty much works.

dimkr commented 2 years ago

Almost in a usable state! sweat_smile

recording.mp4

Super cool stuff!

zigbert commented 2 years ago

You are both incredible! Puppy has always been a conservative choice - not anymore.

Are you running the GTK3 version of pMusic or the one in woofCE?

01micko commented 2 years ago

I've been using the gtk3 version of pmusic in my devel environment. It mostly works fine. Great job! The above developments are pure woof so the gtk2 version is included, and works, but in a pure wayland environment it won't work as all X only applications don't. The curent focus is on wayland with Xwayland - an X server for wayland.

20220914_21h18m43s_grim

dimkr commented 2 years ago

Xwayland works very well in my bookworm64 development builds with dwl - even "big" applications like GIMP work fine.

zigbert commented 2 years ago

That's great to hear. I'll keep the development of pMusic outside woofCE until I have solved the major issues... First of all the drag'n'drop inside the playqueue.

01micko commented 1 year ago

@zigbert it seems only the old method works for gtk3 -Im not sure why.

EDIT: old solution in practical use:

https://user-images.githubusercontent.com/1019119/190877561-607fe04f-d091-46c0-a479-7609adbba7e5.mp4

zigbert commented 1 year ago

@01micko Yepp, the old solution works... though, not as sophisticated as the GTK2 way.

We might end up with this one.

Thank you for your reminder