On Sat, May 05, 2001 at 06:25:52AM +0200, Olivier Chapuis wrote:
> Le Samedi  5 Mai 2001 01:15, vous avez écrit :
> > On 04 May 2001 22:04:21 +0200, Olivier Chapuis wrote:
> > > fvwm-ewmh is almost ready. I will send  the announcement that
> > > [snip]
> > > Any suggestions or comments are really welcome.
> >
> > This is a suprise to me. Seems like a serious work.
> 
> I warn the fvwm-workers a few weeks a ago:
> 
> http://www.hpc.uh.edu/fvwm/archive/0104/msg00141.html
> 
> but maybe I was not clear. Also, I was not sure that I will finish
> the work at all (but it was so funny to see kicker respecting all my desire;
> on the other hand kdesktop is really a problem).
> 
> > I guess we should just include FvwmNetHints module and patch FvwmPager.
> > Including a module, which does not need a configure support is as simple
> > as adding one word in modules/Makefile.am.
> >
> 
> I am not sure that we have to include fvwm-ewmh in FVWM now. Maybe,
> we can include it in the 2.4.x series. The reasons are:
> - We should not do anything that delays 2.4.0
> - fvwm-ewmh needs some change to fvwm2 source codes (for the (mini)icons
> functionality and for applications of Desktop type). 
> - The FvwmPager patch is a bit sensible: there is a "big" change to the
> windows stacking Pager code.
> - In fact, FvwmNetHints needs a change to the configure procedure: the
> FVWM configure procedure define IMLIB if it found the gdk imlib as
> FvwmNetHints needs only the imlib (this save a lot of memory).
> - The code and the man page are really alpha.

What about the more esoteric features of the spec like unicode
icon titles?  The spec demands that the window manager provides a
unicode window title even if the application did not.

Bye

Dominik ^_^  ^_^

--
Dominik Vogt, [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
--
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]

Reply via email to