2012/2/24 Thomas Adam tho...@fvwm.org:
God no. FVWM is not elitist. People will either use it, or not. People
can have ideas, and do. People will have opinions and share them. Or not.
But if/when they do, we'll discuss them, and sometimes good things come of
them.
This isn't endemic to
On Sat, Feb 25, 2012 at 08:47:12AM -0500, MK wrote:
On Sat, 25 Feb 2012 11:16:58 +
Thomas Adam tho...@fvwm.org wrote:
But until we decide to do it that way, it's a little moot, and it
would require some thought and design.
Great for a project for GSoC I'd say, because thankfully
On Thu, Feb 16, 2012 at 11:06:46AM +, Thomas Adam wrote:
All,
Whilst I appreciate that organisations need not worry about this until the
end of February, I'll be moving house then so I need to start thinking about
this now, rather than later.
And to make a start on this, I've created
On Thu, Feb 23, 2012 at 03:58:13PM -0700, msib...@crosswire.com wrote:
SNIP
[I really don't like biting for what is an obvious flamewar, but sometimes
there's useful bits of fallacy which need busting through, so I'll be
picking those up and side-stepping the bait.]
FVWM is not more portable
Here are two thoughts on relatively self-contained potential FVWM GSoC
projects:
* a module that is the inverse of FvwmCommand; call it FvwmQuery.
Where FvwmCommand allows shell scripts to send commands to FVWM,
FvwmQuery would allow them to get information from it.
The FVWM module
A scratch rewrite in C++, using WxWidgets and embedding the
configuration elements in sqlite, killing configuration files for good
and ever. There is a point at which you are doing yourself a favor by
shooting the horse instead of feeding it.
Not trying to piss anyone off. IMHO, I'm just
Am Donnerstag, 23. Februar 2012 schrieb msib...@crosswire.com:
A scratch rewrite in C++, using WxWidgets and embedding the
configuration elements in sqlite, killing configuration files for good
and ever. There is a point at which you are doing yourself a favor by
shooting the horse instead of
Original Message
Subject: Re: FVWM: GSoC 2012: Project ideas
From: Jaimos Skriletz jai...@diamond.boisestate.edu
Date: Thu, February 23, 2012 4:32 pm
To: fvwm@fvwm.org
On Thu, Feb 23, 2012 at 01:34:38PM -0700, msib...@crosswire.com wrote:
Not trying to piss anyone off. IMHO
On Fri, Feb 17, 2012 at 10:33:51AM -0500, MK wrote:
On Fri, 17 Feb 2012 09:45:07 +
Thomas Adam tho...@fvwm.org wrote:
No more so than Name, or Resource would be, yes.
Those are passed thru from xlib, correct? I did not realize fvwm used
all that, I've only ever just used the name, but
On Fri, Feb 17, 2012 at 08:38:06PM +0100, Thomas Funk wrote:
Thomas Adam tho...@fvwm.org wrote:
Comments welcome, or even ideas.
What about
- RANDR support? Switching resolutions without restart Fvwm would be nice.
This one is fine. I've already a head-start in this.
- extend FvwmForm?
On Fri, Feb 17, 2012 at 08:06:46PM +, Thomas Adam wrote:
On Fri, Feb 17, 2012 at 08:38:06PM +0100, Thomas Funk wrote:
Thomas Adam tho...@fvwm.org wrote:
Comments welcome, or even ideas.
Another suggestion for possible projects (seems this list is getting big so any
presepctive
On Fri, Feb 17, 2012 at 01:44:12PM -0700, Jaimos Skriletz wrote:
1) Modify/extend the current menu system to offer more configurability,
the main thing I am looking for here is say allow for multiple mouse
bindings per menu entry (a right click and left click could do different
things). I
On Fri, Feb 17, 2012 at 02:10:54PM -0700, Jaimos Skriletz wrote:
2) Rewrite the menu syntax and redsign the object, there was some talk
about this on the mailing list years ago now and some good ideas for
And the link to that thread is?
Thomas Adam tho...@fvwm.org writes:
On Fri, Feb 17, 2012 at 02:10:54PM -0700, Jaimos Skriletz wrote:
2) Rewrite the menu syntax and redsign the object, there was some talk
about this on the mailing list years ago now and some good ideas for
And the link to that thread is?
Thomas Adam tho...@fvwm.org writes:
On Fri, Feb 17, 2012 at 05:49:00PM -0500, Dan Espen wrote:
Thomas Adam tho...@fvwm.org writes:
On Fri, Feb 17, 2012 at 02:10:54PM -0700, Jaimos Skriletz wrote:
2) Rewrite the menu syntax and redsign the object, there was some talk
about this on
Thomas Adam tho...@fvwm.org writes:
All,
Whilst I appreciate that organisations need not worry about this until the
end of February, I'll be moving house then so I need to start thinking about
this now, rather than later.
Now that 2.6.0 is out, I'm proposing the following project (some of
On Thu, Feb 16, 2012 at 09:57:28AM -0500, Dan Espen wrote:
Thomas Adam tho...@fvwm.org writes:
All,
Whilst I appreciate that organisations need not worry about this until the
end of February, I'll be moving house then so I need to start thinking about
this now, rather than later.
Thomas Adam tho...@fvwm.org writes:
On Thu, Feb 16, 2012 at 09:57:28AM -0500, Dan Espen wrote:
I'd like to see the initial appearance issue get some attention.
I'm working close to that area:
Right now, I'm trying to understand xdg menus.
We make an entry in the FvwmMenu marked:
D:
On Thu, 16 Feb 2012 11:06:46 +
Thomas Adam tho...@fvwm.org wrote:
Now that 2.6.0 is out, I'm proposing the following project (some of
which are a continuation from previous GSoC proposals) -- none of
which are listed in any order.
* Style clean-up (Difficulty: Easy):
This would
19 matches
Mail list logo
