Hi Mikhael,
H, my previous reply seems to have gone astray ...
most of the old
API continues to work.
Almost:
No method add_defaultErrorHandler in FVWM::Module::Tk=HASH(0x9f8ae10) as
guessed from FVWM::Module::Tk::addDefaultErrorHandler at
Hi Dominik,
I *really* need instruction in the docs/DEVELOPER file if we want
the man pages on the web page to be up to date. I don't have the
slightest idea what I have to do. Help!
H, I did start writing some ... not sure if I finished it.
Here's what I had - I'll check/commit it
Hi Renato,
If so, I am just asking if it's possible for the www.fvwm.org web
server not to specify/override the encoding. Then, presumably, the
web browser would determine the encoding from the HTML header it
would render correctly.
Wouldn't it be easier to change the html man page
Hi all,
Just got back from holiday ... been reading through the posts but I'm
confused, maybe I missed something:
On Thu, Aug 16, 2007 at 05:48:05PM -0500, FVWM CVS wrote:
CVSROOT: /home/cvs/fvwm
Module name: fvwm
Changes by: domivogt07/08/16 17:48:05
Modified files:
Log message:
* Check for sed, perl and tbl, needed to build docs.
Why do we need perl to build the documentation?
Because of the script doc/util/genAllCommands.pl.
Pretend it's not there. Delete it from CVS if it really bothers you
(I can keep my own version). I only wrote it to
Hi Viktor,
On Thu, Aug 16, 2007 at 05:05:21PM -0500, FVWM CVS wrote:
CVSROOT: /home/cvs/fvwm
Module name: fvwm
Changes by: griph 07/08/16 17:05:21
Modified files:
doc: ChangeLog
doc/fvwm : Makefile.am focus.xml
Log message:
* run manpage
Hi Viktor,
Is xsltproc case-insensitive?
With a case-insencitive filesystem (i.e. on Mac OS X or Cygwin). It
complained about recorsion in file Focus.xml, line 16, which really
was the file focus.xml. And the generated manpage had four leels of
recursion around there and did not include
Hi Serge,
Links for 'Obsolete or Deprecated' commands in file
'doc/groupedCommands.html' are broken (they missing .html suffix).
Attached patch fixes this.
Applied. Thanks.
Scott. :)
Log message:
* Write fvwm in lower case everywhere
I disagree with this policy.
(sigh, FVWM has been popping up all over
the place since the last time I cahanged this)..
That's because lower case acronyms are counter-intuitive uncommon.
The standard convention is to spell acronyms in
Hi Dominik,
I notice you made a change to doc/Makefile.am. Did that fix your
problem? I'm surprised if it did.
No, I just reformatted it slightly:
I was referring to this change:
- @ cp $(srcdir)/$@ $@
+ @cp $(srcdir)/$@ $(top_builddir)/doc/$@
I notice you've changed it to:
Hi Dominik,
So, configure isn't correctly disabling Xcursor support?
Maybe. Does it still compile or link with libxcursor?
Yep: (I copied the make output appended -lXcursor)
[EMAIL PROTECTED]:~ cd fvwm/cvs.0/build.2/bin
[EMAIL PROTECTED]:~/fvwm/cvs.0/build.2/bin gcc -Wall
Hi Dominik,
I've fixed the
problem that shows up in that file. Does it still happen with
current cvs if you build from scratch?
Fixed now, thanks.
Scott.
On Mon, Jul 16, 2007 at 10:04:26PM +0200, Dominik Vogt wrote:
On Tue, Jul 17, 2007 at 12:27:15AM +1000, Scott Smedley wrote:
But I'm still getting lots of errors in libs/FRender.c.
The fix requires that I link with -lXrender.
But which makefile to edit? The build/make system
Hi Simon,
Are you related to Viktor? Just curious.
I've made the SVG rendering options documentation section look much
better with the new html output. A few descriptive images really makes
a difference.
It sure does!
Your patch is good. Can I ask you to tidy up the formatting a little?
This seems something trivial, but I can't seem to find the real solution.
Ditto. (See the Problems building snap-20070713 thread.)
Just out of curiosity, what distro are you using? what version of make?
Scott.
But I'm still getting lots of errors in libs/FRender.c.
The fix requires that I link with -lXrender.
But which makefile to edit? The build/make system is too complicated
for me. :(
Scott.
On Sun, Jul 15, 2007 at 09:52:28PM +0200, Simon Griph wrote:
I've made the SVG rendering options documentation section look much
better with the new html output. A few descriptive images really makes
a difference.
Looking good.
Hi all,
I need confirmation I'm not crazy.
This works ok (substitute rxvt for xterm if appropriate):
AddToFunc fn I Exec exec rxvt $*
fn -e sleep 4
this is ok too:
AddToFunc fn3 I Test (x rxvt) Exec exec rxvt $*
fn3 -e sleep 4
but this isn't:
AddToFunc fn2
Test (x rxvt) + I Exec exec rxvt
Hi Dominik,
Should we upgrade to the GPLv3?
I'm happy for any of my contributions to be licensed using GPLv3.
(not that permission is required with the v2 or any later version
clause in the existing GPLv2 licence.)
I'd like to see FVWM migrate to GPLv3 soon, allowing a reasonable time
(~1
Hi Victor,
* use more precise docbook tags in many places
Your changes are good. However, a cursory inspection of the HTML output
shows something isn't quite right. There's a strange character in the
section headings (after the section number).
eg. It looks like 1.,Name instead of 1. Name.
I
Hi all,
How were the images on the documentation web page created?
http://www.fvwm.org/documentation/
I need to create another one for a link to the HTML documentation.
Would anyone like to volunteer to create one for me? Using:
http://www.fvwm.org/doc/unstable/
Scott. :)
Hi Uwe,
I want to modify an entry in fvwm-web/navgen_write/navigation.inc
but there is a comment at the top:
// This file is generated automatically by navgen.
How do I generate this file? Which file should I edit so that it will
add a new entry?
Scott. :)
As you can see in the picture, for some reason, the text on the Timeout
label overlaps the text on the last button, so I think that this might
be some kind of overflow
H. There is a race condition in the FvwmForm module. A button
press can trigger a call to RedrawItem() at the same time
This is just
intended to work as a simple Test modification, by reusing all what's
there, and not to provide any advanced conditional functionality,
...
get rid of ugly bash tricks to do something as simple as
to decide the size of a panel.
The if-syntax patch I wrote some time ago
Hi Dominik,
* There is lots of markup in the examples which should not be
there (commands and command options).
It conveys extra information (about what is a builtin command). I
consider it an improvement, but I can remove it if you feel strongly
about it.
* All section headers look the
Hi Dominik,
If you do not want to produce this documentation please use:
./configure --disable-htmldoc
As the process take four times longer than building the
executables, may I suggest that
a) the html pages are not built unless you specifically ask for
them,
Ok. I will
Hi Dan,
Just woke up and had to try this...
That's the kind of enthusiasm I like! :)
When it got to the docs, it started printing this warning:
make[3]: Entering directory `/home/dane/src/fvwm/build_fvwm2_5_20/doc/fvwm'
Generating authors.html
../../../fvwm2_5_20/doc/fvwm/authors.xml:6:
Hi Dan,
I think the key is that I build from OUTSIDE the source dir.
I still get the same problems.
You are correct - fixed now.
Thanks,
Scott. :)
Hi Dominik,
The current
state of the XML documentation prevents me from writing any
documentation. As almost everything I do has to be documented, it
prevents me to do almost anything.
I understand your concerns about the man-page output not being
rendered perfectly I'll endeavour to fix
Hi all,
I have been working on converting the FVWM documentation into DocBook
format. You can view some preliminary HTML results on-line.
http://members.optusnet.com.au/~scott.fvwm/index.html
The most interesting links, so far, are:
All Commands
Grouped Commands
Modules
FVWM man page
Hi all,
I notice that FVWM has a command called GnomeShowDesks, yet it is
not documented in the man page.
Is that ok?
Scott.
Can someone please fix the Google search thingy on this page:
http://www.fvwm.org/contact/
It should be using:
site:www.mail-archive.com
not:
site:www.hpc.uh.edu
The -inurl specifiers probably need updating too.
Scott. :)
Hi Mikhael,
I tried out your ModuleConfig tracker with FvwmTabs - it works great.
Should I expect to get an 'observation' if I dynamically change
config parameters? (using FvwmTalk or FvwmCommand) The dynamic values
are only propogated after I restart FvwmTabs.
Also, you need to
33 matches
Mail list logo
