Re: FVWM Git Stats

2020-02-08 Thread Thomas Funk
Hi Thomas, Very interesting and cool overview of fvwm's life! :-) Thank you for it!! Best, Thomas Am 7. Februar 2020 17:59:07 schrieb Thomas Adam : Hi all, Just for fun, I ran a git analysis tool over the repository (which as you'll remember retains the history from CVS). For those of you

Re: Do we still need color-limit/visual options in fvwm?

2016-05-07 Thread Thomas Funk
On 05/07/2016 12:40 PM, Thomas Adam wrote: Hi all, Just looking through a few things, and I thought I'd ask whether fvwm needs to stlil support color limiting, and color depths for XServers with less than TrueColor? These days, 24-bit seems to be the standard, and indeed, I've never yet come ac

Re: Some advices about the new static website

2016-04-19 Thread Thomas Funk
Hi Jaimos, I've visited the website again and I only can say - WOW! Great work! The Header 'inside' the window looks pretty cool :-) Also your other changes (colors, formatings, ...) One idea came to my mind after clicking Support->FVWM Forums ... Is it possible to show the forums inside the wind

Re: Some advices about the new static website

2016-04-08 Thread Thomas Funk
On 04/09/2016 01:31 AM, Dan Espen wrote: We don't have stable and unstable anymore so references to stable and unstable should be removed. Yes you're right and I know this but since the update to static these html docs with linked keywords are available from unstable only [1]. Therefore I said

Re: Some advices about the new static website

2016-04-08 Thread Thomas Funk
On 04/09/2016 12:53 AM, Jaimos Skriletz wrote: ​I believe I know which ones you were talking about.​ ​Was this the alphabetical ​list of terms that linked to their location inside the man pages. It was a nice set of links as it made looking for some things easier. Yes and the links inside fvwm

Re: Some advices about the new static website

2016-04-08 Thread Thomas Funk
On 04/08/2016 11:41 PM, Thomas Adam wrote: Maybe, but again, there'll only ever be one set of man pages to reflect when releases happen. Since I've put in place a means of generating them from markdown (and have yet to receive offers on help with that), I'll see what happens when I have time to

Fwd: Re: Some advices about the new static website

2016-04-08 Thread Thomas Funk
On 04/08/2016 10:47 PM, Jaimos Skriletz wrote: On Fri, Apr 8, 2016 at 1:44 PM, Thomas Funk mailto:t.f...@web.de>>wrote: ​The "logo" is now the menu entry, so instead of just saying "FVWM" I put the logo in its place. The logo except for looks works just as any other

Re: Some advices about the new static website

2016-04-08 Thread Thomas Funk
On 04/08/2016 11:08 PM, Thomas Adam wrote: On Fri, Apr 08, 2016 at 09:44:48PM +0200, Thomas Funk wrote: What about the perlib pages and the ... uhm ... 'unstable' documentation pages (http://fvwm.org/doc/unstable/index.html)? Will they appear again in the future? perllib maybe

Some advices about the new static website

2016-04-08 Thread Thomas Funk
Hi Jaimos, until your last commit I took a look over the new static pages on fvwm.org and want to tell you what I've noticed: Cool feature with the window buttons (maximize, shade/unshade) and the logo behind B) :) But the small logo (left upper corner) overlaps the main menu 'FVWM' :( Used bro

Re: Thoughts about DEVELOPERS.md WAS: [travis-ci - fvwm.git master branch is "protected"]

2016-03-25 Thread Thomas Funk
"Thomas Adam" wrote: > On Fri, Mar 25, 2016 at 12:25:09PM +0100, Thomas Funk wrote: > > I think we should. It's better to have such in the documentation so no > > questions appears anymore ;) > > > > I can add it to the document, no prob. > > I

Re: Thoughts about DEVELOPERS.md WAS: [travis-ci - fvwm.git master branch is "protected"]

2016-03-25 Thread Thomas Funk
"Thomas Adam" wrote: > On Fri, Mar 25, 2016 at 03:30:03AM +0100, Thomas Funk wrote: > > One point: > > Should we use for development branches a special nomination like > > feature_xy, fix_abc? > > Or only a README which describes the feature/fix? > >

Thoughts about DEVELOPERS.md WAS: [travis-ci - fvwm.git master branch is "protected"]

2016-03-24 Thread Thomas Funk
"Thomas Adam" wrote: > I was thinking along the lines of this diff: > > https://github.com/fvwmorg/fvwm/commit/f81b2f4d7412813f12b235d8f1914409da0bbae9.patch > > Which you can view rendered here: > > https://github.com/fvwmorg/fvwm/blob/ta/git-docs/docs/DEVELOPERS.md > > What do others think?

Re: First try of fvwm-menu-desktop which creates a "full" menu

2012-07-25 Thread Thomas Funk
Thomas Adam wrote: > On 25 July 2012 18:38, Thomas Funk wrote: >>> Dan Espen wrote: >>> Thomas Adam made some comments about using FvwmPerl. Is that resolved? > No -- and as such, until it starts to use perllib and/or FvwmPerl, > it's not ready. There is *no*

Re: First try of fvwm-menu-desktop which creates a "full" menu

2012-07-23 Thread Thomas Funk
2012/7/23 Thomas Funk : > 2012/7/23 Thomas Adam : >> Don't destroy the same menu you're about to (re)create. > But if I don't destroy it it will be added again and again to > the root menu every time I pop it up ... I've tested it on my VM and you're right!

Re: First try of fvwm-menu-desktop which creates a "full" menu

2012-07-23 Thread Thomas Funk
2012/7/23 Thomas Adam : > Don't destroy the same menu you're about to (re)create. But if I don't destroy it it will be added again and again to the root menu every time I pop it up ...

Re: First try of fvwm-menu-desktop which creates a "full" menu

2012-07-20 Thread Thomas Funk
ule FvwmPerl -l fvwm-menu-desktop-gui.fpl to Module FvwmPerl -l fvwm-menu-desktop-config.fpl Thanks. Thomas # This script generates a FvwmForm similar to the FvwmForm-Desktop by # Dan Espen but insert the found xdg menus dynamically into the Form # before processed. # Author: Thomas Funk # Versi

Re: First try of fvwm-menu-desktop which creates a "full" menu

2012-07-19 Thread Thomas Funk
Thomas Adam wrote: > On 19 July 2012 22:11, Dan Espen wrote: >> I'm guessing the other fvwm developers are okay with going to asciidoc? > No. I have an attempt at this, but it's not finished. We either use > groff or nothing, and I don't mean groff backported from some > conversion tool. If y

Re: First try of fvwm-menu-desktop which creates a "full" menu

2012-07-16 Thread Thomas Funk
2012/7/16 Thomas Adam wrote: > Isn't this in the XDG spec as to which menus appear where, in > categories? I'm sure it is. That's right. The process (the python-xdg lib) which generates the menus follow this. But fvwm-menu-desktop only calls the methods for each menu found in the system. The stru

Re: Reworked fvwm-menu-desktop

2011-11-01 Thread Thomas Funk
-Ursprüngliche Nachricht- Von: "Thomas Adam" Gesendet: 01.11.2011 13:12:56 >Dan didn't construct that structure, that's how it was originally based on >parsing the XML files for the XDG menu definitions, and it's always been the >structured formed from the XDG data which I've had an issue

Re: Reworked fvwm-menu-desktop

2011-11-01 Thread Thomas Funk
Hi Thomas, -Ursprüngliche Nachricht- Von: "Thomas Adam" Gesendet: 31.10.2011 00:39:58 >Hi, > >[ I have no time at all to really give this the attention it deserves, so >I'm going to have to be brief and merely point you in the right directions. >I will though expect this to go through sev

Re: Reworked fvwm-menu-desktop

2011-10-30 Thread Thomas Funk
>-Ursprüngliche Nachricht- >Von: "Thomas Adam" >Gesendet: 20.10.2011 15:00:58 >An: "Thomas Funk" >Betreff: Re: Reworked fvwm-menu-desktop > >>Some very quick observations... [...] >>Can you describe the internal data overall, and now i

Re: Reworked fvwm-menu-desktop

2011-10-20 Thread Thomas Funk
-Ursprüngliche Nachricht- Von: "Thomas Adam" Gesendet: 20.10.2011 15:00:58 An: "Thomas Funk" Betreff: Re: Reworked fvwm-menu-desktop >Some very quick observations... >+my $xdg_data_home = $ENV{XDG_DATA_HOME} || "$ENV{HOME}/.local/share"; >+my

Re: Reworked fvwm-menu-desktop

2011-10-20 Thread Thomas Funk
>On Thu, Oct 20, 2011 at 12:12:43PM +0200, Thomas Adam wrote: >Thanks, but I'd like to see a unified diff, not an entire file. Uuups, sorry :S Attached. -- Life is like a box of chocolates - never know what you're gonna get. ___ SMS schrei