> still, I don't see the need to "start from scratch" as you say. once the
> new NEM will be implemented, supporting OEM will be absolutely
> transparent in terms of coding. think of it as a Unified Event Model
> architecture. OEM will be deprecated in terms of performance, but it can
> stay as it is. developers will be able to concentrate on events itself
> and not worry about users calling them as OEM or NEM, trust me :-)
No problem:) I still think there is scope and opertunity for change if you
guys need it...
> no. the current plan is:
> - the object itself will be passed as the first parameter for every
> event with NEM (*and* there will be a method to get a reference to its
> parent, as well as another method to get a reference to its topmost
> container)
> - OEM will stay as it is, that is no object is passed to events
Sounds good to me. I assume you could something like:
sub SomeEventHandler {
my $self=shift;
my $win=$self->Parent;
}
>
> I have already set up a simple wiki (a Kwiki, actually) at:
>
> http://perl-win32-gui.sourceforge.net/cgi-bin/index.cgi
>
> I just hacked Kwiki a bit to let it grok POD text, because I *want*
> documentation to be in POD natively. personally, I find the concept of
> wiki to be a good idea in this case, so this site (eg. the home of
> perl-win32-gui.sourceforge.net implemented as a wiki) could be the
> repository of all things Win32::GUI, and everybody could contribute.
Sounds good. Steve has added lots and lots of doco in the last few weeks -
may that effort continue, with us all contrubuting:)
One thing I would suggest, is to add a way for people to submit example code
(perhaps catagorised by control?).
Cheers,
jez.
