1) modular GUI design
2) internationalisation
3) CLI
1) modular GUI design :
=======================
I think that an important requirement is misssing.
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).
2) Internationalization :
=========================
If we want OSCAR to be successfull, internationalization should be a
requirement of the GUI engine. UTF8 & co ...
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".
The generally acceptepted best practice for any server is to install
only the requested services & components. All the server I manage don't have and
don't need X. If I had the choice, the OSCAR head-node would not those
thingy...
I don't think it is a good idea to separate the :
- CLI
- text based install
- graphic install
- web install
This will transform the OSCAR maintainance into a true nightmare unless
the Neil suggestion is followed : lot's of small CLI utilities andi
several GUI build on top of that.
However, the modularity is not respected in this approach and that's why
I really global approach of the problem is necessary with an interface
builder layer "like" metamenu.
Ben
--
Benoit des Ligneris Etudiant au Doctorat -- Ph. D. Student
Web : http://benoit.des.ligneris.net/
Mydynaweb Developpe(u)r: http://mydynaweb.net/
Centre de Calcul Scientifique http://ccs.USherbrooke.ca/
OSCAR Symposium-May 11-14 http://oscar2003.ccs.USherbrooke.ca/
-------------------------------------------------------
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
