On Mon, Oct 24, 2011 at 06:54:09PM +0100, Harry portobello wrote: > Hullo, > > On 24 October 2011 17:28, <des...@verizon.net> wrote: > > Harry portobello <harryportobe...@gmail.com> writes: > > > >> Hi, > >> > >> On 22 October 2011 11:23, Thomas Adam <tho...@fvwm.org> wrote: > >>> Hello all, > >>> > >>> This has been a while coming since 2.6.0 was released. But I said at the > >>> time that since there was no longer ever going to be a split between > >>> stable/unstable, and that there was only ever rolling-stable releases, > >>> that > >>> there was now never any right time to make changes which have an impact. > >>> > >>> This is one of them. > >> > >> Is this really the right thing to do? Really? How did you come up with > >> this list of depreciated modules to start with? What happens if > >> someone with a config theyve had for ages needs to use a module youve > >> depreciated? Will you personally have to provide the functions of that > >> module in some way? > >> > >> Can you not just leave these modules alone? > > > > Deprecating junk is a time honored Fvwm tradition. > > > > Reducing the size of the code base helps developers. > > As it is, Fvwm has grown so large that I can't keep up with > > the complexity. > > > > Anyway, Tom has done the right thing. He made a proposal and > > now he's getting feedback. > > Maybe. But time honored traditions are grating - when functionality > already exists and is removed for no good reason. I like FvwmTaskBar > but won't get to use it again - instead I have to use two modules I > don't know anything about. There's no thought gone in to this and > will force users to learn things they didn't need to before. I am also > amazed that mail checking is now left up to the user when it's built > in to FvwmTaskBar already! > > Can these modules not be archived and marked as unmaintained which > would still allow users to use them if they chose? > > Please! More thought needed =) >
Functionality is not being removed. With FvwmButons + FvwmIconMan you have way more functionality than FvwmTaskBar. Since FvwmButtons + FvwmIconMan can do everything and more than FvwmTaskBar, there is no reason to keep and matain FvwmTaskBar. FVWM is a small project and mataining multiple tools that do the same thing just takes up the developers time they could spend adding new functionality. The goal is not to remove any functionality, but provide it though a smaller set of well tested modules. The point of Depericating is to give the users time to change their configs and learn the more accepted tool. Its not like this module is just going to disapear in the next release. Last this is an opensource project, You can grab the source code and matain your own unmatained, unoffical FvwmTaskBar module as you suggested. Though taking the time to learn the other options you may find that not only can you achive your current config, have more flexablity. jaimos
