Ken, Alain, et al,

Since I've contributed nothing to this fantastic project, I'd like to 
submit the name "WordIndy" for consideration, having mostly an American 
double meaning: "Indy" for both "Indexer" and "Indianapolis", the famous 
race that pretty much defines "speed" in the auto world. This would 
almost assuredly avoid copyright and trademark conflicts as well. Of 
course, some of you will consider it too be a bit too obtuse.

Joe Wilkins

Ken Shmidheiser wrote:

> Alain, true to character, issues the understatement of the year:
>
>
>> --- snip --- I have enhanced Word Indexer a little bit.
>
>
>
> Alain,
>
> Putting me on the same page as Columbus means you must rank up there 
> with NASA!
>
> Great job with the excellent new features-- especially drag and drop!
>
> Just a few comments and questions:
>
> 1. For consistency, I recommend we change all occurrences where the 
> name of the app appears, including the output file, windows and 
> titles, to either "Word Indexer" or, perhaps, the more diminutive 
> "Wordexer" (which would seem to circumvent copyright or trademark 
> problems from a cursory web search. I had considered the Latin "Index 
> Verbum", as well as the longer, more "pun-ish"-- or perhaps "punish", 
> dependent on viewpoint-- "New Word Sorter". R.C. or others on the list 
> might have some clever ideas.) During development I kept changing the 
> name as is now reflected by inconsistencies throughout the code.
>
> 2. There is a window refresh problem in PPC when a sort/index on very 
> large files. When the navigation dialog is opened to find a file, it 
> clips the contents of the main window beneath it. The contents of the 
> main window are not redrawn until the search is over, making it appear 
> that the app has stalled. The problem does not occur in OS X. (During 
> most of my development I used the 4.2mb text of the King James Version 
> (KJV) of the Bible as the test document in an attempt to make the code 
> industrial strength.) I have tried a variety of window refresh 
> techniques to solve this cosmetic problem, but without success.
>
> 3. Another problem when working with massive text files is that the 
> progress bar appears to stall at "Sorting word list...". Again I have 
> been unsuccessful in implementing an incremental progression of the 
> progress bar while Quick Sort is doing its thing. Any help here will 
> be greatly appreciated. Perhaps we could turn the progress bar to 
> indeterminate during the sort, at least to provide the user visual 
> feedback that the app has not stalled. However, I can't get that 
> working either, At a minimum, we probably should changed the edit 
> field message to:
>
> "Sorting word list (this may take a few minutes on very large files)..."
>
> 4. For some reason, the 200000 default setting for _splitArraySize 
> works fine for the KJV in PPC, but needs to be set to 950000 to work 
> in OS X. I do not understand why this occurs. It would appear to me 
> that just the opposite should occur with OS X's touted superior memory 
> management. Perhaps we could add a user preference to set a higher 
> array size for very large text file sorts. Any thoughts?
>
> 5. The app takes about 100 seconds to index the KJV with strip 
> punctuation, count occurrences, smart sort and unchanged case settings 
> on. It takes about three times that in PPC. I'm using a B&W G3 350. (I 
> should be getting a new G5 at work soon and will look forward to 
> testing it on that platform.) As we've experienced, files under a meg 
> in size literally zip by.
>
> 6. In a single incident, all three radio buttons were unmarked when 
> the app was launched in OS X. Clicking one properly activated them.
>
> 7. I have rewritten the About Window function to make it more 
> attractive in PPC and more compliant with OS X's HIG. (In final builds 
> I would like to add a nice icon.)
>
>
> local fn AboutWindow
> '~'9
> dim as str255 infoStr
> dim as rect   r
>
> setrect( r, 0, 0, 250, 210 )
> appearance Window -_aboutWnd, "About Wordexer", @r,¬
> _kDocumentWindowClass, _kWindowCloseBoxAttribute
>
> def SetWindowBackground( _kThemeActiveDialogBackgroundBrush,_zTrue)
>
> text _helvetica, 16, _boldBit%, _srcCopy
> color _zBlue
> setrect( r, 20, 15, 230, 35 )
> edit field -10,, @r, _statNoFramed, _centerJust
> infoStr = "Wordexer 1.0"
> edit$(10) = infoStr
>
> text _helvetica, 14, _boldBit%
> setrect( r, 10, 40, 240, 60 )
> edit field -11,, @r, _statNoFramed, _centerJust
> infoStr = "Word Counter, Sorter & Indexer"
> edit$(11) = infoStr
>
> text _applFont, 10, 0, _srcCopy
> setrect( r, 0, 70, 250, 185 )
> color _zBlack
> edit field -12,, @r,_copyOnlyFramed_autoGray,_centerJust
>
> infoStr =¬
>   chr$(13) + "   A small utility to designed"¬
> + chr$(13) + "to quickly count, sort and index words"¬
> + chr$(13) + "and expressions in a variety of text files."¬
> + string$( 2, 13 )
> edit$( 12, _maxInt, _maxInt ) = infoStr
>
> infoStr =¬
>              "FB^3 Code by Ken Shmidheiser"¬
> + chr$(13) + "and Alain Pastor"¬
> + chr$(13) + "2003"
> edit$( 12, _maxInt, _maxInt ) = infoStr
>
> edit field 0
>
> Def WindowReposition( _aboutWnd, _mainWnd,¬
> _kWindowAlertPositionOnParentWindowScreen )
>
> window _aboutWnd
>
> end fn
>
>
> Thanks again, Alain, for all your efforts in our behalf. I haven't 
> been able to find an OS X utility out there that does the things 
> Wordexer does.
>
> Ke
> n