What are you hoping to see as a "minimum"? What comes across as "excessive" for you? GUI's in general, and script-based GUI's especially (as opposed to hand-crafted compiled ones), tend to chew up a lot of memory beyond what you might think is reasonable -- and there's just no getting around that. It's the price you pay for the conveniences of rapid code development and highly adaptable interface designs.
Since most machines in operation today have RAM in the hundreds (or at least several dozens) of MB, along with more hundreds (or a few GB) in virtual memory, keeping a GUI's memory footprint slim is not something we need to worry about. Making sure it's as fast as possible is much more important (you can't make people wait when it comes to responding to clicks and drags with the mouse).
If the application involves dealing with huge amounts of data (e.g. hundreds of MB of images or whatever), in addition to running the GUI, it's the data loading that you need to be careful and skimpy about -- and note that the loading and writing of a large data set is usually the biggest component of "unacceptable delays" in GUI response.
In reply to Re: talking about memory...
by graff
in thread talking about memory...
by primus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |