On Friday, March 22, 2002, at 05:55 AM, Tommi Hassinen wrote: > v1.00 : this would be the "ready" program, everything would work > through the GUI, and console would not be needed anymore I think that console output might be good for some uses as an option, but certainly console input shouldn't be needed. I can imagine redirecting some console output to a log file for other uses. > (during 2003 probably). Having worked on a variety of development efforts, I think it's tough to speculate on times. Who knows, maybe it could happen sooner if others pitch in some time and effort? Maybe yes, maybe no. ;-) > Some time ago I also saw a webpage of a graphical CVS program front end, > where the console and the GUI were nicely combined (I don't remember the > program's name anymore). In the program a text widget was used as a > console output window, and a text input widget was used as a console > input > window. Perhaps we could use something similar. Hmm. If you could find it (or a screenshot), that would be a great help. I think I have a rough idea what you mean. > complicated graphical interfaces (for example a command "add a > disulphide > bridge between cys 15 of chain 1 and cys 45 of chain 2" as a text-based > command would be as simple as a dialog-box based system). Yes, some "scripting" would help some and would certainly make "plugins" easier too. I can think of "set torsion between atoms 2 4 5 6 to 175 degrees" or "set coords of atom 1 to (0.0, 1.0, 2.5)" and similar items that would be very useful for me. > In the following days/weeks I try to write it as a table with following > fields: > > - priority (1-5) > - the idea described > - who's working on this, if any > - something else? > > The idea is that the list could be sorted by "priority" anytime and > therefore one could see from the table what is likely to happen soon. Some of these ideas may depend on others, so for "something else," dependencies comes to mind. -Geoff