Remko Troncon <[EMAIL PROTECTED]> writes: > I agree with Uwe. The current approach is a lot easier, much more > maintainable, and gives a good overview. The threshold is a little bit > higher, because you have to actually send a mail to someone, but maybe > that isn't really such a bad thing after all ;-)
If the maintainer of the homepage agree with that, i will be happy ... :) > IMHO, wiki is only suitable for early stages of a work in progress, when > things are in a state of flux, and having centralized documents is a lot > of overhead on synchronization. But once things stopped moving, the > whole wiki hierarchy (which is usually a huge mess by then in which you > get lost very quick) should be organized into centrally administered > documents. It could be very hard to get a centralized document of configuration scripts. But there will be a dozen differant ways to make a panel with FVWMButtons for example. How do you want to deal with that in a centralized document? I think you talk about a manual but i want seomthing for configuration. In the moment all of these things are put in the faq. Okay for the moment ... but a faq could become very unreadable if add a dozen alternatives for every problem on it ... Mario -- Chaos reigns within. Reflect, repent, and reboot. Order shall return. -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
