On Sat, Aug 28, 2010 at 2:42 PM, zpcspm <[email protected]> wrote: > I would suggest to use the term "deprecate" instead of "retire" or > "remove". > > This is how I see it. If the next stable version will be the last one > supporting tk - release it, then create a branch right after the > official release and leave it unchanged.
A branch will not be needed. Indeed, the code could stay the same, except for two or three places. Rather, it is the docs that would change: newbies would think that only Qt exists. Existing users would be free to use Tk and Tk plugins. Examples: --gui=qt would be the default, and no tk plugins would be enabled by default. Perhaps all tk plugins would be gathered in a "deprecated" section of leoPlugins.leo. In other words, we could handle the changeover lightly. The big improvement is that newbies would have less to worry about. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
