On Fri, June 29, 2007 10:21 pm, Andrew Lentvorski wrote: > Lan Barnes wrote: > >> Huh? "frame .f -container ..." Wow, what a gamut of windowing widgets >> that >> comprises! >> >> Why all the hand wringing? >> >>> Thanks for the concrete demonstration of what makes integrating an >>> editor such a PITA. >>> >> >> Looks pretty simple to me. Four lines. Perhaps your PITA threshold is >> lower than mine. > > I find it hard to believe that y'all are this obtuse, so I'm clearly not > explaining the issue. > > Okay, here's a concrete task. I'm going to pick on Lan because he > actually made the mistake of providing code ... ;) > > So here's the task: > > The goal is an email window. It has a Entry widget which holds the To: > address. It has a container widget which holds the vi instance. > > How do I select the address in the Entry widget and insert it into the > vi instance? > > Actual steps please. > > The key question: How do we identify what the character encoding is for > the Entry widget and for the vi instance and how do we harmonize the two? > > -a > Come ON! Give me a frackin' break! That's called ... let me see ... oh, yeah ... "application programming."
The original challenge posed by (I'm going to pick you because you changed the target) _you_ was to provide an app with the editor of the user's choice. What was being edited and what was going to be done with it is, was, and always will be, a wash no matter how the text is collected. TEXT -> MAIL is the same effort no matter what editor is used. But to help you along even more, Tcl has a rich and mature mail library. So does perl. Betcha Python does too. Why? Because it makes things easier for the application programmers, who often collect text for mail from a variety of widgets and editors. -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
