luci@esat.kuleuven.ac.be (03/16/90)
For our research, we use an in-house developed library of image processing routines. We want to group a large set of those routines in a menu driven system. We would appreciate receiving information on ways that you might have considered for building such a system. We are also interested in receiving information on commercially available (or public domain) systems. The following considerations apply to our situation : - any researcher should be able to incorporate his own routines in the menu system. This must be possible without changing the menu program itself. - It must be possible to use the concept on UNIX and VMS machines (especially VAX, DECstations and SUNs). - Speed is not of uttermost importance, adaptibility and ease of maintenance is. - This system is not intended to replace our traditional programming environment ; it should complement it. Stefaan Luckermans K.U. Leuven Dept. Elect. Engineering ESAT / MI2 Kard. Mercierlaan 94 3030 HEVERLEE Belgium Tel. 32 - 16 - 220931 (ext. 1084) luci@esat.kuleuven.ac.be
hschweitzer@hpbbi4.HP.COM (#Heinz Schweitzer) (03/19/90)
Take a look at the emacs-info-mode. With this you can set up nodes of information about your routiens and menues to select them. Crossreferences are also possible. All this is done in a plain ASCII file, and is very easy to do. Heinz Schweitzer Hewlett-Packard Boeblingen West Germany
xrtnt@amarna.gsfc.nasa.gov (Nigel Tzeng) (03/20/90)
In article <2696.2600b400@esat.kuleuven.ac.be>, luci@esat.kuleuven.ac.be writes... ^For our research, we use an in-house developed library of image processing ^routines. We want to group a large set of those routines in a menu driven ^system. ^ ^We would appreciate receiving information on ways that you might have ^considered for building such a system. We are also interested in receiving ^information on commercially available (or public domain) systems. ^ ^The following considerations apply to our situation : ^ ^- any researcher should be able to incorporate his own routines in the ^ menu system. This must be possible without changing the menu program ^ itself. ^ ^- It must be possible to use the concept on UNIX and VMS machines ^ (especially VAX, DECstations and SUNs). ^ ^- Speed is not of uttermost importance, adaptibility and ease of ^ maintenance is. ^ ^- This system is not intended to replace our traditional programming ^ environment ; it should complement it. ^ ^ ^Stefaan Luckermans ^K.U. Leuven ^Dept. Elect. Engineering ^ESAT / MI2 ^Kard. Mercierlaan 94 ^3030 HEVERLEE ^Belgium ^Tel. 32 - 16 - 220931 (ext. 1084) ^ ^luci@esat.kuleuven.ac.be Sorry for wasting bandwith but my mail bounced several times... Anyway, I developed a menu system that uses VMS directory structures and DCL command procedures as the mechanism for menus. Basically each directory is treated by the menu program as a menu screen (and displays it as such) and each sub-directory treated as a sub-menu. These menus are populated by DCL command procedures that are chosen by menu selection. This makes menu changes trivial...to get a new menu screen simply add a directory to your menu tree and place command procedures in it. These command procedures do exactly what you are looking for...some sort of initialization and then image activation. If you would like the source please mail me and I will attempt to get permission to release it. The program was written in VAX FORTRAN and calls a lot of VMS specific routines (Screen Manager for instance) and is running on a VMS 4.7 machine. Otherwise I would be happy to answer any questions...assuming my mailer can find you ;-) NT -------------------------------------------------------------------------------- A| Nigel Tzeng xrtnt@csdr.gsfc.nasa.gov // m| STX Inc. xrtnt@csdr.span.nasa.gov // i| \\ // g| Standard Disclaimer Applies: The opinions expressed are my own. \X/ a| | "Hmmmm." --------------------------------------------------------------------------------