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. This way people in need could still use that branch in its current state (after all, a lot of effort was put into tk, no need to forget it completely). An exact branch copy will become the current trunk instead and will have everything tk related removed from it and eventually the leo core simplified if the removal of tk would make that possible. It's good Edward brought this issue up, because we had it coming anyway. Even if qt GUI was strongly advocated, it was never done at the expense of hurting the tk GUI, so the fact that the qt GUI is used almost exclusively (at least judging by the content of this group) is something natural. Putting tk aside in a reasonable way makes sense, this will spare both developers and bug reporters from thinking about compatibility with tk when implementing new features / writing GUI related bug reports. -- 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.
