Greetings all With the 0.88 release looking so stable (notwithstanding Sewi's issues) my thoughts are starting to turn towards what is left to go for 1.00 and what we can do to simplify the job of maintaining compatibility for plugins as long as possible after 1.00.
So I'd like to propose a big sweep over the entire codebase, and to break as many API things as possible now rather than later. For example: Padre does not import constants from Wx because there's simply too many, and across hundreds of classes this can add up to 10's of megs of ram just for constants. As a result, we're stuck using the somewhat ugly Wx::wxFOO style constants (which also aren't constants since they are AUTOLOAD hooked). I'd like to move to using a naming scheme similar to wxPython and use Wx::FOO instead. While ultimately we need support from Wx.pm for this different style of constant, in the short term I've implemented a demonstration you can see with use Padre::Wx ':api2'; This will call all 3000 of the constant functions in Wx and capture their values. It then calls constant.pm with all the captured values to create "proper" constants with the shorter naming style. Along similar lines, we have a lot of methods named "on_foo" scattered around the API. I'd like to clean some of these up, so that we only use on_foo_bar for handlers which actually catch events directly (i.e. Are passed Wx::Event objects) rather than the mix of some having it and some not that we have now. Adam K _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
