We are considering pruning the main ZIM file [not doing this]

General
1

EDIT - after doing the calculation... this would save about 38K of g-zipped minified code - so have decided it is not worth it.

For ZIM 019, we are considering moving some of the lesser used features of ZIM into a "general" helper module. Or we could call it something fun like "satellite", or "kitchen" or something. We don't have to... it would just make the ZIM file smaller for most apps.

It would mean to use these features, you would have to import ZIM_satellite.

Here is a list of what we are thinking in the order they are found in the Docs. Comments are welcome.

Speech - 4,332
SlicedBitmap - 7,799
Flare - 21,671
MultiFlare - 2,576
FlareBox - 2,776
Layer - 15,477
Slicer - 20,768
SlicerTypes - 5,580
Radial - 13,516
RadialMenu - 11,027
Connectors - 39,040
Marquee - 9,993
HotSpot - 2,276
HotSpots - 4,205
Pack - 22,832
Beads - 4,443
Accessibility - 37,399
Portal - 2,205
Timeline - 11,001
Pixel - 6,760
Parallax - 5,844
VR - 16,761
Wonder - 3,577
Rive - 3,114
RiveListener - 7,082

When minified, this would save 133K. When g-zipped, this would save 38K.

1 Like
2

maybe also
marquee
teleport
indicator

3

I'm not sure how significant this division is.
The goal is to reduce loading time at first?
I'm curious to know if you are thinking of putting all the least used features into one file or will there be a division there too?

4

We were considering taking some of the less used classes out into one other import. But we are not going to do it. I went through that list and calculated and it only saves 38K initial load. It is not worth it. So we are not going to do this. But it was a good exercise to see if that would help... and it really does not - so now we know. ZIM will remain whole!

2 Likes