Better Explanation of Settings

This might belong in Ideas for 2.0 http://drupal.org/node/563576

After install, (if you see it) at the top of the module list, because the top of that page is bunches of words.
Edit, 1 line: Can't remember what D7 has there now. But D6 will be strong for years.
----------
...text overload....
...text overload....
...text overload....
...text overload....

* Boost successfully installed. Please review the available 'configuration''settings'.
* Drupal's standard page caching disabled by Boost.
* The configuration options have been saved.
----------
'configuration' and 'settings' are two links one to 'performance', and one to 'Boost-settings'.

A. my thoughts..
The link should be only to Boost-settings.
why? Because a common selection will be regenerate or Preemptive cache.'performance'

Problem, Preemptive cache checkboxs are not available until choices are made in Boost-Settings. Boost cacheability settings, Checkboxes: URL variable pages, html doc/pages, xml/feed, ajax/json, css and js.

Avoid problem, Consider the Link(s) 'configuration' and 'settings' to be one link to Boost-Settings as a starting point. Doing setup first, then turn it on.

EDIT, remainder: Another thought on this.
If a user installs Boost, but does not set it up at that moment, and does not see the Notice about Drupal Cache being disabled... oops. Possibly some bold text Drupal's page cache disabled in performance settings. Just because of the text overload on that page.
-yep.. picky, picky, picky

Performance pages notes-- so far--

TAB, Performance(Boost settings):

-----------------------------------------------------------------------
1.Boost cacheability settings
Boost will cache pages that end with ?page=1 (among others).(define others)

------------------------------------------------------------------------
2. Reason for this comment. Disable usually means to un-check the box to disable.

(checkbox, empty) Do not cache if error on page
- Boost will not cache the page if there are PHP errors or drupal messages.
- Disable this if you want to cache pages even if it might contain errors.

(checkbox, empty) Do not cache if error on page
+ Not selected will cache pages with PHP errors or drupal messages.(default)
+ Selected will Not cache pages with errors or Drupal messages.

---------------------------------------------------------------------------

Ignore cache flushing:

'flushing' is the right word, but all the Drupal buttons say 'Clear-Cache'
This means keep all static pages and ignore 'Clear-Cache', 'flush' or 'delete' commands, with three ignore choices.

A new person will have to think about this for a while. There is an unfamiliar word disconnect from Ignore and flush to clear-cache.
Possibly make it real familiar by using

- Ignore cache flushing:
- *Disabled. (We all know this one.)
- *Only Ignore Complete Flushes
- *Ignore Flushes & Expiration
- *Ignore All Delete Commands (Not Recommended)
- Enable to put your site into a static state. Recommend turning on CSS & JS caching if enabled.

+ Ignore cache clearing:
+ *Disabled.(default) (We all know this one.)
+ *Only Ignore Complete Clear-cache Commands? or Actions?
+ *Ignore Clear-cache commands and Expiration of cached pages? or files?
+ *Ignore all Clear-cache Commands (Not Recommended)
+ Make a selection to put your site into a static cached state. Recommend turning on CSS & JS caching if enabled.

--------------------------------------------------------------------------------

Verbose Setting: select box
(please verify) I just have no solid info without searching, or testing stuff.

This is for the Db Log?
Setting for the length of error notice?

That's my non-wizard guess, without playing with it.

------------------------------------------------------------------------------------
This might belong in Ideas for 2.0 http://drupal.org/node/563576

Boost directories and file extensions

...The top section needs to stay open for visibility...
Cache Dir:
(Database checkbox)
Cache file path:

...These sections could be collapsed like the htaccess generator...

Generated output storage (HTML, XML, AJAX)

Static storage (CSS, JS)

------------------------------------------------------------------------------------

might as well clog this up some more.. everything is food for thought..
I will say that I have read many long threads about (one) word in the Drupal usability issues.
This module has a lot going on, and an easy read through the settings will help people use it right.

...........................
Status report:
// Just After install, Before setting anything. just nitpicking.

- [x]Boost Configured correctly, should be working.
+ [x]Boost Installed correctly, should be working if configured.
................................

Boost settings page:
Boost advanced settings:

///////////////////////////////////////

- Purge expired cache files on cron runs:
- [ ] Disabled
- [x] Enabled(default)

- Whether to perform a purge of all expired content from the static page cache on cron runs. How often your cron runs works together with the minimum cache lifetime setting, further above, to determine the effective minimum lifetime for items in the static page cache. If you don't enable this setting, you will need to put in place some other custom mechanism for purging expired files, or else they will never be removed (unless manually cleared from the administrative interface).

+ Clear-cache of exspired pages on cron runs:
+ [ ] Disabled
+ [x] Enabled (default)

+ Enabled will clear-cache of all expired content in the cache directories on cron runs. How often your cron runs, works together with the minimum cache lifetime setting on the Performance page. Caution; Disable this setting and you will need some other method of clearing cached pages. If Disabled, files can be manually deleted from server or cleared using the administrative interface.

//////////////////////////////////////

- [x] Expire content on cron only if the sites content has changed.
- Check timestamps in the database for any changes to the site. If theres been a change, flush the expired content.

+ [x] Clear cached content on cron only if the content has changed.
+ Checks the timestamps in the database for any changes to the pages. If there's been a page change, cron will clear them from the cache.

////////////////////////////////

// Here i go with changing the proper word again, it's not my fault. Clear-cache....

- Flush directories from cache if they are empty
+ Clear all empty folders from cache.

- Flush all cached terms pages associated with a node on insert/update/delete
+ Clear all cached pages with terms associated with a node on insert/update/delete
// I just don't know about this one, still not worded right. There has to be a better way to say it.

////////////////////////////////

Do an iframe javascript cookie test for gzip:
Inject an iframe on the homepage on the non-gzip version to check if the browser can actually handle gzip encoding. See Website Performance - Activate Gzip for reason why.

// I went to the website, still don't know why I should run this test?
// People visiting the website may be using several different browsers?
// This is an advanced tool for developers or Themers to test all known browsers with?
// Wouldn't Gzip be documented, known and available in all major browsers at this time?
// I don't think many regular Drupal users will get it. I have been Drupaling for a year, I don't?

////////////////////////////////

// Touch URLs is recognizable to some people, but pre-cache is more in tune with other language on the page.

[checkbox] Enable the cron crawler
- Touch some select URL's so they are cached before anyone accesses them.
+ Pre-cache some URL's so they are cached before anyone accesses them.
// The word some might could use some clarification.

[checkbox] Crawl All URL's in the url_alias table
- Preemptively cache all urls found in the url_alias table. This will crawl that page even if it is not expired. Enable & run cron to get the boost cache loaded.

+ Pre-cache all urls in the Drupal url_alias table. This will crawl all pages even if they are not expired. Enable & run cron to preload the boost cache.

////////////////////////////////////

Clear Boost's Database

Warning: This gives you a clean slate for the boost database, use with caution.
//possibly a clear sentence about why and/or when to use it.

Your fast. This was all up for discussion,lol. Have applied patch, let it sink to my little mind. Will do another run through this weekend and take notes.

note: I am not real comfortable proposing changes to a developers' work of art, being a dummy and all. Hopefully no offense is taken and it might help new Drupal people. I know the 'crowd' doesn't need any of this. That said, I will put my 'picky' hat back on. lol

Noticed one item:
--------------------
Clear expired pages on cron runs:
[ ]Disabled
[x]Enabled
Enabled - Will clear the boost file cache of all expired content. How often your cron runs, works together with the minimum cache lifetime setting on the Performance page.
- Disabled - (Caution) This setting and you will need some other method of clearing cached pages. If Disabled, files can be manually deleted from server or cleared using the administrative interface.

// I don't know, the first sentence just reads strange the way it is. Maybe...

+ (Caution) - If Disabled you will need some other method of clearing cached pages. If Disabled, files can be manually deleted from server or cleared using the administrative interface.
-----------------

Out Of Service. damit, I have lost cable(internet) and main electric power to my house, shop and office. I am working on reserve power with an OLD laptop. I hope to have the main electric service restored in few days. I managed to get internet wired temporarily, I climbed up the pole with a new cable, lol. It sucks, i feel lost.
Off Topic RC4: only got the one site loaded and it is still working as expected, just checked it.
I will be back on this when I get power back. sorry for the delay, I know you want to progress towards RC5.