tcltk-perl Mailing List for tcltk (Page 5)
Brought to you by:
hobbs
You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
(174) |
May
(34) |
Jun
(1) |
Jul
|
Aug
(20) |
Sep
(18) |
Oct
(8) |
Nov
(6) |
Dec
(14) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(16) |
Feb
(8) |
Mar
(3) |
Apr
(1) |
May
(9) |
Jun
(1) |
Jul
(4) |
Aug
(7) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(12) |
Dec
|
2010 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2013 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(2) |
Jun
(1) |
Jul
(1) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(1) |
Jul
|
Aug
(1) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Jeff H. <je...@Ac...> - 2005-01-08 22:10:44
|
M.Srinivasa Rao wrote: > Presently I am working on windows OS.I have Perl and Tcl software in my > system. I want invoke the Tcl interpreter from the perl script and execute > the Pkg_mkIndex utility and return to perl script. > I am able to invoke the Tcl interpreter from shell script using the > following lines of statements. > ########################## > #! /usr/tcl/bin/tclsh8.0 > pkg_mkIndex . *.tcl > exit > ######################### > Like this I want to invoke tclsh and wish from the perl script. If you have the Tcl module for Perl working, then you would just instantiate the interpreter, like so: my $interp = new Tcl; and you can call anything in Tcl with the various methods: $interp->call("pkg_mkIndex", ".", "*.tcl"); or $interp->Eval("pkg_mkIndex . *.tcl"); the Tcl pwd should match Perl's. -- Jeff Hobbs, The Tcl Guy http://www.ActiveState.com/, a division of Sophos |
From: Jeff H. <je...@Ac...> - 2005-01-04 18:47:21
|
For those that wanted to test it on Windows, 0.85 is now passing the Windows PPM, as seen at: http://ppm.activestate.com/BuildStatus/5.6-T.html 5.8 will be forthcoming. The unix builds we have to work on because the Tcl-Tk tests require a $DISPLAY to test on. Jeff |
From: Vadim K. <va...@vk...> - 2005-01-04 12:04:01
|
>>This does not happens with Tcl/Tk 8.5, so visually behaviour >>is better. >> >> > >I believe this was also fixed in Tk 8.4.8+, can you try this >with Tk 8.4.9 and see if you have the same problems? > > > indeed, you're right, I tried 8.4.9 and see problem fixed. my previous version appears to be 8.4.6, so imorovements are between these releases >I can't repro, because if I click on the Windows taskbar item, >since it is already active, it minimizes everything (which is >what I would expect). So I'm not able to drag the outer >toplevel without the dropdown behaving "as expected". > > > ... but when you click on icon at taskbar second time, application gets restored, and at that moment it could be dragged. Best regards. Vadim. |
From: Jeff H. <je...@Ac...> - 2005-01-03 19:08:25
|
> > Can you elaborate on what was fixed to improve the combobox in 8.5 > > that isn"t in 8.4? (later 8.4 version perhaps) > > Consider following simpliest script using Combobox: > > package require BWidget > pack [ComboBox .cb -values {one two three}] ... > I noticed few little misbehaviours on Windows system > When user clicks on arrow to performing dropping a listbox > down, first misbehaviour is titlebar of containing toplevel > window redrawn with a color of inactive window. This > misbehaviour in my opinion is irrelevant. Second misbehaviour > is that at some moment window could be dragged but listbox > does not becomes closed. > > see screenshot at www.vkonovalov.ru/tcltk-misc/1st.JPG > > to reproduce: > - click on arrow of ComboBox widget, listbox should appear > - click on a button of our script at Windows taskbar, > toplevel should become active > - after that toplevel could be dragged but listbox not > closed, and it is clickable > > sometimes latest step does not work (toplevel could NOT be > dragged), in this case misbehaviour could be reproduced by > clicking on icon on taskbar once again (so app will be > minimized) and yet once again (and it will be restored) so > toplevel could be dragged afterwards > > I saw this effect on Win2000 and WinXP. > > This does not happens with Tcl/Tk 8.5, so visually behaviour > is better. I believe this was also fixed in Tk 8.4.8+, can you try this with Tk 8.4.9 and see if you have the same problems? I can't repro, because if I click on the Windows taskbar item, since it is already active, it minimizes everything (which is what I would expect). So I'm not able to drag the outer toplevel without the dropdown behaving "as expected". Jeff |
From: Vadim K. <va...@vk...> - 2005-01-02 16:57:33
|
> > I really appreciate all your help, and also I am glad of new > > comings in Tcl/Tk 8.5 (so Combobox behaving better, and many > > other good features), so I"ll certainly will discuss those in > > Perl"s discussion site. > > Can you elaborate on what was fixed to improve the combobox > in 8.5 that isn"t in 8.4? (later 8.4 version perhaps) Consider following simpliest script using Combobox: package require BWidget pack [ComboBox .cb -values {one two three}] ... or using Perl+Tcl::Tk perl -MTcl::Tk=:perlTk -we "tkinit->ComboBox(-values=>[qw{one two three}])->pack;MainLoop" I noticed few little misbehaviours on Windows system When user clicks on arrow to performing dropping a listbox down, first misbehaviour is titlebar of containing toplevel window redrawn with a color of inactive window. This misbehaviour in my opinion is irrelevant. Second misbehaviour is that at some moment window could be dragged but listbox does not becomes closed. see screenshot at www.vkonovalov.ru/tcltk-misc/1st.JPG to reproduce: - click on arrow of ComboBox widget, listbox should appear - click on a button of our script at Windows taskbar, toplevel should become active - after that toplevel could be dragged but listbox not closed, and it is clickable sometimes latest step does not work (toplevel could NOT be dragged), in this case misbehaviour could be reproduced by clicking on icon on taskbar once again (so app will be minimized) and yet once again (and it will be restored) so toplevel could be dragged afterwards I saw this effect on Win2000 and WinXP. This does not happens with Tcl/Tk 8.5, so visually behaviour is better. perlTk does not have good combobox at all, so no good alternate to check on that side. (I tried Tk::JComboBox, Tk::HistEntry, Tk::BrowseEntry, but those have their own limitations and misbehaviours, and most of them look non-natively on Windows) Vadim. |
From: H. W. M. <mi...@lu...> - 2005-01-02 00:14:53
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jan 1, 2005, at 7:00 PM, Jeff Hobbs wrote: > H. Wade Minter wrote: >> On Jan 1, 2005, at 5:44 PM, Jeff Hobbs wrote: >>> H. Wade Minter wrote: >>> >>>> I'm trying to upgrade my Tcl and Tcl::Tk modules on OS X up to the >>>> new 0.85 release. I'm running the TclTkAquaBI package as my base >>>> Tcl/Tk. >>>> I built the Tcl module successfully by running: >>>> perl Makefile.PL - >>>> --tclconfig=/System/Library/Frameworks/Tcl.framework/tclConfig.sh >>>> && make && make test && make install >>>> When I go to build Tcl::Tk 0.85, though, I get: >>> >>> [test failures] >>> >>> Are you using the latest 8.4.9 TclTkAquaBI install? >> I wasn't - I was on TclTkAquaBI 8.4.8.0, but I just uninstalled that >> one, installed 8.4.9.0, rebuilt both modules, and had the exact same >> problem. Tcl-0.85 installs perfectly, Tcl-Tk-0.85 fails all tests. > > OK, I asked because you do need 'package require Tk' to work > in order for the the Tcl::Tk module to work, and that was only > recently corrected on Tcl/Tk Aqua. Can you verify though that > the package require Tk does work from tclsh? Otherwise, I'll > have to query the Mac guys on what might be the problem. I > only tested Win/Lin. Although the tests fails, perhaps the > module still works?? I found the problem. I had built Tcl-0.85 against /System/Library/Frameworks/... when I needed to be using /Library/Frameworks/. Switching that fixes things. - --Wade -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin) iD8DBQFB1zzto4DwsyRGDscRAndrAJ4gWhIZ1koZC7sKQvBC/xCfkLayRgCgs+3m 0812ktkX2/EmPxk2azjEoYk= =Wvfo -----END PGP SIGNATURE----- |
From: Jeff H. <je...@Ac...> - 2005-01-02 00:01:00
|
H. Wade Minter wrote: > On Jan 1, 2005, at 5:44 PM, Jeff Hobbs wrote: > >> H. Wade Minter wrote: >> >>> I'm trying to upgrade my Tcl and Tcl::Tk modules on OS X up to the >>> new 0.85 release. I'm running the TclTkAquaBI package as my base >>> Tcl/Tk. >>> I built the Tcl module successfully by running: >>> perl Makefile.PL - >>> --tclconfig=/System/Library/Frameworks/Tcl.framework/tclConfig.sh && >>> make && make test && make install >>> When I go to build Tcl::Tk 0.85, though, I get: >> >> [test failures] >> >> Are you using the latest 8.4.9 TclTkAquaBI install? > > > I wasn't - I was on TclTkAquaBI 8.4.8.0, but I just uninstalled that > one, installed 8.4.9.0, rebuilt both modules, and had the exact same > problem. Tcl-0.85 installs perfectly, Tcl-Tk-0.85 fails all tests. OK, I asked because you do need 'package require Tk' to work in order for the the Tcl::Tk module to work, and that was only recently corrected on Tcl/Tk Aqua. Can you verify though that the package require Tk does work from tclsh? Otherwise, I'll have to query the Mac guys on what might be the problem. I only tested Win/Lin. Although the tests fails, perhaps the module still works?? Jeff |
From: H. W. M. <mi...@lu...> - 2005-01-01 23:05:26
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jan 1, 2005, at 5:44 PM, Jeff Hobbs wrote: > H. Wade Minter wrote: >> I'm trying to upgrade my Tcl and Tcl::Tk modules on OS X up to the >> new 0.85 release. I'm running the TclTkAquaBI package as my base >> Tcl/Tk. >> I built the Tcl module successfully by running: >> perl Makefile.PL - >> --tclconfig=/System/Library/Frameworks/Tcl.framework/tclConfig.sh && >> make && make test && make install >> When I go to build Tcl::Tk 0.85, though, I get: > [test failures] > > Are you using the latest 8.4.9 TclTkAquaBI install? I wasn't - I was on TclTkAquaBI 8.4.8.0, but I just uninstalled that one, installed 8.4.9.0, rebuilt both modules, and had the exact same problem. Tcl-0.85 installs perfectly, Tcl-Tk-0.85 fails all tests. - --Wade -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFB1yypo4DwsyRGDscRAkk0AKDaJU0Bw5GjMPu4KZyGGo8+WeV+fQCguzEr I4us3xH5RuDuoXf72xLI44k= =TVp2 -----END PGP SIGNATURE----- |
From: Jeff H. <je...@Ac...> - 2005-01-01 22:46:01
|
H. Wade Minter wrote: > I'm trying to upgrade my Tcl and Tcl::Tk modules on OS X up to the new > 0.85 release. I'm running the TclTkAquaBI package as my base Tcl/Tk. > > I built the Tcl module successfully by running: > > perl Makefile.PL - > --tclconfig=/System/Library/Frameworks/Tcl.framework/tclConfig.sh && > make && make test && make install > > When I go to build Tcl::Tk 0.85, though, I get: [test failures] Are you using the latest 8.4.9 TclTkAquaBI install? -- Jeff Hobbs, The Tcl Guy http://www.ActiveState.com/, a division of Sophos |
From: H. W. M. <mi...@lu...> - 2005-01-01 20:12:17
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm trying to upgrade my Tcl and Tcl::Tk modules on OS X up to the new 0.85 release. I'm running the TclTkAquaBI package as my base Tcl/Tk. I built the Tcl module successfully by running: perl Makefile.PL - --tclconfig=/System/Library/Frameworks/Tcl.framework/tclConfig.sh && make && make test && make install When I go to build Tcl::Tk 0.85, though, I get: Kenbridge:~/.cpan/build/Tcl-Tk-0.85 root# perl Makefile.PL Checking if your kit is complete... Looks good Writing Makefile for Tcl::Tk Kenbridge:~/.cpan/build/Tcl-Tk-0.85 root# make cp lib/Tcl/Tk.pm blib/lib/Tcl/Tk.pm cp lib/Tcl/Tk/Widget/Balloon.pm blib/lib/Tcl/Tk/Widget/Balloon.pm Manifying blib/man3/Tcl::Tk.3pm Kenbridge:~/.cpan/build/Tcl-Tk-0.85 root# make test PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/after.........dubious Test returned status 0 (wstat 10, 0xa) DIED. FAILED tests 1-6 Failed 6/6 tests, 0.00% okay t/geomgr........dubious Test returned status 0 (wstat 10, 0xa) DIED. FAILED tests 1-14 Failed 14/14 tests, 0.00% okay ... Is there something special I need to do to get the build working? - --Wade -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin) iD8DBQFB1wQYo4DwsyRGDscRAnvhAKD9UHbg9FXnpvpn2ZDUiGIYfjAi2ACeLLjY AqOC3XTlgMbg/6N8uOk7jvs= =IDCp -----END PGP SIGNATURE----- |
From: Jeff H. <je...@Ac...> - 2004-12-31 19:55:07
|
> So, thank you all for your good addition, I did release to > CPAN, also another incremental version is to be within January. Thanks. > I really appreciate all your help, and also I am glad of new > comings in Tcl/Tk 8.5 (so Combobox behaving better, and many > other good features), so I'll certainly will discuss those in > Perl's discussion site. Can you elaborate on what was fixed to improve the combobox in 8.5 that isn't in 8.4? (later 8.4 version perhaps) > Happy new year to everybody! Happy New Year! Jeff |
From: Konovalov, V. <vko...@sp...> - 2004-12-31 07:25:36
|
> I have made minor changes to the modules and bumped their version > numbers to 0.85. I think they are ready for release, if Vadim > doesn't mind giving them a push. > > For Tcl, it is just making the Makefiled do --usestubs by default, > and a test case fix. > > For Tcl-Tk, it is adding pkg_require to deprecate need_tk, fixing > some tests and making the build a tad more robust when it is a > subdir of the Tcl module. ok, will note to myself how to do and what to explain in future... up to now, I did this incorrectly (for example at http://perlmonks.org/?node_id=416925) > > I have already tagged them in CVS as Tcl-0-85 and TclTk-0-85. If > any other changes are made, please remember to retag (with cvs > tag -F $TAGNAME). > > Hopefully these minor changes will make everything pass for PPM > building here, but it needs to be pushed to CPAN to get the real > full test. I had an idea to make some other patches to go into next release (mostly to make 'tcltkdb' working, and some documentation additions that will explain how to easily extend Tcl::Tk) but I'll postpone those to next release, which is probably will be at the very beginning of 2005. So, thank you all for your good addition, I did release to CPAN, also another incremental version is to be within January. I really appreciate all your help, and also I am glad of new comings in Tcl/Tk 8.5 (so Combobox behaving better, and many other good features), so I'll certainly will discuss those in Perl's discussion site. Happy new year to everybody! Best regards, Vadim. |
From: Jeff H. <je...@Ac...> - 2004-12-31 01:24:53
|
I have made minor changes to the modules and bumped their version numbers to 0.85. I think they are ready for release, if Vadim doesn't mind giving them a push. For Tcl, it is just making the Makefiled do --usestubs by default, and a test case fix. For Tcl-Tk, it is adding pkg_require to deprecate need_tk, fixing some tests and making the build a tad more robust when it is a subdir of the Tcl module. I have already tagged them in CVS as Tcl-0-85 and TclTk-0-85. If any other changes are made, please remember to retag (with cvs tag -F $TAGNAME). Hopefully these minor changes will make everything pass for PPM building here, but it needs to be pushed to CPAN to get the real full test. Jeff |
From: Konovalov, V. <vko...@sp...> - 2004-12-24 07:57:49
|
> I want to make the --usestubs option the default build option. > This will enable improved binary version independence. > > Any objections? No objections. |
From: Jeff H. <je...@Ac...> - 2004-12-24 00:33:30
|
I want to make the --usestubs option the default build option. This will enable improved binary version independence. Any objections? Jeff |
From: Jeff H. <je...@Ac...> - 2004-12-20 19:38:22
|
Vadim Konovalov wrote: > (CC-ed to Tcl::Tk discussion list) > > > >>"real soon now", but lack of Perl mega-widgets is a > > show-stopper, no? > > Another thought as being "show-stopper" - my feeling that lack of = perlTk > mega-widgets is not a show-stopper in Tcl::Tk but rather moving in = slightly > different direction, probably more convenient way from perspective of > creating widgets At the same time, it will be important for many to have the compatibility, and it is possible. This brings up an interesting point regarding the future structure of the Tcl::Tk code. Only the Tcl module has C (XS) code, the rest is all perl-based. The Tcl::Tk code already has multiple interface implementations. At ActiveState we have actually created another called Tcl::yTk, that is an even lower-level / stripped down binding. It would be nice to see each interface become distinct. This would make coding and supporting them easier. That means turning the existing compat stuff for Perl/Tk into a proper Tcl::pTk module. That would alleviate the funny compat stuff from the other code, while freeing up that module to focus on Perl/Tk support issues. > > 2. How does it behave wrt PAR, perl2exe, or PerlApp (ie, bundling > > into a single executable for distribution) ? Obviously, I'd need to > > bundle tcl + tcl/tk stuff into the executable; I'm wondering if > > Tcl::Tk will be able to find the tcl + tcl/tk pieces in that > > environment ? We use Tcl::Tk (and Tcl::yTk) in the ActiveState PDK UIs. Those are wrapped with PerlApp. At this point there is a bit of hand-crafting involved to do that. We are aware that users will want to wrap end apps, but first we need to focus on the actual use (making it available via PPM, foolproof CPAN builds, etc). As Vadim said, you can always move around the DLLs and runtime files with your app (for that most part, that "just works"), but that is understandably not ideal. > > 3. Much of the tcl.tk website seems to be undergoing repair...is > > there an alternate link to enumerate all available widgets ? The Tcl/Tk wiki (http://wiki.tcl.tk/) is a good reference. On the main tcl.tk site there are a lot of links that end up at the currently functionally disabled resource area. The main problem we were having was with URL spamming, so we took that part offline. In fact, looking at some other ref stuff this morning I saw that the Perl/Tk wiki was defaced as well (since corrected). Ah, it would be so much better to live in a world without spammers ... Jeff Hobbs, The Tk Guy http://www.ActiveState.com/, a division of Sophos |
From: Konovalov, V. <vko...@sp...> - 2004-12-20 17:10:07
|
(CC-ed to Tcl::Tk discussion list) > >>"real soon now", but lack of Perl mega-widgets is a > show-stopper, no? Another thought as being "show-stopper" - my feeling that lack of perlTk mega-widgets is not a show-stopper in Tcl::Tk but rather moving in slightly different direction, probably more convenient way from perspective of creating widgets > My reading of Tcl/Tcl::Tk indicates it creates a tcl interpretter. > > 1. Does this interpretter run in the same process as perl, or > a subprocess ? In the same process. Just like ordinary C library call. No additional processes, but you can still create another interpreters from Tcl language (if you wish), but I did not tried this. If thinking about extra overhead with creating additional interpreter, it actually results in smaller memory footprint and faster startup time... > > 2. How does it behave wrt PAR, perl2exe, or PerlApp (ie, bundling > into a single executable for distribution) ? Obviously, I'd need to > bundle tcl + tcl/tk stuff into the executable; I'm wondering if > Tcl::Tk will be able to find the tcl + tcl/tk pieces in that > environment ? I did not tried it from PAR. Because I feel uncomfortable when application's DLL's (speaking of Win32) are unpacked into TEMP dir and executed from there: there could be no space there, there could be race conditions, security risks. I created similar approach of moving around Tcl/Tk application with my Perl-based executables. It actually works to create statically linked Tcl/Tk that linked with Tcl.xs so all Tcl/Tk code could live in one single DLL and all Tcl/Tk scripts libe in one single ZIP file. I am currently in process of finalizing of this approach, which I expect will be robust in a week or so. I can share my own experience on this. So - it is not hard to create movable independent binaries. > > 3. Much of the tcl.tk website seems to be undergoing repair...is > there an alternate link to enumerate all available widgets ? I also noticed this and have no idea why things are behaving this way. Probably you should go to wiki instead: http://mini.net/tcl , there is category widget there. Best regards, Vadim. |
From: Jeff H. <je...@Ac...> - 2004-12-16 23:50:03
|
> I'm trying to get Tcl::Tk up and working in windows on > Activestate Perl 5.8.4 and Activestate Tcl 8.4.9.0.121397. Ah yes ... > First I tried adding through Activestate's PPM. They don't > have Tcl or Tcl::Tk. I am aware of it missing from ActiveState's PPM repo. I also know the fixes required, but the right people are all away on vacation, so I can't get that corrected until January. > I've tried CPAN's auto install: "perl -MCPAN -e shell", but > that errors out because it can't find 'test'. That may be a failing in the dependency specs / checking, as I think that's just used for testing the Tcl module. > harmless)" the following libraries are not found (I've taken a > random sample and confirmed that they aren't on my system). Hmmm, those look like libs that should be somewhere on the system, part of MSVC or something. Jeff Hobbs, The Tcl Guy http://www.ActiveState.com/, a division of Sophos |
From: Nick B. <nb...@od...> - 2004-12-16 22:13:07
|
Hello, I'm trying to get Tcl::Tk up and working in windows on Activestate Perl 5.8.4 and Activestate Tcl 8.4.9.0.121397. First I tried adding through Activestate's PPM. They don't have Tcl or Tcl::Tk. I've tried CPAN's auto install: "perl -MCPAN -e shell", but that errors out because it can't find 'test'. I've never built a module before. However, I downloaded the modules from CPAN and tried perl makefile.pl. It "looks good", but says, "Note: (probably harmless)" the following libraries are not found (I've taken a random sample and confirmed that they aren't on my system). oldnames.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib netapi32.lib uuid.lib wsock32.lib mpr.lib winmm.lib version.lib odbc32.lib odbccp32.lib msvcrt.lib It ends with "Writing Makefile for Tcl". Running make returns this error: make: *** No rule to make target `C:\Perl\lib^', needed by `Makefile'. Stop. I've been working on getting Tcl::Tk going for more than a day now, so any help would be appreciated. Thanks, Nick |
From: Konovalov, V. <vko...@sp...> - 2004-12-08 15:03:59
|
> > use Tcl::Tk qw=:perlTk=; > > $mw=tkinit; > > $mw->Declare('feedback','iwidgets::feedback',-require=>'Iwidgets',- > > prefix=>' > > feedb'); > > $fb=$mw->feedback(-steps=>10000)->pack(-fill=>'x'); > > $fb->step(1),$fb->update for 0..9999; > > MainLoop; > > For someone coming from a Perl/Tk (as opposed to a Tcl/Tk) > background, > how would I find out about these Tcl/Tk widgets and how to use them? The more perlTk syntax supported, the more you can just use perlTk's documentation. For other Tcl/Tk widgets that do not have perlTk counterpart you should use Tcl/Tk documentation that comes with that widget. While reading, following rules should apply: - Tcl interpreter is used to process Tcl/Tk widgets; Similar perlTk concept exists, but very opaque (for me at least) All Tcl::Tk widget commands are translated to Tcl syntax and directed to Tcl interpreter. This is why $interp->Eval("text .t") is same as $mw->Text; except that in second place Tcl::Tk will generate widget's name for you - in Tcl/Tk widget have path, which consist of several names starting with dot separated by dots. mainwindow has name '.' child window have name of parent window appended with another dot appended with this widget's name. example - frame .fr contains button .fr.b on it - when widget is created, a special command is created within Tk - a widget's path. That said, .fr.b is Tk's command Transition is simple. Tcl/Tk => Tcl::Tk --- $button = $interp->widget(".fr.b"); Tcl::Tk => Tcl/Tk --- $path = $button->path; This is why we read in Tcl/Tk about button: The "button" command creates a new Tcl command whose name is pathName. This command may be used to invoke various operations on the widget. It has the following general form: - widget options are same in Tcl::Tk and Tcl/Tk - when you read in Tcl/Tk documentation something like following: pathName method-name optional-parameters (some description) you should understand that widget in question has said method and you could invoke it as $widget->method-name(optional-parameters); $widget is that widget with pathName Sometimes in Tcl/Tk method-name consist of two words (verb1 verb2), in this case it should be invoked as verb1Verb2 And - if you do not succeed with perlTk syntax, you could always use Tcl syntax. Best regards, Vadim. |
From: H. W. M. <mi...@lu...> - 2004-12-08 14:36:01
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Dec 8, 2004, at 7:03 AM, Konovalov, Vadim wrote: >> Following one-liner on Win32 that shows BWidget's ProgressBar: >> perl -MTcl::Tk=:perlTk -we >> "$mw=tkinit;$mw->Declare('ProgressBar','ProgressBar',-require= >>> 'BWidget');$m >> w->ProgressBar(qw/-maximum 1000 -variable/,\$r)->pack for 0..9; >> $r++,$mw->update for 0..1000;MainLoop" > > can't resist to show another way to do progress bar. > > Almost the same one-liner: > perl -MTcl::Tk=:perlTk -we > "$mw=tkinit;$mw->Declare('feedback','iwidgets::feedback',- > require=>'Iwidgets > ',-prefix=>'feedb');$fb=$mw->feedback(-steps=>10000)->pack(- > fill=>'x');$fb-> > step(1),$fb->update for 0..9999;MainLoop" > > but now it uses progress bar from Iwidgets package. > > A version to run from file: > > use Tcl::Tk qw=:perlTk=; > $mw=tkinit; > $mw->Declare('feedback','iwidgets::feedback',-require=>'Iwidgets',- > prefix=>' > feedb'); > $fb=$mw->feedback(-steps=>10000)->pack(-fill=>'x'); > $fb->step(1),$fb->update for 0..9999; > MainLoop; For someone coming from a Perl/Tk (as opposed to a Tcl/Tk) background, how would I find out about these Tcl/Tk widgets and how to use them? - --Wade -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFBtxFIo4DwsyRGDscRAu8IAJ94CRhkRBZnbJiOVMOaNQB5cUVCugCePgjm 3FLnWapsRfUwECm+8tBnP+0= =uZvI -----END PGP SIGNATURE----- |
From: Konovalov, V. <vko...@sp...> - 2004-12-08 12:04:43
|
> Following one-liner on Win32 that shows BWidget's ProgressBar: > perl -MTcl::Tk=:perlTk -we > "$mw=tkinit;$mw->Declare('ProgressBar','ProgressBar',-require= > >'BWidget');$m > w->ProgressBar(qw/-maximum 1000 -variable/,\$r)->pack for 0..9; > $r++,$mw->update for 0..1000;MainLoop" can't resist to show another way to do progress bar. Almost the same one-liner: perl -MTcl::Tk=:perlTk -we "$mw=tkinit;$mw->Declare('feedback','iwidgets::feedback',-require=>'Iwidgets ',-prefix=>'feedb');$fb=$mw->feedback(-steps=>10000)->pack(-fill=>'x');$fb-> step(1),$fb->update for 0..9999;MainLoop" but now it uses progress bar from Iwidgets package. A version to run from file: use Tcl::Tk qw=:perlTk=; $mw=tkinit; $mw->Declare('feedback','iwidgets::feedback',-require=>'Iwidgets',-prefix=>' feedb'); $fb=$mw->feedback(-steps=>10000)->pack(-fill=>'x'); $fb->step(1),$fb->update for 0..9999; MainLoop; |
From: Konovalov, V. <vko...@sp...> - 2004-12-08 09:00:44
|
> > 1) How does Tcl::Tk interact with Perl/Tk submodules. For > example, I > > use Tk::ProgressBar::Mac to generate a progress bar. > However, when I > > try to use it with my mimimal changes, I get an error when > I attempt to > > call the widget. Do I need to remove or rewrite any > non-core widgets > > that my script uses in order to use Tcl::Tk? You can not use pure-perl perlTk widgets. However there exists a way to create pure-perl Tcl::Tk widgets. But this design not decided and it is not documented - so you can't use this either. However I hope to solve this within a month (or may be two), so expect positive answer to your question soon. But usually it is easier to use existing Tcl/Tk widget: Following one-liner on Win32 that shows BWidget's ProgressBar: perl -MTcl::Tk=:perlTk -we "$mw=tkinit;$mw->Declare('ProgressBar','ProgressBar',-require=>'BWidget');$m w->ProgressBar(qw/-maximum 1000 -variable/,\$r)->pack for 0..9; $r++,$mw->update for 0..1000;MainLoop" Note 'Declare' widget method of widget. It creates ProgressBar widget in Tcl::Tk It declares that widget of type 'ProgressBar' (1st arg) should use widget 'ProgressBar' (2nd arg) of Tcl/Tk and it requires 'BWidget' package (Tcl/Tk script will use 'package require BWidget') It provides great flexibility, and general Tcl/Tk widgets availability. Once invoked, you can use ProgressBar anywhere in your program. (it is called 10 times in my example) (note to myself -- should document 'Declare' method clearly (as TODO comment says)) > > > > 2) Does Tcl::Tk support drag and drop? I had to comment out the > > Tk::StartDrag and Tk::DragDrop calls in order for the script to run > > under Tcl::Tk. It was not implemented in Tcl::Tk's, so there is no perlTk compatibility WRT Tk::StartDrag and Tk::DragDrop As I currently understand, perlTk uses Drag-n-drop borrowed from Tix. There exists also drag-n-drop in BWidget Tcl/Tk's package. As using drag-n-drop from Tcl::Tk you can use either Tix one or BWidget's one. Both ways should be easily doable, Usually Tcl/Tk distribution comes with BWidget and without Tix. Please see BWidget's demo from your Tcl/Tk installation to see which drag-n-drop will be available to your Tcl::Tk scripts. > > 3) Are Pixmap window icons supported? they should be... What code is not working? > > I don't mind porting some of my code over to the Tcl::Tk > way of doing > > things, but I'm not fluent in Tcl or the way this module > does things, > > whereas I've been working with Perl/Tk for 3-4 years now. On first > > glance, aside from a few problems, my app runs well by > changing "use > > Tk;" to "use Tcl::Tk qw(:perlTk);", which is both surprising and > > encouraging. Good work to the team for making at least the initial > > stuff so easy! The key point here - anything that does not works with Tcl::Tk but works in perlTk could be easily adopted to Tcl::Tk. But with Tcl::Tk you will get more avilability in general. Also, it is planning to do distributions of Tcl::Tk with Tcl/Tk. Best regards, Vadim. |
From: Jeff H. <je...@Ac...> - 2004-12-08 06:07:16
|
Hi Wade, H. Wade Minter wrote: > Based on this and your post today on comp.lang.perl.tk extolling the > virtues of the Tcl::Tk interface vs. the "Perl/Tk" interface, I've > decided to see what it would be like to convert my fairly complicated > Perl/Tk application (http://www.lunenburg.org/mrvoice/) to the Tcl::Tk > module. > > Surprisingly enough, with the :perlTk interface to Tcl::Tk, I didn't > have to comment out much functionality from my app to get it working on > OS X with Tcl::Tk 0.84. However, I've got a couple of questions. If Cool! > you're the guy to answer them, I'd appreciate them. If not, feel free > to direct me to the right person or mailing list. tcl...@li... is the best list. I've cc'ed, but you should join if you continue developing with it. As to the questions, see the longer post I made to another person in that thread where I reference your questions (anonymously). The key item is that Tcl::Tk is still pre-1.0 for a reason, and that the Perl/Tk compatability is weakest in the submodule area. > 1) How does Tcl::Tk interact with Perl/Tk submodules. For example, I > use Tk::ProgressBar::Mac to generate a progress bar. However, when I > try to use it with my mimimal changes, I get an error when I attempt to > call the widget. Do I need to remove or rewrite any non-core widgets > that my script uses in order to use Tcl::Tk? > > 2) Does Tcl::Tk support drag and drop? I had to comment out the > Tk::StartDrag and Tk::DragDrop calls in order for the script to run > under Tcl::Tk. > > 3) Are Pixmap window icons supported? > > I don't mind porting some of my code over to the Tcl::Tk way of doing > things, but I'm not fluent in Tcl or the way this module does things, > whereas I've been working with Perl/Tk for 3-4 years now. On first > glance, aside from a few problems, my app runs well by changing "use > Tk;" to "use Tcl::Tk qw(:perlTk);", which is both surprising and > encouraging. Good work to the team for making at least the initial > stuff so easy! Learning a little Tcl will help, but it really isn't necessary to make Tcl::Tk work for you - that's the point. You should really be able to work at the Perl level. However, for compatability, leveraging existing Tcl modules may well be to your advantage. -- Jeff Hobbs, The Tk Guy http://www.ActiveState.com/, a division of Sophos |
From: Konovalov, V. <vko...@sp...> - 2004-11-16 06:49:16
|
> > > Did I understood correctly that "sl" in "libtcl8.4.sl" stands for > > > "starpack library"? > > > > No, it stands for "shared library". It is the HP-UX > > equivalent of a .so or .dll. indeed. > > To follow up on this, the code for handling the starpack as > dll has nothing to do with the recent HP-UX support commits > (those are purely for HP-UX). The code has been in the CVS > for a while now. If you compile with -DUSE_TCL_STUBS (which > should probably be the default), then when it loads the Tcl > library, we make 2 extra sym checks for TclKit_AppInit, which > would replace Tcl_Init on the interp, and TclKit_SetKitPath. > These are used to indicate the shared library is the starkit > source, and all is contained within it. Yes, I noticed that some time ago. I understood general idea with stubs, also I noticed TclKit_AppInit. As I understood, all those are in line with general Tcl TEA. I find those changes very useful, but I did not used -DUSE_TCL_STUBS yet. Best regards, Vadim. |