Re: Tcl::Tk Compatibility Updates for Perl/Tk

On Tue, May 11, 2010 at 7:23 PM, Jeff Hobbs <[email protected]> wrote:
> On 11/05/2010 3:21 AM, Konovalov, Vadim (Vadim)** CTR ** wrote:
>>>
>>> I haven't heard from you in a while and was wondering were you were at
>>> in reviewing and/or incorporating the changes I made to Tcl::Tk for
>>> perl/tk compatibility?
>
>        ...
>>>
>>> If you don't think the changes fit your planned direction for the
>>> Tcl::Tk package, I was thinking that another option for the changes is
>>> to be released as a separate package (something like a new Tcl::pTk
>>> package )
>>>
>>> What do you think?
>>
>> I really like this solution - because it was my blue dream and real
>> preference to have Tcl::Tk module really small - essentially one single PM
>> file.
>>
>> But your solution has an unfortunate problem, though.
>> Having yet another perl+tk solution will make people confused.
>> They will not know what to select between Tkx, perl/Tk, Tcl::Tk and
>> Tcl::pTk.
>>
>> But if users of this mailing list will see this as no-problem, I will
>> greatly support this, and even will help you with some eventual patches of
>> your new module.
>
> I would like to echo my appreciation for John's efforts.  I for one think
> that Tcl::Tk might be better served to just be "compatible" if possible.  I
> do understand Vadim's point about nice clean modules, but I think this one
> would serve the community best by reducing any possible confusion.
>
> My $.02 ..
>
> Jeff
>

I agree.

Tcl::Tk as-is doesn't have much use to me right now, because I have a
large codebase of perl/tk code that I would like to use, which the
existing Tcl::Tk doesn't work with. (but it does work with my updates
to Tcl::Tk).

The fact the existing Tcl::Tk is relatively small doesn't really
matter to me, because I have much larger set of code that I have to
work with. I don't think I would even notice the difference in
load/run times between a 1-file Tcl::Tk package and a 20-file Tcl::Tk
package.

Just my opinion from the standpoint of a developer with a lot of
existing perl/tk code to support.

-John