I've recently discovered Fossil, and have been migrating all of my repositories over to it. I was wondering about a few questions that I've come up with since I started using Fossil in my day to day life and wanted to see what the community's thoughts were on them.
1) Compress the releases found on http://www.fossil-scm.org/download.html using UPX ( http://upx.sourceforge.net/). While deploying Fossil to my home computers, work machines, and servers, I found the extra step of unzipping the "self-contained" executable unnecessary. Speaking from personal experience: UPX does its job flawlessly every time. There are entire Linux distributions compressed using UPX proving that it has no effect on executable integrity. UPX even does a better job of compressing the binary than ZIP does: linux-x86-20111021125253 (ZIP: 477K) (UPX: 383K) macosx-x86-20111021125253 (ZIP: 550K) (UPX: 473K) openbsd-x86-20111021125253 (ZIP: 537K) (UPX: 416K) w32-20111021125253.exe (ZIP: 498K) (UPX: 402K) Although, one caveat to this is that many Windows users have Anti-virus solutions installed that claim UPX compressed executables are either viruses, or "possible threats." Perhaps it would be best to leave the Windows release as a ZIP. 2) Add (or replace zlib with) LZMA. Some of my repositories are very large; the compression difference between the DEFLATE algorithm and the LZMA algorithm is not negligible, and can even be substantial. Recently, even the Linux kernel has officially begun using lzmalib to compress their releases: http://www.kernel.org/pub/linux/kernel/v3.0/ (even the difference between BZ2 and XZ is about 13M, or 31M smaller than GZ). A quick implementation of LZMA (by editing auto.def and blob.c's blob_compress, blob_compress2, and blob_uncompress) resulted in the following repository sizes for the latest trunk of SQLite: sqlite-zlib.fossil (4.8M) (~5.0K per file) sqlite-lzma.fossil (3.5M) (~3.6K per file) How's that for bandwidth efficient enough for " dial-up"? 3) The web interface could use a face lift, as well as some HTML5 functionality. I've got a lot of web development experience and would love to contribute in this area, also. All of the work on the JSON APIs is a great step toward making the entire interface XHR compatible. What are the community's feelings on jQuery? I get the gist that externals are trying to be avoided, so that's why I'm asking, I would love to write a library that turns the current site in to a highly interactive version without touching the HTML or CSS at all. Thanks for your time! I look forward to your replies. :D Sincerely, Caleb
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
