[Tile-dev] tile vs. tk

[Jeff H. <je...@Ac...>]

As I work with tile, I realize that the need for both Tk
and tile widgets existing in an interface is a necessity,
at least for 8.5 (until the individual management of tile
based widgets becomes better and more established).

So that leads me to the problem of the standard way in
which tile is added as an augmentation:

package require tile
namespace import -force tile::*

Of course you don't need the namespace force in their,
but I think what we really need is an interim step that
does the opposite for all Tk widgets, like:

namespace move $tkWidgetCommands tk::*

There is no such command now, but I think that tile should
be providing it.  Also, I think we should be reconsidering
the 'tile' name *right now*, and I think that ttk is still
useful.  The tile code is already full of TTK_* APIs, for
themed Tk.  I think this separation from old Tk_ tk::* is
actually a good thing, rather than thinking these should
become the tk::* in the future.  We are talking about 1
char, and I don't really think that I'm ready to screw over
every existing Tk app in Tk 9 by making our life hard over
a single extra t or not.

So, comments?

Jeff