Easiestquickest method for very simple interfaces 4025

On Tue, 12 Jul 2005 18:00:26 +0200, Anton Suchaneck staggered into the Black Sun and said:

Whatever. You will probably find out what I mean later.0

Hmm, maybe I should've said "in a GUI that exists right now".

This is all pretty doable.

What, specifically, implements the things you described? You've come up short on specifics in almost every message you've posted--this is something you need to work on. I don't know why you're dragging trees into this, either.

I picked the example that I described because it was something that I could figure out how to do from the command line and *couldn't* figure out how to do from any currently-existing GUI. It's possible that no good GUI method exists right now.

That depends on the file. All files have a definite beginning and a definite ending, and between those points, there are bytes. The standard C library's functions are sort of based on that buttumption. "Forks" and "alternate file streams" are system-specific, and not to be relied upon--there's a reason why most Windows programs don't use Stuffit or Binhex format on the Net. It is often *very* useful to be able to dump those raw bytes out with cat or od or vim or whatever.

Heh. Programming is error-prone no matter what you do. Some UML monkeys got loose in some code that my co-workers had to deal with, and they had a *very* hard time dealing with the resulting mess. Flowcharts in their stereotypical form got shot to poo by the advent of event-driven programming (which almost all GUI programs use in some way.)

Pick the language you know best. Pick any widget set. Personally, I'd use Gtk2::Perl for this, but that's just because I like Perl and I have some experience with its Gtk2 bindings.

This is where you have to read the documentation for the widget set you decide on. Every set has functions for loading images and displaying them. I don't know what exactly you want your "table objects" to do, but Gtk2::SimpleList can be used to construct multi-columned lists that contain text, icons, checkboxes, and all kinds of things. Other widget sets may make this task harder or easier; it all depends on what you want.

This is totally orthogonal to the main question you asked, but I think it's got limited utility right now. "Computers are fast, accurate, and stupid; humans are slow, inaccurate, and brilliant--together, they are unbeatable." In your programs, make the computer do the boring, repebreastive stuff, and let the human make the decisions that require intelligence.

Look upthread; another poster said that Tcl was a total PITA if you had to write more than 1 screenful of it. I mentioned upthread that Tk widgets are ugly--though I don't know for sure if they're easier or harder to develop with than Gtk2 widgets. It *is* possible to do almost anything with Gtk2 or Qt widgets, which may not be the case for other widget sets. You should try a couple of them in whichever language you prefer, just to see how you like them.

Good luck, then. I find that if I build a complex GUI, it makes perfect sense to me, but confuses other people. If I build a simple GUI, everybody understands it. Whatever you end up doing will have to be driven by whatever your users want. HTH,

0 Experience keeps a costly school, but there are those who will learn in no other.

-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong ----------------------------- This space sort of for rent.