The most useful aspect of the ccp4i GUI is its automatic generation of com files. However, I would prefer the GUI to output a .com file into my working directory (rather than the obscure location they are saved to now) every time I run a program so that I can then tinker with it and add any extra keywords I want to. It would also be nice to see how different options are changing the .com file (something similar to the way dreamweaver shows you the updated html in a split-screen with the WYSIWYG editor).
Something else that might be useful could be log files suggesting extra keywords/parameters in much the same way as mosflm does already. Finally, if a function does not work (such as the shelx conversion in mtz2various mentioned last month or the temperature factor check box I mentioned in Refmac) then these functions should definitely not be included in the GUI. Better a spartan GUI where everything works than a complete GUI with questionable parts. Simon -----Original Message----- From: CCP4 bulletin board [mailto:[EMAIL PROTECTED] On Behalf Of Phil Evans Sent: 10 May 2007 13:58 To: [email protected] Subject: Re: [ccp4bb] CCP4 GUI I always liked Kevin's comments on little-used options in the DM documentation "Don't use these unless you really know what you are doing. In which case you'd better have a better idea of what you are doing than I do." Phil On 10 May 2007, at 13:07, Kevin Cowtan wrote: > Miguel Ortiz Lombardia wrote: >> I was thinking in the "less scary" widgets-based interface for >> not-so-used options. If possible, I think that all options should be >> available to the interface. > > My programs at least have a load of options which I put in for the > purposes of testing out ideas, which didn't work but may be useful > at some point in the future. Generally these options are not error > checked. They should not be made available to the user.
