Fluxbox 1.3.6 Released

jones_supa writes: After nearly two years since the previous release, the Fluxbox team has released version 1.3.6 to start off the new year. Like most Linux geeks already know, Fluxbox is the long-standing X window manager derived from Blackbox. The new version (announcement) puts emphasis on quality assurance and takes care of fixing a bunch of critical bugs: clocktool problems, rendering long text, race condition on shutdown, lost keypresses after workspace switch, corruption of fbrun-history, and resize and move problems. The two new features are an ArrangeWindowsStack action and treating Windows with a WM_CLASS as DockApp as DockApps. Translations for Bulgarian, Hebrew and Japanese also got updates. The Fluxbox project sends many thanks to all the contributors.

Comments

I know what it is

[Osgeld]

but the description of it in this summary is pointless

  "Like most Linux geeks already know, Fluxbox is the long-standing X window manager derived from Blackbox"

lets say I am not a linux geek, I have linux but its ubuntu or min and whatever ships with that is all I know as far as desktops go? what is fluxbox? oh its derived from blackbox, gee fucking thanks for that useful bit of info, so why even have it in there?

Re:Wayland / serious question

[serviscope_minor]

Wayland is just like X. A framework to build gui stuff on. It is X compatible too and supports the protocol.

No, it isn't compatible with X, no more than Windows or OXS is compatible with X (both can run an X server).

Wayland's view of the world is essentially a bunch of surfaces, collections of which belong to programs. a program can draw updates to the surface then inform Wayland that the drawing updates are done.

The wayland compositor is on the other end and decids how to draw the surfaces to the screen (or whatever). It also distributes input events to the various surfaces.

For X on the other hand, the server owns the surfaces and is responsible for drawing them. Typically, a window manager arranges them on the screen and allows them to be moved around (though X can run without a WM).

You can rnu X on top of a Wayland compositor. the server manages windows as surfaces then hands them to Wayland to draw. There's no theoretical reason that the Wayland compositor couldn't then hand any surfaces not already managed by X straight back to X. Then an X11 window manages could be used on Wayland. In other words, the compositor could only draw to the screen durfaces from the X server and then route any others through the X server first.

There'd probably be problems with dnd or copy and paste of anything other than text due to the way the protocols differ. Those things could hypothetically be fixed as well: thost protocols on X are surprisingly sane and pleasant.

[outdated rant about x]

If you think X ran slowly on an old machine, try running ANY piece of software on it. I guarantee X worked better then than any modern program you run and enjoy now ever would have.