Permalink
Browse files

gtk debugged... moving to os/2 for testing

  • Loading branch information...
1 parent 42b714d commit ad3be79c1909febad0819651147eb0bce71c85da @rcaputo committed Oct 7, 2000
Showing with 282 additions and 177 deletions.
  1. +10 −7 Changes
  2. +18 −18 README
  3. +1 −1 lib/POE.pm
  4. +187 −118 lib/POE/Kernel.pm
  5. +2 −1 lib/POE/Session.pm
  6. +64 −32 tests/21_gtk.t
View
17 Changes
@@ -52,18 +52,21 @@ Version numbers have four fields: X.YYZZAA
`-----------------
-0.1108 2000.??.??
+0.1108 2000.10.06
-----------------
Added Gtk support. Added t/21_gtk.t to test it.
-(!!!) Broke Tk backward compatibility. Renamed $poe_tk_main_window to
-$poe_main_window so that it can be used sanely by different user
-interfaces.
+(!!!) Broke Tk backward compatibility. POE supports different X
+toolkits now, so it's silly to export ${"poe_$toolkit_main_window"}
+for each. Renamed $poe_tk_main_window to $poe_main_window. Both Tk
+and Gtk use it for the top-level/main window.
-(!!!) Broke Tk backward compatibility. Renamed the TKDESTROY signal
-to UIDESTROY so that it can be used sanely by different user
-interfaces.
+(!!!) Broke Tk backward compatibility again. POE supports different X
+toolkits now, so it's silly to have a separate DESTROY signal for
+each. Renamed TKDESTROY to UIDESTROY, and both Gtk and Tk use it.
+
+Updated POE::Kernel docs.
0.1107 2000.10.04
View
36 README
@@ -61,47 +61,47 @@ Finally you can install it:
Test Results and Coverage
-------------------------
-These are the `make test' results for POE 0.1106. Hardware: Cyrix
-P166+; 64MB RAM. Software: OS/2 4, fix 13; perl 5.6.0; no Perl/Tk; no
-Event.
+These are the `make test' results for POE 0.1108 on OS/2:
- All tests successful, 3 tests skipped.
- Files=21, Tests=365, 216 wallclock secs ( [line shortened here] )
+Hardware: Cyrix P166+; 64MB RAM.
+Software: OS/2 4, fix 13; perl 5.6.0; no Perl/Tk; no Event; no Gtk.
-These are the `make test' results for POE 0.1106. Hardware: AMD
-486-40 (overclocked to 50); 16MB RAM. Software: FreeBSD 4.0-STABLE;
-perl 5.6.0; Perl/Tk 800.021; Event 0.79.
+ -><-
+
+These are the `make test' results for POE 0.1108 or FreeBSD:
+
+Hardware: AMD 486-40; 16MB RAM.
+Software: FreeBSD 4.0-STABLE; perl 5.6.0; Perl/Tk 800.021; Event 0.79;
+ Gtk/Perl 0.7000.
All tests successful.
- Files=21, Tests=381, 565 wallclock secs ( [line shortened here] )
+ Files=22, Tests=391, 660 wallclock secs ( [line shortened] )
-These coverage results are for POE 0.1106 on the FreeBSD machine.
+These coverage results are for POE 0.1108 on the FreeBSD machine.
This machine more thoroughly tests different POE options, so the
coverage results are more meaningful. Even at their best, however,
-the results are highly misleading. They are, in fact, slightly low
-because of errors introduced by the profiling code. Please take these
-figures with a grain of salt.
+the results are highly misleading.
Source File = Ran / Total = Covered
- POE.pm = 19 / 21 = 90.48%
+ POE.pm = 19 / 19 = 100.00%
POE/Component/Server/TCP.pm = 23 / 23 = 100.00%
POE/Driver/SysRW.pm = 42 / 54 = 77.78%
POE/Filter/Block.pm = 37 / 37 = 100.00%
POE/Filter/HTTPD.pm = 11 / 100 = 11.00%
POE/Filter/Line.pm = 83 / 88 = 94.32%
POE/Filter/Reference.pm = 60 / 66 = 90.91%
POE/Filter/Stream.pm = 11 / 11 = 100.00%
- POE/Kernel.pm = 696 / 931 = 74.76%
+ POE/Kernel.pm = 795 / 1100 = 72.27%
POE/Preprocessor.pm = 119 / 138 = 86.23%
- POE/Session.pm = 85 / 194 = 43.81%
+ POE/Session.pm = 86 / 195 = 44.10%
POE/Wheel.pm = 9 / 11 = 81.82%
POE/Wheel/FollowTail.pm = 71 / 89 = 79.78%
POE/Wheel/ListenAccept.pm = 33 / 47 = 70.21%
POE/Wheel/ReadWrite.pm = 111 / 190 = 58.42%
POE/Wheel/SocketFactory.pm = 199 / 282 = 70.57%
- All Told = 1609 / 2282 = 70.51%
+ All Told = 1709 / 2450 = 69.76%
-Good luck, and thank you for reading!
+Thanks for reading!
-- Rocco Caputo / troc@netrus.net
View
@@ -7,7 +7,7 @@ use strict;
use Carp;
use vars qw($VERSION);
-$VERSION = '0.1107';
+$VERSION = '0.1108';
sub import {
my $self = shift;
Oops, something went wrong.

0 comments on commit ad3be79

Please sign in to comment.