This is an unordered list of things that I'm thinking about doing with MGv.
- I'm considering moving to GNU autoconf (mostly to get libtool
so I can portably make wlib a shared library) but I'll have to
see if I can make autoconf as convenient to use as my GNU makefiles.
- Resizing a zoom window should expand the zoomed area rather than
stretching it; effectively, this would allow you to alter the
zoom reticule after the zoom has popped up.
The GHOSTVIEW window property
(see
The GHOSTVIEW Property) has
four optional values that may be of assistance here.
- Switching to an XmMainWindow widget might be a good idea but
writing my own simpler main window widget would probably be a better
idea.
The only utility of this modification would be proper resize
handling for the menu bar.
In order to get the menu bar to wrap around when the window gets
too thin, you have to set its XmNcolumns resource; however,
you need to be directly involved in the geometry management in
order to determine what value XmNcolumns should have.
Hence, you need to be a manager widget to properly resize a menu bar
without resorting to kludges. This will probably happen when I get
around to adding a toolbar.
- The wlib library needs a simple resource persistence interface.
This should be pretty easy once I have whatever to String
type converters for the various resources. Any hacking towards
this end might also yield a reasonable way to build Options
dialogs for modifying the application resources.
- I like the panning in Acroread (you grab the page and move it
around with the mouse) so I think I'll add it to MGv some time.
- I have had a request for a toolbar so I'll probably add one even
though I personally hate toolbars. When I add a toolbar, I'll
make sure it is fully user configurable.
- The mgvScroll action should have a percentage argument (with
the scrollPercentage resource as a default).