From: Mattia B. <mb...@ds...> - 2002-09-11 08:29:01
|
On Wed, 11 Sep 2002, Jouke Visser wrote: >Hi, > >One thing that is beginning to increasingly annoy me is the fact that >it's not clear which modules should be loaded for specific Wx classes I >want to use. I'm doing a 'use Wx qw(:everything)' normally, and for >image-related classes I am supposed to do a 'use Wx::Image', for No >html-related classes, I am supposed to do a 'use Wx::Html' (even though >it's for the usage of 'Wx::HtmlWindow', not 'Wx::Html'). Wx::Html - anything related to wxHtml Wx::Help - anything related to the help system Wx::Print - anything related to printing Wx::FS - anything related to wxFileSystem Wx::Grid - anything related to wxGrid Wx::MDI - anything related to MDI Wx::STC - StyledTextControl Wx::XRC - XML resources Wx - you better do that first... In case some functionality crosses the boundary you need all related classes (e.g. Wx::HtmlEasyPrinting -> Wx::Html, Wx::Print; Wx::HtmlHelpController -> Wx::Help, Wx::Html). >Isn't it an idea to do a 'use Wx qw(:everything)' which preloads every >submodule that comes with the standard wxPerl distribution? Or even to >add another tag like 'use Wx qw(:allclasses)'? I prefer the latter, if it is to be implemented. >I think it should be clear when which module should be loaded, or not to I tink it is a simple matter of documentation; would it be visible enough if I added a "wxPerl notes" just below "wxPython notes"? >load specific modules at all. Regards Mattia |