FVWM: mwmborder style in 1.0.6

[elliot s]

I'm guessing it's 1.0.6 as borders.c is a few days old.

borders.c was changed so that mwmborder no longer creates a minimal
button relief.  It's either no border or raised/sunk.

Removing mwmborder from config restores the minimal window border, but
not button border.

I changed the 2 : 2 to 1 ; 1 on my copy of borders.c to return behavior.

What's the planned way of having minimal but existing relief in buttons?

Re: FVWM: FVWM3-1.0.0 is released

[elliot s]

Retrying from laptop since fvwm mail doesnt like my tablet gmail (html issue).

Is there a way to get a precompiled 64 bit version?
Perhaps put one up on the site?
I check pkgs.org but I assume it'll be a long time before it hits there.

Thanx

Re: FVWM: When will fvwm3 be ready to start trying out?

[elliot s]

Resending as it failed earlier...

I've been waiting for it to hit pkgs.org since I don't have a compiler. I
wish a 64 bit compiled version got put into bin so us small distribution
linuxes can use it. It's pretty generic so should work with anything.

Re: FVWM: FVWM3: RandR support ready for testing

[elliot s]

Can a (64 bit) compiled version be put in bin for those of use that
don't have a compiler?  I don't think theres much if any that are OS
dependent.  I just pull fvwm from whichever pkgs has the latest
version and it works.

I'm actually running puppy xenial.

Thanx

Re: FVWM: two questions about icons

[elliot s]

fvwm is a more of a window manager toolkit.  You use it to build your
own window manager.  That used to be more obvious when the default
config  was really uselessly minimal.

Re: FVWM: [Draft] New Configuration Format

[elliot s]

<<
BlockA \
 line1, \
 line2, \
 line3, \
 line4

 Is less visually appealing and can be more difficult locate errors than

 BlockB {
 line1,
 line2,
 line3,
 line4
 }
>>

There's the python method of blockingusing indentation.  WYSIWYG
I was skeptical at first, but now i like it.

if x:   # note the :
 y=z
a=1
if n:
a=3
b=1
else:
b = 0
print a,b
print y

Re: FVWM: [Draft] New Configuration Format

[elliot s]

What would be an example of what a user defined function looks like?
That's where most of the "needs easy reading and editing" happens.
Also, i would have a space between option and value.
So -f red, not -fred   (who's fred, and what's he doing in my rc file?)

Re: FVWM: [Draft] New Configuration Format

[elliot s]

If a conversion script can convert the current rc file to a code
friendly format, can a front end parser do that instead, so that we
keep the current user friendly format?

Re: FVWM: Per-monitor tags/groups

[elliot s]

>> It looks like your code is doing ChangeButton colorsets also.
>> Is that a post 2.6.6 change?
>
> Yes, on the master branch, will be in 2.6.7. No release date set for that,
> but master should be stable, so I urge you to try it.

Since i wasnt running xinerama, i only had one "screen". So instead i
edited the c code to get the pagers/taskbars to look at only the
windows on their half of the page, by checking against window's x.  It
would be nice if instead modules could be told which states to skip.
Then each window could dynamically control who uses it by setting
State.

FVWM: desktop per monitor

[elliot s]

I'd like to have one desktop per monitor (ie an independent pager
per monitor) with the ability to move or extend windows across the
monitors.  Basically, a double wide page, where each pager controls
the windows with their (0,0) on that page half. Having the page button
show the icon of the last focused window would be nice, if possible.

I assume the pagers could be faked by fvwmbuttons and scripting.
Has anyone already done that?
This would be via fvwm only (ie. no added software packages or system
config changes).

Thanx

Re: FVWM: desktop per monitor

[elliot s]

On 5/19/12, Dan Espen des...@verizon.net wrote:
 elliot s elliot...@gmail.com writes:

 On 5/19/12, Thomas Adam tho...@fvwm.org wrote:
 On 19 May 2012 22:28, elliot s elliot...@gmail.com wrote:
 I'd like to have one desktop per monitor (ie an independent pager
 per monitor) with the ability to move or extend windows across the
 monitors.  Basically, a double wide page, where each pager controls
 the windows with their (0,0) on that page half. Having the page button
 show the icon of the last focused window would be nice, if possible.

 Not possible without Xinerama and even then, you're encroaching on
 per-desktop support which isn't possible yet.

 I assume the pagers could be faked by fvwmbuttons and scripting.
 Has anyone already done that?

 The only thing you can do is use FvwmEvent to hold different pagers
 for each *desk* -- and make them stickyacrosspages for that desk,
 killing the other pagers as you move between desks.

 I don't know if this is what you're asking or not.  But likely what
 you're asking isn't possible yet, and no amount of scripting is going
 to help you.

 -- Thomas Adam

 I'm figuring on having a backing desktop that holds the windows that
 live soley on the right hand side of the page, and a variable holding
 the value of the current right hand page. When i press a page
 fvwmbutton, it moves all of the current right hand windows to the
 backing desk, page variable and moves to current desk the windows of
 the new page from the backing desk.  Pressing the real pager operating
 the left hand page moves all of the right hand current windows to the
 current left hand page. I dont want to use sticky style so as not to
 lose which right hand windows are truly sticky.

 Sorry, I've never used Fvwm's Xinerama support but it sounds to me
 like it might help do some of the things you want.

 http://www.fvwm.org/documentation/manpages/stable/fvwm2.php

 (search for xinerama)

 Have you tried it?

 --
 Dan Espen

I'm actually vnc'ing to fvwm, so theres only one server screen.

I started working on my plan.  I got the left and right halves of the
page to switch independently...the left side using the fvwmpager and
the right side using fvwmbuttons to swap its windows with backing
desks.

Unfortunately, the taskbar (fvwmbuttons/fvwmiconman) is combined for
the two sides.  I can't create 2 taskbars and tell them to use [w.x]
to (dont)show.

Re: FVWM: New default configuration wanted...

[elliot s]

I think, because of this, a default configuration is not that important.
 I think, a better idea could be to leave the default config as minimal
 as it is, and instead of changing the default config, better invest
 some time into an idea of offering some example configurations for
 new FVWM users.


It's easier to remove code from a maximal config than it is to figure
out how to to add functionality to a minimal config.

FVWM: (Icon)TitleFormat doesnt quite work like IndexedWindowName for one window

[elliot s]

Version 2.6.3:
Previous versions only added the (%t) when there was a repeated name.
The new code always adds it.
I worked around the %t in add_window.c by checking if count was
non-zero, tho that wouldnt kill the parens, which i changed to a space
in my fvwmrc.

Re: FVWM: 2.6.3 does not build

[elliot s]

Speaking of 2.6.3, I'd found what I think is a bug ((Icon)TitleFormat
doesnt quite work like IndexedWindowName for one window) and reported
it to fvwm_workers, but i don't see it on that list's archive.  If it
doesnt show up on the archive, does that mean that the msg didnt go
thru?

Re: FVWM: Task Bar Disappearing

[elliot s]

 My FvwmIconMan buttons for iconified windows are always flat, whether
  I set IconButton or not.  My non-iconified window buttons react to the
  settings just fine.
  I'm running 2.7.0.

 If i remove Colorset and IconColorset and instead use Background and
 IconButton colors, that gave me the relief for iconified windows.


False alarm.
Apparently, my IconColorset had a color the same as the relief.

Re: FVWM: Task Bar Disappearing

[elliot s]

Well, i got the FvwmIconMan/FvwmButtons pair looking like my fvwmtaskbar.
Two differences:
fvwmtaskbar had a shared mail checker/date display.
I dont know of an easy way to get both, so now it's just an xclock display.
fvwmtaskbar colorset colors show up lighter than the same colorset in
FvwmIconMan or elsewhere..

Re: FVWM: Task Bar Disappearing

[elliot s]

Perhaps a sample of FvwmButtons/FvwmIconMan fvwmtaskbar replacement
code can be put into the wiki so that everyone currently using
fvwmtaskbar doesnt have to dumpster dive thru the forum.

Re: FVWM: Task Bar Disappearing

[elliot s]

Use FvwmIconMan and FvwmButtons.  I'll be deprecating FvwmTaskBar soon
 enough.  It's dead.


Is there an example somewhere on converting fvwmtaskbar functionality
to FvwmIconMan/FvwmButtons?

Re: FVWM: Desktops versus Pages - how to use?

[Elliot S]

I have mine set up w/ 2 desks of 4 pages each. Only one desk is
visible at a time.
Middle clicking on a  page switches me to that page on the other desk.
I have numbered title bar buttons to move windows to numbered page,
or can move it to same page on other desk.

Re: FVWM: Alarm/calendar applications that work well in fvwm?

[Elliot S]

I searched for iCal with Google and there are indeed two
iCals, one is the well known (and current) Apple iCal and the other is
the one referred to above which has been a bit of an orphan for a
while but does have a few people working on it.


I can't get tcl/tk(/c) ical to compile  run anymore, so ive partially
created a pure tcl that's .calendar/user.tcl compatible. Presently, it
can display most of .calendar but not alter it.