I completely agree, all actions done installing a cluster should funnel through an API that consists of command line programs. The GUI or CLUI or DRUI (dumb readline user interface 8-) should just interact with the user, and call various API defined programs to actually do the work.

At 05:26 PM 3/6/2003 -0500, Michael Chase-Salerno wrote:
On Thu, 2003-03-06 at 16:27, Neil Gorsuch wrote:

I won't argue that a GUI is probably more scalable for many operations,
but the important thing to get across is that it isn't necessarily OUR
GUI. The main function of the CLUI in my mind is to provide a documented
interface for solution builders to wrap their OSCAR based solutions
around. We will lose the interest of some of these groups if we force
them to use our own GUI.

I should also note that this interface doesn't necessarily have to be a
CLUI, it could be a Perl (or whatever) API. The important thing is that
it is documented and supported. A CLUI is just a way to kill 2 birds
with 1 Vulcan Anti-Aircraft Cannon.



-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com
_______________________________________________
Oscar-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to