Hi there,
I was fiddling around with the "2D Drawing example file" to check the JS optimisation, and switched on the "Optimise JavaScript Output" in Compiler Options....
However, it doesn't matter, if it's on, or off. The resulting JS is the same size, and the resulting library folder is always about 3.1mb.
In FireFox, loading time and sizes are the same with or without optimisation, and even the calls are the same.
Do I get this wrong, or should the output be smaller?
I am on a Mac, by the way - using SpiderBasic 2
Cheers
Jörg
Libraries aren't compressed
Re: Libraries aren't compressed
Optimize output only optimize the spiderbasic.js file, not all depencies (which are already compressed in SB 2.00). For a small program, not all dependencies are required, you can check this with the network tab of Firefox dev tools for example
-
- Posts: 40
- Joined: Fri Sep 25, 2015 12:00 pm
Re: Libraries aren't compressed
Ah, merci for the clarification. So, no bugFred wrote:Optimize output only optimize the spiderbasic.js file, not all depencies (which are already compressed in SB 2.00). For a small program, not all dependencies are required, you can check this with the network tab of Firefox dev tools for example

Is it then possible to just let Spiderbasic copy the needed dependencies when compiling? It doesn't matter for webspace, but an App on mobile devices should be as small as possible...