From: Bruce S. <bw...@ar...> - 2003-06-06 15:55:02
|
Note, it may appear that I'm talking to myself here. But, I'm not crazy, really! ;-) > IMO, we also badly need a way to detect network cards, instead of making > the user input or select a module. I'm fairly stuck there. I'll look into how some other distributions do this, later. I want to get a basic menu system built first. > > Doesn't need to be much and you can "steel" it from "make menuconfig", > > which is stolen from the Linux kernel config. ;-) > > The first problem I noticed is lxdialog doesn't seem to exist on the CD I've been looking a lot at "lxdialog" a lot. Due to lack of documentation that I can find, I've been reverse engineering the menuconfig script, and have even looked at the C code. I think I understand how it works now. > I see Redhat has a package called "dialog" which lxdialog is based on. Then I started comparing the functionality of "lxdialog" and "dialog". For my use on a "setup" program, the standard "dialog" program ( http://hightek.org/dialog/ ) would be much nicer. "dialog" is a more powerful program, and would make the shell script a lot easier and smaller. The largest advantage I noticed is "dialog" can do check-lists and radio-lists with one program call. It lets you [un]select items with the space bar all within a single program execution, and returns all the item(s) selected. You don't have to put it in a shell script loop and redraw the screen every time a new item is [de]selected. Since we need to add either "lxdialog" or "dialog" to the distribution so it exists on the CD for my program, I recommend we add "dialog". Thoughts? Comments? Questions? ... Go ahead and add it? :-) - BS |