Easiestquickest method for very simple interfaces 4024

That's not the point. My aim now is to handle my data and not to specialize on computer administration. As I said I'm rather searching a solution for my tasks, but I give this one a try: In my visual approach you open "stuff" and "things" (hotkey, type, click,... whatever you like). You mark all files and add them to a (predefined?) data buffer. All can be done by hotkeys. These are pretty standard tasks. "Junk" goes into buffer 2. In Buffer 3 you type the appropriate Boolean operation on B1.name and B2.name. One key for the buffer number, one for the name entry. The Boolean operation could be displayed as a tree before being evaluated.

I believe the computer system should be brought up to date with current PC speed and visual features. The reactor did not have a single terminal in a dark room with a command line, where you had to type "catdev-temperature". There were flashy LEDs, switches and digital displays for easier handling. Why would they want to? The system was improved. Forget backwards-compatibility. But people imagine files as some sort of object and not a sequence of explorer is intuitive. And of course all data, text or image, keeps its data character in order to be processed. Writing scripts and giving names to all of them would still be an ugly solution for my current tasks. I'd have to think which scripts filter what. There is a reason why people create flowcharts, UML-diagrams (or whatever they're called) and so on. Also programming is very error prone. A decent visual approach could help a lot. I need a proper parameter preview. Otherwise I have to open the file, copy the needed line or even decompose it for further evaluation. It should be like a table of parameters and maybe preview pictures. So in my case I don't have so many. And speed limitation is not a fact I'm considering at the moment. That the thing I'm not sure about. What's the interface that is quickest to program if I have a single window GUI with only a few buttons. However I'd be thankful for nice predefined table objects and methods to display images. That's what I did. It works. Now I want to add features and I notice the hacks should be made more maintainable to easier extension. I also notice that working at an actual research reactor is stressful enough so that I need all my concentration to interpret incoming data. It doesn't have to be too strong. Offering more sophisticated word continuation or automatic suggestion for macros would be a good start for editors. I just wanted an opinion on which of these (or any other) is best. Tcl, PerlTk,...? I'll give it a go and learn.

Anton