BulkLoader Request/Suggestion

[gil...@gmail.com]

I noticed that bulk loader compiles into an empty project with a lot
of weight. This is because of all the loading types. For example, if
you are creating a project without any sound, the Sound object still
gets compiled into your SWF because of BulkLoader.

My request is this: Break the BulkLoader class into two classes:
BulkLoader and BulkLoaderCore (or something like that).....

The new BulkLoader class would function exactly as it does now, but
most of the code would be in the BulkLoaderCore class. (BulkLoader
would be a wrapper with all the convenience functions and
automatically loaded loading types). The BulkLoaderCore class would
not have any imports or references to the loading types, and it would
not contain convenience (casting) functions like BulkLoader.getSound
(...)

I think that the new bulk loader would be applicable to projects with
strict file size requirements, because you could write your own
wrapper for BulkLoaderCore that would only be as heavy as need be..

[Arthur Debert]

Hi Gilbuns.

> I noticed that bulk loader compiles into an empty project with a lot
> of weight. This is because of all the loading types. For example, if
> you are creating a project without any sound, the Sound object still
> gets compiled into your SWF because of BulkLoader.

The thing is, all native classes (Sound, MovieClip, Bitmap) do not
make a difference on the compiled swf filesize, as they are native to
the player.

> The new BulkLoader class would function exactly as it does now, but
> most of the code would be in the BulkLoaderCore class. (BulkLoader
> would be a wrapper with all the convenience functions and
> automatically loaded loading types). The BulkLoaderCore class would
> not have any imports or references to the loading types, and it would
> not contain convenience (casting) functions like BulkLoader.getSound
> (...)
>
> I think that the new bulk loader would be applicable to projects with
> strict file size requirements, because you could write your own
> wrapper for BulkLoaderCore that would only be as heavy as need be..

Since the native classes are not compiled, this would get a small
filesize difference (2 kb max). This would only save the byte code for
the conviniece functions.

I understand the need, I have been calling BulkLoader by BloatedLoader
for while, but this would require some major changes only to save 2/3
kb. Having a single, simpler LoadingType could make a difference, but
that would make the code a mess (this is how it use to be before the
loading item refactor). This is, one of the reasons why I, at this
point, won't code any new features unlees it is something very
important.

Cheers
Arthur Debert