Re: GUI for modules

[Axel B. <Axe...@cs...>]

Some years ago I wrote something that runs a small http server
for the user, to allow the user to update his module environment
using his web browser.
This allows updating of the .cshrc file (and possibly others,
but unfortunately the 2.2b version of modules that we use here
only updates startup files for the 'current' shell that the user
is using.)
For updating a running shell in an open window it also generates
commands that can be copied/pasted to the shell window.

Unfortunately the current implementation is quite targeted
to our local module hierarchy (consisting of 3 levels:
appplication group -- application -- version of application).
In addition, next to each module file we have a file with
additional info (who installed it when, who maintains it,
how much maintance can be expected, etc).
In the past I have started cleanup to get at least
to something that can be distributed and played with,
but, as too often, got distracted by more urgent matters,
and it still is not in a distributable state, I think.

To give some idea, I made some (ugly, but cannot find out how
to do better right now) screendumps that can be viewed at
<URL:http://www.cs.utwente.nl/~belinfan/modgui/>

As far as I get comments, it seems reasonable workable
(it is used by the small group of 10-15 people or so,
I think)

> Is anybody working on a GUI for modules? Here's my wish list:
 
> - present an "ms explorer" view of modulefiles (with expandable
>   version lists), where every name/version is listed only once
>   according to the order of paths in MODULEPATH;

Not expandable, but the bottom-left window contains the current list
of modules loaded via the .cshrc file.
Clicking a categorie/program/version there makes the top-right
window scroll to this module version

> - present all modulefiles/versions at request
all module files available are shown in the top-right window.
the middle-left window shows an overview of the categories in the window,
with command to initadd, initremove, initswitch (update .cshrc file,
and the bottom-left display), and add and remove (display the shell
command to do that in the bottom-right window.
In addition, for each version we can ask for the information file, and
for the module file to be displayed (they appear in the top-right window).

> and provide a window
>   for modifying/reordering of paths in MODULEPATH;

shows up when the 'reorder modules' link is followd in the top-left
window.

> - use highlighting for added/initadded modules;

The top-right window (showing all available modules)
gives implicit feedback about the initadded modules,
by the commands that it allows.

> - present a menu that:
>   1. displays help;
>   2. does "init*";
>   3. starts a terminal emulator and does "add <modulefile> ..."
>      for that particular shell according to selection;

the top-left window containts a command to start a terminal emulator
to test the current .cshrc settings

>   4. does "add <modulefile>; exec <modulefile>" (and/or, ultimately,
>      mangles startup files for common window managers so that
>      appropriate stuff is entered in menu definitions);
>   5. can pop up windows where stdio/stderr is redirected for
>      debugging.


Regards,
Axel.