At 10:47 AM 3/6/2003 -0500, Benoit des Ligneris wrote:
We are designing a very modular OSCAR however, the GUI is monolithic. This can't fit together : the modular design will be "destructed" by the monolithic GUI design. We are confronted with this problem with, for instance, the thin-OSCAR project. How can we add options to the existing GUI ? To any monolithic GUI ? How can we integrate with the current stuff ? Should any package author have access to the OSCAR GUI and be able to "patch" it in order to fit his needs ? As a consequence, I'm convinced that we need a kind of general GUI framework for OSCAR. Rebuilding the actual monolithic GUI will not provide this functionality. The modular GUI design is a consequence of the modular OSCAR design and we must ensure that we do not break this modularity by writing a GUI that has to be modified each time someone add a functionality to OSCAR (which is the actual case and will be the case of a "simple" rewrite of the GUI).
I also disagree with this next section. A well crafted GUI will always be easier to use for both large and small clusters. I would think that the limitiations of a CLUI would make scaling harder.
3) CLI & Text based install: ============================
This is, I think, a very important point. The point & click approach is not scalable. We made some progress with the automatic MAC collection but that does not cover everything especially if we want to provide a true "cluster framework".
-------------------------------------------------------
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
