wxperl-users

[wxperl-users] Loading of modules

[Jouke V. <jo...@pv...>]

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 
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').

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 think it should be clear when which module should be loaded, or not to 
load specific modules at all.

-- 
 ---------------------------------------------------------------------- 
| Jouke Visser            | http://jouke.pvoice.org  (personal)        |
|                         | http://www.pvoice.org    (pVoice & pStory) |
| Perl GUI Geek           | http://wxperl.pvoice.org (wxPerl)          |
 ---------------------------------------------------------------------- 

Re: [wxperl-users] Loading of modules

[DH <cra...@ya...>]

I too dislike this.
It's also a pain in the ass cause there is no pod in
any of the modules,
so you can't figure out by reading the pod that you have to
use Wx::Html to get at Wx::HtmlWindow, you have to go diving in the sourcecode.

If anything, Wx::Html ought to have pod saying
that in order to use Wx::HtmlWindow, you have to use Wx::Html.

If I had enough brains to do this, Wx::Whatever would be in its own file,
complete with documentation

--- Jouke Visser <jo...@pv...> 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 
> 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').
> 
> 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 think it should be clear when which module should be loaded, or not to 
> load specific modules at all.
> 
> -- 
>  ---------------------------------------------------------------------- 
> | Jouke Visser            | http://jouke.pvoice.org  (personal)        |
> |                         | http://www.pvoice.org    (pVoice & pStory) |
> | Perl GUI Geek           | http://wxperl.pvoice.org (wxPerl)          |
>  ---------------------------------------------------------------------- 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> In remembrance
> www.osdn.com/911/
> _______________________________________________
> wxperl-users mailing list
> wxp...@li...
> https://lists.sourceforge.net/lists/listinfo/wxperl-users


__________________________________________________
Yahoo! - We Remember
9-11: A tribute to the more than 3,000 lives lost
http://dir.remember.yahoo.com/tribute

Re: [wxperl-users] Loading of modules

[Mattia B. <mb...@ds...>]

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