September 2003 (development
- First version.
- Built a database model that stores
all the statistical data for the applications. The database supports multiple
- Designed the main control window. The usage model is
apparent from the window design: the user can analyze as many applications as
she likes; the top-most application and a summary for all applications is
shown. Three main choices now exist: (1) do not optimize the top-most
application, (2) optimize the top-most application, and (3) optimize all
applications. Added three buttons for each of these choices. The obvious fourth
choice (do not optimize any of the applications) is equivalent to closing the
window or quitting Applimizer.
- Two optimization options are currently
available: language de-localization and HTML optimization. Applimizer can
optimize either or both; the user can decide.
- The user can control the
optimization through an options window that can slide out from underneath the
main window. Selecting or de-selecting an option will dynamically alter the
optimization statistics in the main window.
- Designed a custom data
formatter used by the text fields that show the size for the applications. It
will show both a short form of the size, for example 1.5 MB, as well as the
actual size in bytes.
- Added more statistics fields that show the
saving that is achieved. Two fields are added: the absolute saving and the
relative saving as a percentage of the overall size of the application(s).
- Modified the optimization algorithms to support the addition of new
optimization techniques in future versions.
- Known problem: HTML
optimization appears to hang.