[Padre-dev] [Padre-commit] rev 997 - trunk/lib/Padre

[Adam Kennedy]

In particular, the biggest targets should be things like PPI that are
external to the Padre and are not needed before the initial window
loading. Another obvious candidate are any Padre::Wx:: classes that
aren't needed until post-startup.

Some of these have Class::Autouse hooks in already, so they already
defer loading.

Before you remove the loading of a Padre:: class, start up the
application and look at %INC.

You should be able to see which classes are loading, and which are autoloading.

Adam K



2008/11/15 Jerome Quelin <jquelin at gmail.com>:
> On 08/11/14 19:40 +0200, Gabor Szabo wrote:
>> ok, I am not sure if this really helps as Padre::Document is so essential
>> without it we won't be able to open any document anyway.
>>
>> so I am not sure we need to require these.
>> what do you think?
>
> indeed. do that for non-core module / non-core features.
> jérôme
> --
> jquelin at gmail.com
> _______________________________________________
> Padre-dev mailing list
> Padre-dev at perlide.org
> http://mail.perlide.org/mailman/listinfo/padre-dev
>