Hello, > We have that now. Any package can come up with any configurator panel for > the package, without any changes to the OSCAR GUI. What I don't want is for > a package to be able to dynamically insert buttons/whatever into the main > OSCAR GUI. Packages should not be able to mess up the main OSCAR GUI.
Not really. Some packages needs additional steps, not just a configurator panel. Some packages will have their own logic and offer choices & user input depending on the precedent. I don't say that packages should be able to add buttons & co to a given OSCAR pannel but they should be able to provide their own pannel and their own logic directly from the OSCAR wizard. Packages should be able to do it without affecting a single line of code of the wizard otherwise we will end up with a completely unstable and unmanageable GUI wizard. Modular GUI is only a logical consequence of modular OSCAR. If the GUI is not modular then OSCAR is not modular and we will come back at an early (less advanced IMHO) OSCAR version... 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
