Re: Release announcement (WAS: Re: FVWM: 2.6.0 release candidates?)
On Tue, Apr 12, 2011 at 01:34, Thomas Adam tho...@fvwm.org wrote: Sadly, Alex is no longer with is, and he would have been proud to see the replace second is with us: ...is no longer with us... FVWM he knew, as being released as stable, so this release is dedicated to him. May he still rest in peace. -- Met vriendelijke groeten / With kind regards Hans Voss --- * Infrastructure Architect * Infrastructure, Cloud, Open Source, Networking and Security * General Open Sourcerer -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- * hans.v...@gmail.com * hans.v...@logica.com * Skype: j.j.voss * Twitter: hansvoss * Facebook: http://facebook.com/hans.voss --- * Linked In page: http://www.linkedin.com/in/hansvoss * My blog: http://jazzterdaily.blogspot.com - Tech and other news that caught my attention. * Google Reader: My shared News feed: http://tinyurl.com/hansvoss-feed -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Re: Release announcement
Thomas Adam tho...@fvwm.org writes: On Tue, Apr 12, 2011 at 12:34:48AM +0100, Thomas Adam wrote: On Mon, Apr 11, 2011 at 10:35:41PM +0100, Thomas Adam wrote: On Mon, Apr 11, 2011 at 10:00:39PM +0100, Thomas Adam wrote: On Mon, Apr 11, 2011 at 09:40:52PM +0100, Thomas Adam wrote: If anyone feels like somethings should be added/removed/augmented, let me know. More updates -- but the whole document this time -- mostly from authors I've forgotten about, so please, keep your updates coming. I appreciate it: Another update: Unless anyone says so, I'm releasing this tomorrow evening at some point. Just want to say the release announcement is excellent. Nice job.
Release announcement (WAS: Re: FVWM: 2.6.0 release candidates?)
On Mon, Apr 11, 2011 at 10:00:39PM +0100, Thomas Adam wrote: On Mon, Apr 11, 2011 at 09:40:52PM +0100, Thomas Adam wrote: If anyone feels like somethings should be added/removed/augmented, let me know. More updates -- but the whole document this time -- mostly from authors I've forgotten about, so please, keep your updates coming. I appreciate it: FVWM 2.6.0 released! It's been almost five years since the last stable release of FVWM (2006) and almost ten years since the development version of FVWM (2.5.X) which became this latest stable release was started! A lot of hard work from many talented individuals has made this release possible. Highlights == In no particular order: * EWMH support, including support for managing different window types (docks for example). * Colorset commands replace FvwmTheme (which is now deprecated) * WindowStyle command applies a style to a specific window only. * XFT fonts are supported, per locale. * Focus-specific policies supported as styles (FP*, !FP*) * FocusStyle command allows styling of focus policies specifically. * Dynamic actions can be sent to most modules whilst they're running to customise their behaviour (SendToModule). * Gettext support introduced for output strings (most commonly seen on menu items.) * Mouse gestures (libstroke) bindings are available. * New module FvwmProxy to manage moving windows around. * New module FvwmWindowList to make the list of running windows more customisable over the builtin WindowList command. * Variable placeholders ($w, $d, $c) deprecated in favour of newer formats. Also, the number of variable placeholders has been expanded. - $[func.context], $[w.desk], $[w.layer], etc. * Nesting of placeholders is also allowed. * FvwmEvent: The PassId option is deprecated as actions always run within a window context. * Many new conditional commands with different options. * New style command Unmanaged to make certain windows completely divorced from FVWM's control. * New command FakeKeyPress. * Window-specific key/mouse bindings. (Bindings no longer have to be global.) * Many new style options: - FixedSize - FixedPosition - MoveByProgramMethod - UseTitleDecorRotation - IconBackgroundColorset - IconTitleColorset - HilightIconTitleColorset - IconTitleRelief - IconBackgroundRelief - IconBackgroundPadding - Closable - Iconifiable - Maximizable - AllowMaximizeFixedSize - PositionPlacement - InitialMapComand Plus many others... * Window states are now available to identify windows to perform groups of commands on. * fvwm-menu-desktop uses the XDG menu specification. * PNG/SVG support for icons. * Menu-context bindings. * The name style names match against can be augmented by the X-resource fvwmstyle. * New fvwm-convert-2.6 script to convert older fvwm 2.4.x config files. * Bugfixes! There are of course significant bug fixes gone into this release; far too many to list here, and many of them so specific to the development version alone that listing them is out of context when comparing them to the last stable release. Overall, a number of bug fixes for memory management, and ease of managing windows has happened. Upgrading from FVWM 2.4.X - 2.6.0 == It is worth spending some time looking at the dependencies at FVWM's disposal. None of them are required per se for FVWM to work: * Xinerama * Readline * Fribidi * XFT * Iconv * PNG * SVG * XPM * XRender * Stroke * Xsm * Xcursor * SM (Session Manager) Note that not all of these are external libraries per se -- some of them are merely facets of an XServer's configuration, but a lot of it will depend on the platform FVWM is running on. Preferred way of upgrading your configuration file == In the old stable (2.4.X), the path to the default user config file is now: $ ~/.fvwm/config by default, although the older paths of: $ ~/.fvwm/.fvwm2rc $ ~/.fvwm2rc are still supported; just deprecated in favour of ~/.fvwm/config. Note that the INITIALIZATION section in man fvwm lists the other locations FVWM might also look in to find a valid config file. Since there's been some syntax changes, a handy script can be used -- fvwm-config-2.6 to convert a 2.4.X style config file. Please see the man page for fvwm-convert-2.6. History === It's taken almost ten years for FVWM 2.6.0 to arrive. In that time, FVWM has had contributions from numerous people -- many of them can be found here: http://fvwm.org/authors/ Whilst it is unfair to single any one particular person out, it is without question that I (Thomas Adam) would like to pay particular homage to the following people (again in no particular order): * Dominik Vogt -- for being one of the most useful sources of information on FVWM to date, and making it
Re: Release announcement (WAS: Re: FVWM: 2.6.0 release candidates?)
On Mon, Apr 11, 2011 at 10:35:41PM +0100, Thomas Adam wrote: On Mon, Apr 11, 2011 at 10:00:39PM +0100, Thomas Adam wrote: On Mon, Apr 11, 2011 at 09:40:52PM +0100, Thomas Adam wrote: If anyone feels like somethings should be added/removed/augmented, let me know. More updates -- but the whole document this time -- mostly from authors I've forgotten about, so please, keep your updates coming. I appreciate it: Another update: * Added Scott Smedley. * Other slight touch-ups. I don't plan on doing anything else on this until tomorrow now. FVWM 2.6.0 released! It's been almost five years since the last stable release of FVWM (2006) and almost ten years since the development version of FVWM (2.5.X) which became this latest stable release was started! A lot of hard work from many talented individuals has made this release possible. Highlights == In no particular order (and neither an exhaustive list): * EWMH support, including support for managing different window types (docks for example). * Colorset commands replace FvwmTheme (which is now deprecated) * WindowStyle command applies a style to a specific window only. * XFT fonts are supported, per locale. * Focus-specific policies supported as styles (FP*, !FP*) * FocusStyle command allows styling of focus policies specifically. * Dynamic actions can be sent to most modules whilst they're running to customise their behaviour (SendToModule). * Gettext support introduced for output strings (most commonly seen on menu items.) * Mouse gestures (libstroke) bindings are available. * New module FvwmProxy to manage moving windows around. * New module FvwmWindowList to make the list of running windows more customisable over the builtin WindowList command. * Variable placeholders ($w, $d, $c) deprecated in favour of newer formats. Also, the number of variable placeholders has been expanded. - $[func.context], $[w.desk], $[w.layer], etc. * Nesting of placeholders is also allowed. * FvwmEvent: The PassId option is deprecated as actions always run within a window context. * Many new conditional commands with different options. * New style command Unmanaged to make certain windows completely divorced from FVWM's control. * New command FakeKeyPress. * Window-specific key/mouse bindings. (Bindings no longer have to be global.) * Many new style options: - FixedSize - FixedPosition - MoveByProgramMethod - UseTitleDecorRotation - IconBackgroundColorset - IconTitleColorset - HilightIconTitleColorset - IconTitleRelief - IconBackgroundRelief - IconBackgroundPadding - Closable - Iconifiable - Maximizable - AllowMaximizeFixedSize - PositionPlacement - InitialMapComand Plus many others... * Window states are now available to identify windows to perform groups of commands on. * fvwm-menu-desktop uses the XDG menu specification. * PNG/SVG support for icons. * Menu-context bindings. * The name style names match against can be augmented by the X-resource fvwmstyle. * New fvwm-convert-2.6 script to convert older fvwm 2.4.x config files. * Bugfixes! There are of course significant bug fixes gone into this release; far too many to list here, and many of them so specific to the development version alone that listing them is out of context when comparing them to the last stable release. Overall, a number of bug fixes for memory management, and ease of managing windows has happened. Upgrading from FVWM 2.4.X - 2.6.0 == It is worth spending some time looking at the dependencies at FVWM's disposal. None of them are required per se for FVWM to work: * Xinerama * Readline * Fribidi * XFT * Iconv * PNG * SVG * XPM * XRender * Stroke * Xsm * Xcursor * SM (Session Manager) Note that not all of these are external libraries -- some of them are merely facets of an XServer's configuration, but a lot of it will depend on the platform FVWM is running on. Preferred way of upgrading your configuration file == In the old stable (2.4.X), the path to the default user config file is now: $ ~/.fvwm/config by default, although the older paths of: $ ~/.fvwm/.fvwm2rc $ ~/.fvwm2rc are still supported; just deprecated in favour of ~/.fvwm/config. Note that the INITIALIZATION section in man fvwm lists the other locations FVWM might also look in to find a valid config file. Since there's been some syntax changes, a handy script can be used -- fvwm-config-2.6 to convert a 2.4.X style config file. Please see the man page for fvwm-convert-2.6. History === It's taken almost ten years for FVWM 2.6.0 to arrive. In that time, FVWM has had contributions from numerous people -- many of them can be found here: http://fvwm.org/authors/ Whilst it is unfair to single any one particular person out, it is without
