Divorcing Command Line and GUI

[Alex Martelli]

"Timothy Grant" <tjg at exceptionalminds.com> wrote in message
news:mailman.984160633.14724.python-list at python.org...
> Hello Everyone.
>
> This is something of a strange question, but please bear with
> me.
>
> I have a series of tools that I have created that work from the
> command line. I have now been tasked with creating GUIs for
> those tools. The problem I'm faced with is that the command
> line tools and the GUI tools will probably be licensed
> differently (e.g, command line will be Open Source, GUI will be
> something undetermined as of yet.) This means that I can't put
> my GUI code in with my CL code.
>
> My first cut at this demarcation sort of worked, but was also
> troublesome. So while I have some new ideas, I'm looking to see
> if anyone else in the python community has ever had to do
> something like this, and if there are any easily maintainable
> solutions to this problem.

Piece of cake -- just make sure your CL tools take a switch
(-u or --unbuffered) to work without any input buffers on
stdin/stdout, and similarly-unbuffered Python GUI front-ends
will be easily able to drive them (after an os.popen2).


Alex