On Mon, 2004-02-23 at 18:05, Jez White wrote: > I'm looking at this more from the users perspective, not as a hacker. > > I think a decision has to be made whether to make any new module is going to > be backward compatible or not. Personally, I think this would be a good time > to "start from scratch" and incorporate all the lessons that have been > learnt so far. Why not deprecate the OEM and only support NEM - this would > make the job easier for you guys, while reducing the amount of confusion on > our part? Users who are still reliant on OEM (myself included) would just > use the current code line until they are ready to upgrade. Some users would > be alienated, but in the medium term it would be a win win situation for > everyone. A clean, simple code line would be a benefit to all.
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 :-) > General things I'd like to see: > > * Destroy working correctly on all objects. as I said, this is a little nasty, but it can be implemented. > * The parent window (and or the control?) passed as first parameter for > every event (this would allow context aware event handlers - as Johan > Lindstom suggested a few weeks back). 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 > * A Win32::GUI website hosted on sourceforge (with lots content, > documentation and examples). 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. cheers, Aldo
