[tcltk-perl] few thoughts about Tcl-Tk

[Konovalov, V. <vko...@sp...>]

Dear Jeff,

1.
Right now there exist widgets (like Button, Label and so on) that when
created live in their own package, say, Tcl::Tk::Widget::Button
This will help in not interfering methods between widgets. Works better than
I expected. (I thought doing this will be more complicated than it actually
became)

However complicated widgets behave differently, say, "Menu" becomes
Tcl::Tk::Widget and not Tcl::Tk::Widget::Menu.

I am going to fix this, probably before releasing to CPAN.

Do you have additional ideas on this?

2.
It is actually not clear to me why most code in "need_tk" must present
there, and therefore much of TODO there.
I mean why I code like 
  $int->Eval("destroy [tixTree .___ptk_tree]"); #TODO
must be there.
Do you have an idea why calling $int->call("tixTree", ...) is not good
enough to find proper name? Something with TCL autoloading?
(BTW tk_optionMenu behaves same way)

3.
Is it good to create some support "tcl" or "tk" files inside Tcl-Tk just to
ease processing? Create some Tcl/Tk wrappers to move some logic from Tcl::Tk
to nearby files

4.
I think it would be very nice in addition to existing perlTk compatibility
widgets to create a while bunch of new widgets with same logic, and this
will create some more interest of using module.

Best regards,
Vadim.