You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
|
Feb
(7) |
Mar
(5) |
Apr
(4) |
May
(15) |
Jun
(10) |
Jul
(4) |
Aug
(12) |
Sep
(39) |
Oct
(22) |
Nov
(46) |
Dec
(65) |
2002 |
Jan
(19) |
Feb
(27) |
Mar
(50) |
Apr
(73) |
May
(85) |
Jun
(52) |
Jul
(49) |
Aug
(95) |
Sep
(152) |
Oct
(81) |
Nov
(42) |
Dec
(62) |
2003 |
Jan
(45) |
Feb
(47) |
Mar
(101) |
Apr
(110) |
May
(53) |
Jun
(72) |
Jul
(125) |
Aug
(77) |
Sep
(87) |
Oct
(69) |
Nov
(55) |
Dec
(71) |
2004 |
Jan
(127) |
Feb
(68) |
Mar
(93) |
Apr
(102) |
May
(64) |
Jun
(92) |
Jul
(40) |
Aug
(113) |
Sep
(44) |
Oct
(61) |
Nov
(44) |
Dec
(100) |
2005 |
Jan
(57) |
Feb
(51) |
Mar
(101) |
Apr
(73) |
May
(45) |
Jun
(97) |
Jul
(92) |
Aug
(94) |
Sep
(46) |
Oct
(83) |
Nov
(82) |
Dec
(68) |
2006 |
Jan
(92) |
Feb
(116) |
Mar
(84) |
Apr
(66) |
May
(40) |
Jun
(57) |
Jul
(89) |
Aug
(82) |
Sep
(58) |
Oct
(94) |
Nov
(104) |
Dec
(70) |
2007 |
Jan
(86) |
Feb
(108) |
Mar
(193) |
Apr
(84) |
May
(71) |
Jun
(54) |
Jul
(17) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: D.J.Moon <lm...@es...> - 2001-06-07 12:26:06
|
Okay, it compiles now, and the printing functions work now. There appear to be some issues with the actual printing implementation, but it appears to be at the WxWindows level since the WxWindows printing samples behave the same way. Specifically, the preview window comes up with a default zoom of 70%, which means the page is extremely huge.. you have to set the zoom down to 10% to be able to display the page on the screen (at 1280x1024 resolution). There is also a problem with the bottom margin being different between the preview and the printout (so page content breaks in different places for each). Also, with HTML printing, the page numbering on the preview frame's interface always displays a total page count of 999. However, since these behaviors also happen in the WxWindows samples, it is most likely an issue with the WxWindows version we have. We're going to try using 2.2.7, and see how that goes. d. -----Original Message----- From: wxp...@li... [mailto:wxp...@li...]On Behalf Of Mattia Barbon Sent: Wednesday, June 06, 2001 5:02 PM To: wxp...@li... Subject: Re: [wxperl-users] Wx::HtmlEasyPrinting > XS/Locale.xs: In function `void XS_Wx__Locale_AddLanguage(PerlInterpreter *, > CV*)': > XS/Locale.xs:107: no method `wxLocale::AddLanguage' > dmake.exe: Error code 1, while making 'Wx.o' > > Win2000, mingw, WxWindows 2.2.6, wxPerl from cvs around 5/21/2001 (this is > the last time we grabbed from cvs that worked) Fixed now, all should be fine... BTW, printing framework *SHOULD* be functional ( I did some quick tests today ) Regards Mattia _______________________________________________ wxperl-users mailing list wxp...@li... http://lists.sourceforge.net/lists/listinfo/wxperl-users |
From: Mattia B. <mb...@ds...> - 2001-06-06 21:02:09
|
> XS/Locale.xs: In function `void XS_Wx__Locale_AddLanguage(PerlInterpreter *, > CV*)': > XS/Locale.xs:107: no method `wxLocale::AddLanguage' > dmake.exe: Error code 1, while making 'Wx.o' > > Win2000, mingw, WxWindows 2.2.6, wxPerl from cvs around 5/21/2001 (this is > the last time we grabbed from cvs that worked) Fixed now, all should be fine... BTW, printing framework *SHOULD* be functional ( I did some quick tests today ) Regards Mattia |
From: Mattia B. <mb...@ds...> - 2001-06-06 20:54:14
|
> We were trying to get the Wx::HtmlEasyPrinting object to work, and ran into > the following problem: > > When we try to create a printing object: > > my $print = new Wx::HtmlEasyPrinting(); Yes, I fixed it some time ago see below, but as an ugly and horryble workaround: bless $print, "Wx::HtmlEasyPrinting"; # should be OK > then the $print object is of class Wx::Object, not Wx::HtmlEasyPrinting, > which causes it to not work for trying to call any of the methods of > Wx::HtmlEasyPrinting. > > Tried recompiling wxPerl from a fresh copy from cvs downloaded today > (6/6/2001), but the current copy does not compile (gives the following > error: > > XS/Locale.xs: In function `void XS_Wx__Locale_AddLanguage(PerlInterpreter *, > CV*)': > XS/Locale.xs:107: no method `wxLocale::AddLanguage' > dmake.exe: Error code 1, while making 'Wx.o' Oops, this is a wxWin 2.3 method... forgot to add guards around it... fixed now; it was some time I didn't check 2.2 compilation... checking now, sorry Mattia |
From: D.J.Moon <lm...@es...> - 2001-06-06 19:27:09
|
We were trying to get the Wx::HtmlEasyPrinting object to work, and ran into the following problem: When we try to create a printing object: my $print = new Wx::HtmlEasyPrinting(); then the $print object is of class Wx::Object, not Wx::HtmlEasyPrinting, which causes it to not work for trying to call any of the methods of Wx::HtmlEasyPrinting. Tried recompiling wxPerl from a fresh copy from cvs downloaded today (6/6/2001), but the current copy does not compile (gives the following error: XS/Locale.xs: In function `void XS_Wx__Locale_AddLanguage(PerlInterpreter *, CV*)': XS/Locale.xs:107: no method `wxLocale::AddLanguage' dmake.exe: Error code 1, while making 'Wx.o' Win2000, mingw, WxWindows 2.2.6, wxPerl from cvs around 5/21/2001 (this is the last time we grabbed from cvs that worked) d. |
From: Mattia B. <mb...@ds...> - 2001-05-30 20:45:21
|
Silly me... ftp://wxperl.sourceforge.net/pub/wxperl/0.06/ > Hello, > I just uploaded RPMs for wxPerl 0.06; they are built > on RedHat 6.2, wxGTK 2.2.7, Perl 5.005_03; maybe they will work > on Perl 5.6.0, probably not. I plan to provide RPMs for Perl 5.6 > soon, anyway. > > If you try them, please report any problem to > wxp...@li... > > Thanks > Mattia |
From: Mattia B. <mb...@ds...> - 2001-05-30 19:56:49
|
Hello, I just uploaded RPMs for wxPerl 0.06; they are built on RedHat 6.2, wxGTK 2.2.7, Perl 5.005_03; maybe they will work on Perl 5.6.0, probably not. I plan to provide RPMs for Perl 5.6 soon, anyway. If you try them, please report any problem to wxp...@li... Thanks Mattia |
From: Mattia B. <mb...@ds...> - 2001-05-21 19:19:23
|
> Would you believe ... IT WORKED??! Whee! Hourrah! > > Module Version OS > wxPerl 0.07 (from CVS 5/21/01 14:30gmt) Win2k > > Our stats: > ActiveState build 623 > wxWindows 2.26 > gcc 2.95.2-20001116 > > Great work!! Now we can start breaking stuff! ;-) > > Oh, and belated thanks for implementing html printing so quickly. Oh, if you use it, you're doing the less amusing part: testing... Thanks! Mattia |
From: Logan G. <lm...@es...> - 2001-05-21 15:00:26
|
Would you believe ... IT WORKED??! > Module Version OS wxPerl 0.07 (from CVS 5/21/01 14:30gmt) Win2k Our stats: ActiveState build 623 wxWindows 2.26 gcc 2.95.2-20001116 Great work!! Now we can start breaking stuff! ;-) Oh, and belated thanks for implementing html printing so quickly. --Logan |
From: Mattia B. <mb...@ds...> - 2001-05-19 12:35:17
|
Hello, I just finished a module ( ExtUtils::FakeConfig ) that allows overriding %Config values at Makefile.PL time. It comes with a pre-canned setup that allows compilation of modules for ActivePerl with MinGW; building modules is as easy as: perl -MConfig_m Makefile.PL dmake dmake test dmake install it is tested with: Module Version OS DBD::CSV 0.1022 Win2k DBD::ODBC 0.28 Win2k DBI 1.14 Win2k SQL::Statement 0.1016 Win2k Text::CSV_XS 0.20 Win2k wxPerl 0.04 Win2k For more information visit http://wxperl.sourceforge.net/ap_mingw/ Best regards Mattia |
From: Mattia B. <mb...@ds...> - 2001-05-09 20:23:10
|
Hello, since it seems I'm the only one tha can compile wxPerl w/ MinGW :-(, I just uploaded a .zip file containing a binary version for ActivePerl see ftp://wxperl.sourceforge.net/pub/wxperl/snapshot/ To use it: download to path\Wx-xxxxxxxx.zip mkdir snapshot cd snapshot unzip path\Wx-xxxxxxxx.zip ( or use WinZip / PkUnzip / whatever ) Then do: perl -Mblib="somepath\snapshot" your_program.pl New classes since 0.06: Wx::FSFile Wx::FileSystem Wx::FileSystemHandler Wx::InternetFSHandler Wx::MemoryFSHandler Wx::ZipFSHandler Wx::HtmlEasyPrinting Wx::PageSetupDialog Wx::PageSetupDialogData Wx::PrintData they are untested <lame excuse>I don't have that much time lately</lame excuse>, however wxFileSystem::AddHandler( new handler ) _does_ work, and probably HtmlEasyprinting too ( I'd be _really_ surprised if it didn't ). When I have some more time, I will test'em seriously, promise... this snapshot is intended as an exceptional measure, but it it interests someone, I can make snapshots on a more regular basis Regards Mattia |
From: Mattia B. <mb...@ds...> - 2001-05-04 09:26:44
|
> Category: None > Group: None > Status: Open > Priority: 5 > Submitted By: Logan Graves (lgraves) > Assigned to: Nobody/Anonymous (nobody) > Summary: Html printing (please?) > > Initial Comment: > Is the wxHtmlEasyPrinting class in the works > (realizing that wxHtmlPrintout & possibly > wxHtmlDCRenderer, may have to be implemented at the > same time)? Looking at docs it seems that you need only wxHtmlEasyPrinting, and maybe wxPrintData & wxPageSetupDialogData; all the three are really straightforward to wrap; one thing you may do is beta testing: once I resolve this %^$Q#$ compilation/link/whatever error mentioned elsewhere, then you might test if it works better than me ( because you use it in real programs ). If you don't want to compile it yourself, maybe I could setup some "nightly builds" for betas. > Or is Printing in general too far down on the > wxPerl "to do" list? Well, just before this mail, it was really far down, but this pushed it up a bit ;-) The problem with printhing is that it is a BIG subsystem, and IIRC, it makes no sense to implement only part of it ( wxEasyHtmlPrinting is an exception because it is self-contained, but I seem to remember that all other Print classes are interrelated... ) BTW: if you need other features, yous let me know: the TODO list isn't immutable... Regards Mattia |
From: Mattia B. <mb...@ds...> - 2001-05-04 09:26:37
|
> Sorry for not being quite clear before, we were doing > perl Makefile.PL USE_SHARED=0 > ..trying again with simply not specifying USE_SHARED at all had the > same results (it used dlltool, and still broke anyway) I was _really_ hoping it was that simple... > > binutils-2.10.91-20010114.zip > > gcc-2.95.2-20001116.zip > > ld-2.10.91-20010126.zip > > libbfd-2.10.91-20010121.zip > > make-3.77-mingw32.zip > > mingw-runtime-0.5-20010221.tar.gz > > mingw32-docs-html.exe > > w32api-0.5-20010301.tar.gz > > > > Tried these versions of the packages (well, with w32api 0.4), wxPerl > compiled fine again, and broke again in the same way. This is really > wierd. We have no idea what else could be going on here. Just to be sure, I did a fresh GCC install with these packages ( and w32api/mingw-runtime 0.4 ); after some header moving ( I have the w32api with the wrong packaging scheme... ), it compiled wxWindows, ( just had to change typedef long INT32; -> typedef int INT32; in jmorecfg.h ), then did a build with perl -MConfig_m Makefile.PL in the cvs snapshot you're using, guess what? all compiled/linked/run fine... Last chance: send me your build log ( dmake > build.log ) I _now_ remember I had a similar problem: it was caused by some combination of -mdll -lmsvcrt, or something like this ( the problem is that I don't remember if it happened with ActivePerl or perl built from sources, with dlltool or -shared... ) If it is this, it is a bug in Config_m.pm Thanks Mattia |
From: D.J.Moon <lm...@es...> - 2001-05-03 20:40:37
|
> if you built with > perl Makefile.PL USE_SHARED=1 > > the results should be _identical_ to previous results > Sorry for not being quite clear before, we were doing perl Makefile.PL USE_SHARED=0 ..trying again with simply not specifying USE_SHARED at all had the same results (it used dlltool, and still broke anyway) > 1 - if they are grabbed at the same time, there shuold be no problem > 2 - if GCC works & compiles wxWIndows & wxPerl, it is unlikely > that you have an unpacking problem... usually unpacking > problems result in weird compile/link time errors > That is good to know, at least by way of eliminating a level of paranoia about what could be wrong. > > binutils-2.10.91-20010114.zip > gcc-2.95.2-20001116.zip > ld-2.10.91-20010126.zip > libbfd-2.10.91-20010121.zip > make-3.77-mingw32.zip > mingw-runtime-0.5-20010221.tar.gz > mingw32-docs-html.exe > w32api-0.5-20010301.tar.gz > Tried these versions of the packages (well, with w32api 0.4), wxPerl compiled fine again, and broke again in the same way. This is really wierd. We have no idea what else could be going on here. |
From: Mattia B. <mb...@ds...> - 2001-05-03 19:25:46
|
> > > wxPerl 0.06 source tarball > > > wxWindows 2.26 > > > Win2000 Version 5.00.2195 > Okay, we tried using the new USE_SHARED option in the cvs (grabbed No, don't use it: using USE_SHARED you end up linking with g++ -shared _as it did previously_, by _not_ using it ( or setting USE_SHARED=0 ) you should obtain a dlltool/dllwrap default linking... the point of USE_SHARED is that I can use it for developement, while people not knowing/using it obtain a standard ( hopefully safe... ) build, or know what they are doing Sorry again for the wasted time. > using cvs, not the nightly zip, (since you wanted to know)) copy, but > that did not make a difference (i.e. still get the same error on > "dmake test"). We think that maybe trying to get a mingw setup more if you built with perl Makefile.PL USE_SHARED=1 the results should be _identical_ to previous results > closely identical to yours may be the next thing to try. Part of the > problem may be incorrect/incompatible versions of the various mingw > packages, and part of the problem may simply be that we aren't > unpacking them all together quite correctly. 1 - if they are grabbed at the same time, there shuold be no problem 2 - if GCC works & compiles wxWIndows & wxPerl, it is unlikely that you have an unpacking problem... usually unpacking problems result in weird compile/link time errors > To at least make sure that we are trying to work with the same > versions, we'd like to know (if you could) what versions/dates of the > various mingw packages you use. The packages that we have been > downloading are the following: binutils-2.10.91-20010114.zip gcc-2.95.2-20001116.zip ld-2.10.91-20010126.zip libbfd-2.10.91-20010121.zip make-3.77-mingw32.zip mingw-runtime-0.5-20010221.tar.gz mingw32-docs-html.exe w32api-0.5-20010301.tar.gz But is probably time that I get the "latest all" and try it out > (We have been using 0.4 of mingw-runtime and w32api, to avoid having > to go through the trouble of needing to patch the wxWindows source.) Different w32api versions should not make any difference, anyway Thanks for your patience... Mattia |
From: D.J.Moon <lm...@es...> - 2001-05-03 14:38:49
|
----- Original Message ----- From: "Mattia Barbon" <mb...@ds...> To: <wxp...@li...> Sent: Wednesday, May 02, 2001 5:07 PM Subject: Re: [wxperl-users] WxPerl 0.06 compilation on Win32 > > wxPerl 0.06 source tarball > > wxWindows 2.26 > > Win2000 Version 5.00.2195 > > > > "gcc -v" lists gcc version as: > > Reading specs from > > c:\gcc-2.95.2-1\bin\..\lib\gcc-lib\mingw32\2.95.2\specs gcc driver > > version 2.95.2 19991024 (release) executing gcc version 2.95.2-mingw > > snapshot 20010329 > I use a different one: > ---- > Reading specs from C:\Programmi\Devel\GCC\bin\..\lib\gcc- > lib\mingw32\2.95.2\specs > gcc driver version 2.95.2 19991024 (release) executing gcc version > 2.95.2-20001116 > ---- > but maybe it is an ld / libbfd problem... > Okay, we tried using the new USE_SHARED option in the cvs (grabbed using cvs, not the nightly zip, (since you wanted to know)) copy, but that did not make a difference (i.e. still get the same error on "dmake test"). We think that maybe trying to get a mingw setup more closely identical to yours may be the next thing to try. Part of the problem may be incorrect/incompatible versions of the various mingw packages, and part of the problem may simply be that we aren't unpacking them all together quite correctly. To at least make sure that we are trying to work with the same versions, we'd like to know (if you could) what versions/dates of the various mingw packages you use. The packages that we have been downloading are the following: binutils gcc (but we already know you're using gcc-2.95.2-20001116) ld libbfd mingw-runtime w32api (We have been using 0.4 of mingw-runtime and w32api, to avoid having to go through the trouble of needing to patch the wxWindows source.) |
From: <no...@so...> - 2001-05-03 13:47:22
|
Feature Requests item #421031, was updated on 2001-05-03 06:47 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=365655&aid=421031&group_id=15655 Category: None Group: None Status: Open Priority: 5 Submitted By: Logan Graves (lgraves) Assigned to: Nobody/Anonymous (nobody) Summary: Html printing (please?) Initial Comment: Is the wxHtmlEasyPrinting class in the works (realizing that wxHtmlPrintout & possibly wxHtmlDCRenderer, may have to be implemented at the same time)? Or is Printing in general too far down on the wxPerl "to do" list? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=365655&aid=421031&group_id=15655 |
From: Mattia B. <mb...@ds...> - 2001-05-02 23:04:19
|
<big snip> > Anyway... > in wxPerl source tree > build/Win32_MinGW.pm , at the bottom there is a function starting like > this: It was more than this: use the current CVS ( do you use cvs, or the snapshots I put in wxperl site? just curious... ), I made all necessary changes Sorry for the silly mistake... Mattia |
From: Mattia B. <mb...@ds...> - 2001-05-02 21:06:59
|
> wxPerl 0.06 source tarball > wxWindows 2.26 > Win2000 Version 5.00.2195 > > "gcc -v" lists gcc version as: > Reading specs from > c:\gcc-2.95.2-1\bin\..\lib\gcc-lib\mingw32\2.95.2\specs gcc driver > version 2.95.2 19991024 (release) executing gcc version 2.95.2-mingw > snapshot 20010329 I use a different one: ---- Reading specs from C:\Programmi\Devel\GCC\bin\..\lib\gcc- lib\mingw32\2.95.2\specs gcc driver version 2.95.2 19991024 (release) executing gcc version 2.95.2-20001116 ---- but maybe it is an ld / libbfd problem... > wxWindows dll compiles fine, wxWindows samples compile and run > fine, > wxPerl 0.05 source compiles, tests, and runs fine. Compiling wxPerl > 0.06 reports no errors, but running "dmake test" does the following.. > > C:\Wx-0.06>dmake test > C:\Perl\bin\Perl.exe -Mblib -IC:\Perl\lib -IC:\Perl\lib -e "use > Test::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;" > t\1_load.t t\2_inheritance.t Using C:/Wx-0.06/blib > t\1_load............Can't load 'C:/Wx-0.06/blib/arch/auto/Wx/Wx.dll' > for module Wx: load_file:Invalid access to memory location at mmm... weird > Not sure what's going on here, especially since this compiler > setup > works for everything _but_ wxPerl 0.06 (and higher, a cvs snapshot > pulled this afternoon (May 2 2001) from sourceforge had the same > results). I did notice that the makefile is using "g++ -shared" to > make the wx dll's, rather than the "old", 2 step linking process used > by the wxPerl 0.05 makefile (and the wxWindows 2.2.6 makefiles). FWIW wxWindows 2.2.6 can be set up to use g++ -shared ( there is a comment in src/makeg95.env ) Anyway... in wxPerl source tree build/Win32_MinGW.pm , at the bottom there is a function starting like this: sub dynamic_lib { package MY; my( $this ) = shift; my( $text ) = $this->SUPER::dynamic_lib( @_ ); return $text unless $text =~ m/dlltool/i; my $wximplib = MM->catfile( wxConfig::top_dir(), qw(blib arch auto Wx Wx.a) ); change the line return $text unless $text =~ m/dlltool/i; to return $text; and redo the whole build ( perl Makefile.PL ; ... ) And let me know it it works... Sorry for the bug, I use g++ -shared because it is faster, and should be better in general... BTW, your bug report is _great_ ( I mean: detailed / well explained ) Thanks Mattia |
From: D.J.Moon <lm...@es...> - 2001-05-02 18:03:02
|
wxPerl 0.06 source tarball wxWindows 2.26 Win2000 Version 5.00.2195 "gcc -v" lists gcc version as: Reading specs from c:\gcc-2.95.2-1\bin\..\lib\gcc-lib\mingw32\2.95.2\specs gcc driver version 2.95.2 19991024 (release) executing gcc version 2.95.2-mingw snapshot 20010329 wxWindows dll compiles fine, wxWindows samples compile and run fine, wxPerl 0.05 source compiles, tests, and runs fine. Compiling wxPerl 0.06 reports no errors, but running "dmake test" does the following.. C:\Wx-0.06>dmake test C:\Perl\bin\Perl.exe -Mblib -IC:\Perl\lib -IC:\Perl\lib -e "use Test::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;" t\1_load.t t\2_inheritance.t Using C:/Wx-0.06/blib t\1_load............Can't load 'C:/Wx-0.06/blib/arch/auto/Wx/Wx.dll' for module Wx: load_file:Invalid access to memory location at C:\Perl\lib/DynaLoader.pm line 200. at t\1_load.t line 4 Compilation failed in require at t\1_load.t line 4. BEGIN failed--compilation aborted at t\1_load.t line 4. t\1_load............dubious Test returned status 255 (wstat 65280, 0xff00) t\2_inheritance.....Can't load 'C:/Wx-0.06/blib/arch/auto/Wx/Wx.dll' for module Wx: load_file:Invalid access to memory location at C:\Perl\lib/DynaLoader.pm line 200. at t\2_inheritance.t line 4 Compilation failed in require at t\2_inheritance.t line 4. BEGIN failed--compilation aborted at t\2_inheritance.t line 4. t\2_inheritance.....dubious Test returned status 255 (wstat 65280, 0xff00) FAILED--2 test scripts could be run, alas--no output ever seen dmake.exe: Error code 2, while making 'test_dynamic' (Similar errors occur when trying "perl run minimal" to run a sample app) Not sure what's going on here, especially since this compiler setup works for everything _but_ wxPerl 0.06 (and higher, a cvs snapshot pulled this afternoon (May 2 2001) from sourceforge had the same results). I did notice that the makefile is using "g++ -shared" to make the wx dll's, rather than the "old", 2 step linking process used by the wxPerl 0.05 makefile (and the wxWindows 2.2.6 makefiles). |
From: Mattia B. <mb...@ds...> - 2001-04-14 14:17:52
|
Hello, I released the new version of wxPerl. The source package is available on the SouceForge download page at http://sourceforge.net/project/showfiles.php?group_id=15655 A binary PPM package for ActivePerl/Win32 and wxWindows documentation patched for wxPerl are available at ftp://wxperl.sourceforge.net/pub/wxperl/0.06/ ftp://wxperl.sourceforge.net/pub/wxperl/0.06/INSTALL.txt for details The PPM is based on wxWindows 2.2.6, the docs are wxWindows 2.2.6 docs + some wxPerl specific notes; you may browse the HTML version using the wxWindows help viewer. ( the only change in the docs since 0.05 is that the 0.06 docs are cross referenced, so if you don't need cross references you may save a bit of bandwidth ) Regards Mattia |
From: Mattia B. <mb...@ds...> - 2001-04-13 20:39:05
|
> Here's a small example demonstrating the issues we've found with the > PlSizer object. What do you mean exactly wuth 'PlSizer'? Wx::PlSizer is meant for user defined sizers: say you want a sizer doing something different than the standard sizers ( i.e. it lets you override a couple of sizer methods ). the MyPlSizer in the sample is (should) be just a Perl-written wxBoxSizer: excepting bugs, it does nothing else than a wxBoxSizer, if you look at the code, it is almost identical... > The enclosed app is mostly ripped from the WxPerl sample, Layout.pl . Thanks for the report ( I will correct the sample ASAP... ) > We posted this here, instead of to the Tracker, since it's notclear > if the problem lies in our methods, the PlSizer's code, wxWindows, or > simply the supplied manual. From what I understand, this is a problem in the sample ( the MyBoxSizer is broken in some way... ), not in Wx::PlSizer itself. Please correct me if I am wrong! ( and use Wx::BoxSizer ) Thanks Mattia |
From: Logan G. <lm...@es...> - 2001-04-13 14:55:16
|
Win98se & Win2000 WxPerl 0.05 (ppm binary) ActiveState 5.6 623 Mattia & listmembers (if applicable ;-), Here's a small example demonstrating the issues we've found with the PlSizer object. The enclosed app is mostly ripped from the WxPerl sample, Layout.pl . The first menu item, GoodPlSizer, is basically the same as the "MyPlSizerFrame" except we've placed the toplevel Plsizer directly on its frame, instead of on a panel. This one behaves as expected, just as it does in the sample. The second item, GoodBoxSizer, is almost the same as the first, but we've replaced the PlSizers with a standard BoxSizers and added the two lines at the bottom to fit & set the window's minimum size. This one also behaves as expected; initializing its size properly & setting its min size. The last item, BadPlSizer, is also almost the same as the first, except we have added the same two lines at the bottom to fit & set the window's minimum size. When this one comes up initially, its size is the size of the full screen (if the screen is 1280 x 1024, so is the frame--note it is not maximized ) It can be maximized, but... Any attempts to move or resize cause the window to jump to an even larger height and a ludicrous width. After some attempted resizing, the window may seem to disappeared, but we suspect that it's actual size & pos are so unreasonable to Windows that they aren't being displayed on the screen. We posted this here, instead of to the Tracker, since it's not clear if the problem lies in our methods, the PlSizer's code, wxWindows, or simply the supplied manual. L.Graves, D.Moon LM R&D |
From: <no...@so...> - 2001-04-05 18:34:16
|
Bugs item #414075, was updated on 2001-04-05 11:34 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=115655&aid=414075&group_id=15655 Category: None Group: None Status: Open Priority: 5 Submitted By: Logan Graves (lgraves) Assigned to: Nobody/Anonymous (nobody) Summary: Typo in Wx::Sizer.pm Initial Comment: wxPerl 0.05 PPM Wx::Sizer, Line 48 reads: Wx::_match( @_, $Wx::_wwin, 1 ) && return $this- >RemoveWinodow( @_ ); should be: ... ->RemoveWindow( ... ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=115655&aid=414075&group_id=15655 |
From: Amanjit G. <ama...@gm...> - 2001-03-17 22:40:26
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! > > downloaded the recent distribution and installed it with PPM. > Oops, I forgot tht samples are not included in PPM... > Sorry, I will upload them ASAP ( this means: while I send this mail ) Thanks a lot for the samples! I hope a lot of perl guys will pick on wxperl, I was quite happy to see so much working already. thanx for the samples, btw I checked some of the tutorial things on the web page as well. thanx a lot. -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com> iQA/AwUBOrPZQXQJ/f85m7B+EQKzDQCdGP7Dx/i36CnIspOH9I9fibD/nhkAoNx9 bOGItZB5f6VeFSvPQEisjSrH =0zxj -----END PGP SIGNATURE----- |
From: Mattia B. <mb...@ds...> - 2001-03-17 20:53:42
|
> I would like to know if anyone has some WxPerl samples handy, I > downloaded the recent distribution and installed it with PPM. Oops, I forgot tht samples are not included in PPM... Sorry, I will upload them ASAP ( this means: while I send this mail ) > I downloaded the .chm document file supplied at the ftp site for > wxperl, and searched for "perl" in the document, and found only one > hit?!? try searching for wxPerl... > Would just like to see some sample script to get me started.. Coming! Mattia |