#21 2017-01-08 03:25:36

daggoth

Member

Registered: 2016-01-02

Posts: 26

Re: Fvwm Window Manager - share configs, functions, all that jazz.

Can you elaborate on this? I've seen some references to Fvwm3 coming out, but haven't investigated any further.

From the mailing-list :-

To that end, the latest stable release (2.6.7) marks the end of the line for fvwm2.  This release is unique because it was my opportunity to remove all of the modules which I thought were no longer providing anything useful (because the functionality no longer exists outside of fvwm in certain applications, or because more widely-used modules in fvwm provided equivalent/better funtionality).  Indeed, this releases also includes a new default configuration.  I hope you find it useful.

In fact, I'm not envisaging any further work happening on fvwm2.X at all.  So what does this mean for fvwm?  In order for us to continue to make larger changes, we need to be able to break backwards compatibility and to make a lot of structural changes.  All of this goes towards a lot of other changes we'd like to make.  This therefore means that we will look at fvwm3 to do this.  This will be different to fvwm2.

So they have tied off fvwm2, and are now working on fvwm3. It may take a while. It seems that parts of the fvwm codebase are currently a mess. But by changing the fvwm syntax, the fvwm codebase can be made smaller and cleaner. Such that the development  of fvwm can continue forward indefinitely.

Initially, this code rewrite will neither add nor remove features from FVWM. A conversion script will be provided to update old configs. But I have placed my fvwm-2.6.7 package on hold for now - I expect some breakage when fvwm3 arrives.

Other links :-

Aspirational goals for fvwm3 - here

New format - here

Thread about new format - http://www.mail-archive.com/fvwm@fvwm.org/msg03023.html

Last edited by daggoth (2017-01-08 07:48:26)