On 16 Mar 2009 00:52:27 +0100, Dominik Vogt wrote:
On Sun, Mar 15, 2009 at 07:00:05PM +, Mikhael Goikhman wrote:
On 15 Mar 2009 00:34:16 +0100, Dominik Vogt wrote:
[snip]
To be interactive the module should both listen to fvwm and to the
input (mouse, keyboard) in the same event
On Sun, Mar 15, 2009 at 07:00:05PM +, Mikhael Goikhman wrote:
On 15 Mar 2009 00:34:16 +0100, Dominik Vogt wrote:
[snip]
To be interactive the module should both listen to fvwm and to the input
(mouse, keyboard) in the same event loop. Don't you agree?
Yes. And why does this rule
2009/3/14 Dominik Vogt dominik.v...@gmx.de:
[...]
As far as I remeber:
* deb and rpm: We got bug reports that nobody took care of.
* html documentation: It's mostly unusable for me and way too
complex. There are be other, simpler ways to achive the same
benefits (asciidoc?).
i'm
On Sat, Mar 14, 2009 at 11:13:21AM +, Thomas Adam wrote:
2009/3/14 Dominik Vogt dominik.v...@gmx.de:
But this is almost thrust upon existing developers. Dominik, you
obviously fall into this category: could you fix something in perllib
or FvwmTabs if it broke?
No, I couldn't.
Ciao
2009/3/14 Mikhael Goikhman m...@homemail.com:
[...]
One of the examples of a pragmatical asciidoc that may be considered is
POD (Plain_Old_Documentation article in Wikipadia). Well, all perl
documentation in fvwm is already in POD, and the corresponding html is
generated from it.
That's
On 14 Mar 2009 15:34:52 +, Thomas Adam wrote:
2009/3/14 Mikhael Goikhman m...@homemail.com:
[...]
One of the examples of a pragmatical asciidoc that may be considered is
POD (Plain_Old_Documentation article in Wikipadia). Well, all perl
documentation in fvwm is already in POD,
