Dominik Vogt <fvwm-workers@fvwm.org> writes: > On Thu, Jul 05, 2001 at 01:12:24PM +0200, Olivier Chapuis wrote: > > On Thu, Jul 05, 2001 at 10:36:30AM +0200, Dominik Vogt wrote: > > > On Wed, Jul 04, 2001 at 12:00:04PM +0200, Olivier Chapuis wrote: > > > > I am glad to announce the third release of fvwm-ewmh: version 0.3 > > > > > > > > fvwm-ewmh is made up of a module, FvwmNetHints, and a patch against > > > > the last stable FVWM source tree (fvwm-2.4.0). With these, FVWM can > > > > handle Extended Window Manager Hints from the freedesktop group. > > > > This allows running FVWM with KDE version 2 and get a special > > > > support for applications based on the development version of GTK+ > > > > (aka GTK+ version 2). > > > > > > Should we aim to include this in 2.4.1 along with Xinerama > > > support? > > > > > > > I do not know. The main problem is that at the present time fvwm-ewmh > > need an other release timing than fvwm (it needs more release). The > > other problem is that I get very few feed back so fvwm-ewmh is still > > alpha for the world (but beta for my machine, I call this state pre-beta). > > So, do we want alpha code in fvwm-2.4.1? > > Maybe the answer for these problems can come from the release scheduling > > for 2.4.1. > > There are other problems: > > - the English of the doc > > That's not really a problem. I'd be willing to proof read it. > > > - In my opinion FvwmNetHints should be integrated in fvwm3 (as a > > compile time option and not as a module) > > I believe we schould have ewmh support way before 3.0. With all > the changes planned for 3.0, it will take years before the next > stable realease.
It might be a good idea to put fvwm-ewmh and possibly Xinerama into branches. When the branch is done it can be merged into 2.4.x and released. -- Dan Espen 444 Hoes Lane Room RRC 1C-214 E-mail: [EMAIL PROTECTED] Piscataway, NJ 08854 Phone: (732) 699-5570 -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]