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? I used it in my config, but it lacks in some
> places. I think, it's a nice tool to create GUI based parts.
Extend how? As far as I see it, we need one or the other in terms of
FvwmForm or FvwmScript. Currently they both do subtle things when comparinf
one to the other. But if a project was born to somehow unify them (and to
keep the name FvwmForm) I would not object.
> It could replace FvwmGtk which is a little bit outdated (as I know
> it supports only Gtk1. There was an attempt to port it to Gtk2 but
> Gtk3 is the future...) in some ways.
The comparison here ends, as far as I am concerned. No further mention of
GTK is needed.
> - add support for Wayland ... ok, probably too much for a GSoc
> project ... but as an idea?
Considering Wayland is as experimental as XCB, consider this an outright
"No".
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
