I've seen a few other people posting "WIBNI" stuff, so I thought I'd add
in my $0.02 in case anyone's looking for things to do ... :)
1) Module cleanup. It seems to me that there're at least a few modules
where functionality is overlapping. I appreciate that people have
different priorities, but it'd be really nice for new users if there
was one module for each task... and it would be nice to get one
really excellent module rather than 2 or 3 pretty good ones. The
"Console" variants in the extras directory leap immediately to mind.
1a) As part of #1, get a shared library for fvwm modules. Pack as much
stuff into it as possible--this may mean generalizing some of the
stuff currently available in only one or two modules. Once we have
automake/autoconf support, we can use libtool to make shared
library support almost trivial.
1b) Also as part of #1, it would be nice if more modules allowed
separate config files, rather than requiring things in .fvwm2rc
(like FvwmButtons does, for example). Configs for some modules
(like FvwmForm!) can grow very large. Also, it's nice if you can
change the file, then see the changes without having to restart
fvwm (or using a Console program).
2) New core feature for SmartPlacement: have SmartPlacement try extra
hard to avoid overlapping windows tagged StaysOnTop.
3) FvwmForm -- this is a MOST handy module, but it needs someone to
work on new features.
- Cut and paste !!! (especially paste!)
- Keyboard accelerators
- Dropdown lists
- Some more conditionals for the command invocation; I'd like a
trinary operator. Or, maybe something like the shell variable
queries.
- Nice to have: ability to draw lines across the window; ability
to include pixmaps; etc.
4) FvwmButtons
- Allow "compressed" buttons, where the buttons aren't uniform
width (or height, for vertical bars), but rather just as wide as
they need to be. This is most important for swallowed items.
- A "tool tips" or "balloon help" feature.
- One FvwmButtons app managing multiple button bars (I think
there's one per button bar now, right?) Generally I would like
all "stay alive" modules to manage multiple instances of
themselves where that makes any sense.
Gee, it seems like there were other things, too...
--
-------------------------------------------------------------------------------
Paul D. Smith <psmith_at_baynetworks.com> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions--Bay Networks takes no responsibility for them.
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Mon Jun 01 1998 - 14:14:53 BST