On Sat, June 30, 2007 1:43 pm, Andrew Lentvorski wrote: > Lan Barnes wrote: >> Come ON! Give me a frackin' break! That's called ... let me see ... oh, >> yeah ... "application programming." > > Congratulations, we agree. > > However, the original point was that "Why do we have so many editing > widgets? Integrating My Favorite Editor into Thunderbird is easy. You > just open a window and drop my editor into it." > > What I have just demonstrated is that it is *not* that easy. > > -a >
It is easy. It's also easy to grab a standard edit widget and use it. No big deal. What is rare is the need for simple edits within an app. Within an app you have constraints, data checking, yadda yadda yadda. But what you're complaining about is the complexity of application programming. The implementation of the editor has little is anything to do with that. When I write a data base front end and have a free form comment field, the code for the edit widget and storage/retrieval (Tcl/Tk) is rarely more than 7 or 8 lines, and it's bulletproof. If I want to use the user's $EDITOR it might add 2 lines (just to check and make sure s/he has one). I call that "integrating the user's preferred editor." The distinction between integrating an editor and adding apication ornmentation is clear and you are smart, so you're simply stubbornly insisting on obviscating it so you can claim to be right :-P -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
