Re: FvwmRearrange bug if Style TitleAtLeft/TitleAtRight is used
Hi, On Wed, Feb 29, 2012 at 01:15:38PM +0100, Tiziano Zito wrote: > On Mon 27 Feb, 18:02, Thomas Adam wrote: > > On Feb 27, 2012 5:34 PM, "Tiziano Zito" wrote: > > > > > > Hi FVWM developers, > > > > > > first of all thank you for maintaining my window manager :) > > > > Patching this to use the TITLE_AT_* macros is the preferred way for this, > > as you can then get the frame geometry correctly. Can you patch it this way > > instead? It's easy enough. > > OK, I'll give it a try. How is this progressing? Do you want me to fix it, or do you have something in progress? -- Thomas Adam
Re: fvwm html pages with asciidoc
On Tue, Mar 13, 2012 at 01:25:48PM +0100, Thomas Funk wrote: > Hi Thomas, > > I've played around with the asciidoc manpages to include them into > fvwm html > pages (interesting for fvwm-web). Thanks for this, as well as the other work I've not yet had time to review. I'll try and look at it soon, it's just that I'm rather busy at the moment. I don't want any work done on the fvwm-web side of things at all for now. So you can stop here, and later when I've got the documentation reviewed, I'll take a look at fvwm-web. -- Thomas Adam
Re: fvwm for Fedora
On Mon, Mar 12, 2012 at 11:18:14PM -0500, Ranjan Maitra wrote: > Hi, > > I have been looking at the fvwm RPM for fedora and i noticed that the > following patches are in there: > > fvwm-0005-Explicitly-link-against-fontconfig.patch This has long since been fixed in 2.6.X, AFAIK. > fvwm-2.5.21-menu-generate.patch Redundant with fvwm-menu-desktop, although work is underway to improve it. > fvwm-2.5.30-mimeopen.patch > fvwm-2.5.30-more-mouse-buttons.patch > fvwm-2.5.30-xdg-open.patch For these, see: http://www.mail-archive.com/fvwm-workers@fvwm.org/msg02776.html > There is also the following: > fvwm-xdg-menu.py Redundant? > From looking at the archives, it is not clear to me if the last one > should be included/excluded? Are any of the above no longer necessary > for fvwm-2.6.4? See above. > Separately, I also was wondering: do any of these patches conflict with > the following more commonly used patches (for Gentoo/ArchLinux)? No. They're not supported. > Finally, does anyone here know what is going on wrt Fedora's fvwm? > Bugzilla requests there do not seem to have been even checked out for > months, sometimes years, and it is not clear whether the WM has any > support or not. I'm hoping Jason Tibbitts will respond as he knows a little about what Fedora do, but as far as I am concerned, I only work with what's posted here, upstream. Hence, if you don't report bugs, they won't get fixed. -- Thomas Adam
fvwm for Fedora
Hi, I have been looking at the fvwm RPM for fedora and i noticed that the following patches are in there: fvwm-0005-Explicitly-link-against-fontconfig.patch fvwm-2.5.21-menu-generate.patch fvwm-2.5.30-mimeopen.patch fvwm-2.5.30-more-mouse-buttons.patch fvwm-2.5.30-xdg-open.patch There is also the following: fvwm-xdg-menu.py >From looking at the archives, it is not clear to me if the last one should be included/excluded? Are any of the above no longer necessary for fvwm-2.6.4? Separately, I also was wondering: do any of these patches conflict with the following more commonly used patches (for Gentoo/ArchLinux)? 01-TranslucentMenus.patch11-MultiBorder.patch 02-ColourBorders.patch 12-FvwmButtonsTips.patch 03-ResizeOutlineThin.patch 13-FvwmIconMan.patch 04-Conditionals.patch14-Hover.patch 05-FlatSeparators.patch 15-FirstItemUnderPointer.patch 06-BorderUnderTitle.patch16-ThinGeometryProxy.patch 07-InactiveFont.patch 08-FluxRoundedCorners.patch 09-TopBorder.patch 10-ButtonWidth.patch Finally, does anyone here know what is going on wrt Fedora's fvwm? Bugzilla requests there do not seem to have been even checked out for months, sometimes years, and it is not clear whether the WM has any support or not. Many thanks and best wishes, Ranjan
fvwm html pages with asciidoc
Hi Thomas, I've played around with the asciidoc manpages to include them into fvwm html pages (interesting for fvwm-web). Atached is a working example which uses two asciidoc manpages (FvwmForm and FvwmTheme) inside the actual Fvwm page. It is based on the asciidoc webpage example. On Debian you'll find it under /usr/share/doc/asciidoc/examples/website/ Used componnents: - layout_fvwm.conf to build the manpage inside a fvwm page - build-website.sh create the html pages - manpage.css - stylesheet for the manpage formating. It is very poor at the moment, and need some changes to fit the fvwm look. But that's no prob, cause if you create a standalone asciidoc html page with "asciidoc -f manpage " the complete formating will be found at the beginning of the page. - style.css the original fvwm style sheet I've put two links for testing in FvwmForm: -> external link: FvwmTheme - in "*FvwmForm: Colorset n" -> internal link: DEFAULTS - in "*FvwmForm: Back color" These links doesn't occur inside a manpage. See for yourself - create with "create-manpage.sh FvwmForm.txt" a manpage and view it. I hope this will help to switch completely to asciidoc. It's amazing how easy it is to build different document types with one asciidoc document. Cheers, Thomas asciidoc-html.tgz Description: application/compressed-tar
