Sorry for my English.
My friend spoke me that from fvwm it is possible to make all. Whether it is possible to make such scheme of a window: heading of a window on the right, graphic borders on three parties of the window, two graphic corners.
http://img27.picoodle.com/img/img27/3/8/13/f_windowm_5ba97cf.png
ps graphic == image texture
You want the unofficial patches — from me and someone else. With those, then it’s possible.
– Thomas Adam
MultiBorder from fvwm-patchset? (http: // jesgue.homelinux.org/fvwm-files/) And it will make graphic corners?
Yes, though there might be lots of versions there. I patched some of them myself to allow them to continue working while the fvwm cvs changed. However I am not using fvwm since some times, and it’s been even longer since I stopped using those patches, so I can’t guarantee they’ll work. Al I can say is that if they do, then they can do what you described graphically on your first post. Nothing else.
Also, note that the numbered patches are cumulative, that means that some of them might need hand editing of the source unless you apply all the previous ones as well.
EDIT: Some of my configs also have graphical decos, I think. Amongst them ports of some very famouse decos like qnx or crux, just in case you want them.
What patchset from jesgue.homelinux.org/fvwm-files/ for fvwm-2.5.18?
I am not sure, I would start with this one:
jesgue.homelinux.org/fvwm-files/ … r2.tar.bz2
And if it doesn’t work, then try using previous versions until you find one that can patch cleanly.
However, is there any reason why you can’t use the 2.5.26?
The reason in that at attempt to impose a 12-MultiBorder.patch patch from fvwm-2.5.26-patchset.tar.bz2:
fvwm-2.5.26 # patch -Np1 -i 12-MultiBorder.patch
patching file fvwm/borders.c
Hunk #1 succeeded at 1281 (offset -373 lines).
Hunk #2 FAILED at 1474.
Hunk #3 succeeded at 1539 (offset -422 lines).
Hunk #4 succeeded at 1563 (offset -422 lines).
Hunk #5 FAILED at 1577.
Hunk #6 FAILED at 1641.
Hunk #7 FAILED at 1751.
Hunk #8 succeeded at 1789 with fuzz 1 (offset -439 lines).
Hunk #9 FAILED at 3416.
Hunk #10 FAILED at 3866.
6 out of 10 hunks FAILED -- saving rejects to file fvwm/borders.c.rej
patching file fvwm/builtins.c
Hunk #1 succeeded at 762 (offset -22 lines).
Hunk #2 succeeded at 1515 (offset -22 lines).
Hunk #3 succeeded at 1892 (offset -22 lines).
patching file fvwm/menus.c
Hunk #1 succeeded at 2614 (offset 130 lines).
Hunk #2 succeeded at 2753 (offset 130 lines).
Hunk #3 succeeded at 2801 (offset 130 lines).
Hunk #4 succeeded at 2816 (offset 130 lines).
patching file fvwm/menustyle.c
patching file fvwm/menustyle.h
Hunk #1 succeeded at 187 (offset -2 lines).
Hunk #2 succeeded at 237 (offset -2 lines).
patching file fvwm/screen.hFAILED me guards…
fvwm sources from latest portage ACCEPT_KEYWORDS=“~x86” emerge -f fvwm (/usr/portage/distfiles/fvwm-2.5.26.tar.bz2)
Remember that those patches are cumulative. There’s no guarantee that 12 will apply if you didn’t apply the ones that goes before, from 01 to 11. This is that way because some of them modify the same parts of the source code.
In case you are interested, I maintain an fvwm cvs live ebuild in the devnull overlay. You can read it here:
hg.core.ws/devnull/file/cd210d82 … 999.ebuild
You can also install the whole overlay using layman if you wish. There’s a USE flag that controls whether or not this patches are applied, you need to make sure it’s on (USE=“extras”).
Many thanks - all have turned out. And where I can particularly see an approximate code (fvwm config) for use multiborder?