Include legacy code in base2 automatically

[GoogleCodeExporter]

The base2 legacy code is fairly small, and I think it would be good if it
could be included in the packed base2 file automatically. We're either
going to give it to everyone anyways, or use nasty browser detection
methods to try and give it to only those browsers which need it, and will
almost certainly miss some.

Original issue reported on code.google.com by curiousdannii on 25 Jul 2007 at 4:04

[GoogleCodeExporter]

For the moment, we _could_ write an "build.html" (or "combine.html"), which can 
create a custom lib file, with 
only the components you need. The "build.html" will run from the file:// 
protocol, so it can use 
IO.LocalFileSystem. Lists the files in /trunk/base2/lib/src, and with a 
checkbox, you can choose which ones to 
include. The result will be optionally packed.

This would also be useful, when base2 is distributed in a ZIp-file via the 
Downloads TAB

Hmm. I don't have time for this. Something for you, Dannii?

Original comment by doek...@gmail.com on 25 Jul 2007 at 10:33

• Added labels: Priority-Low, Type-Enhancement, Usability
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

I don't want to include the legacy file automatically. It will add about 3K to 
the
final size and only about 1% of developers are interested in it. You can always
combine the two files into one file yourself and then compress it with packer 
or jsmin.

Original comment by dean.edw...@gmail.com on 26 Jul 2007 at 5:16

• Changed state: WontFix

[GoogleCodeExporter]

There's now a combine.html. Very rough, works in IE only I guess. The file 
should be
opened as a file (ie: file://c:\svn\base2\src\utils\Combine\combine.html).

You can find it in trunk/src/utils/Combine/combine.html

Original comment by doeke.zanstra@gmail.com on 6 Aug 2007 at 12:21