3 ms·
I’m not arguing that scripting or batching is not useful - I’m only arguing that that a CLI is usually not a good base to build the GUI on top of. Having a lib
by alkonaut 8y ago
I’m not arguing that scripting or batching is not useful - I’m only arguing that that a CLI is usually not a good base to build the GUI on top of.
Having a libsomeghing and a something-cli and something-gui is a perfectly good solution, but usually not if the GUI calls the CLI instead of the lib.
- ajuc 8y ago> Having a libsomeghing and a something-cli and something-gui is a perfectly good solution That's what he proposes? > The GUI wrapper should be a separable module. If they're plug-replaceable, the application isn't irretrievably wedded to any specific GUI technology... > This means your program should be runnable both with and without the GUI present, and accept input from a mouse or under programmed control. Preferably that means both a shell-level interface for convenience and a C-level interface for efficiency; Perl programmers could elect either method. That way, naive users can use push-button GUIs, blind users can use Braille terminals, and sophisticated users can program solutions to intricate problems. Basically he says we need to use model-view-controller architecture to write desktop applications.