> I think its clear that we have to stop adding things to 2.5.x > and turn it into a stable release. > > For that, we need to make sure we have a complete set of features, > get the documentation up to date and create test cases. > > I think I've seen todo lists from all the major players. Just keep > publishing them. (And try to make them get smaller over time.) Make > sure that test cases are part of your todo lists.
My plan is to remove the unnessesay "Closable","Maximizable","Iconifiable" and "AllowMaximizeFixedSize" since they correspond to "!" variants of "Unclosable","Unmaximizable","Uniconifiable" and "DisallowMaximizeFixedSize" Does it make sence to let the non-default styles be the only ones, and have the opposite styles as the default? I guess this should be done for all styles. But I guess this will be done for 3.0, since it breaks backwards compatablility. Also, I might add a "DisallowIconifyFixedSize" to complement "DisallowMaximize" fixed size. But I guess this would also call for a "DisallowShadeFizedSize". Or maybe this better wait until after 2.6. //Marcus -- 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]
