jwbaumann ,

I appreciate your thoughtful response. The comments that you added were quite useful. Remember that this is basically a 1.0 release of the product and there are a lot of ways in which it can be enhanced.

I have interspersed my responses below.

> Regarding wastefulness of screen real estate and the limited
> travel of the vertical pane divider - I am running at 1024 X 768.
> Even if I enlarge Parsnips to fill the entire screen, I can
> slide the divider less than a third of the window width, and
> at that window size, Parsnips is definitely hogging screen real
> estate.

I have fixed the problem of the divider not allowing full movement to one side or the other. I also added a quick way of fully collapsing it to the left or right

> Regarding the relevance being purely eye candy - if I create
> an item with a title of "fruit", keyword of "apple", and
> content of "macintosh", save it, then search on "apple",
> the relevance is only 38%. In order to make the relevance 100%, I must change all 3 words (title, keyword, and content) to "apple".
> This is just plain silly.

The "relevance" number is provided by the Lucene search engine upon which Parsnips is based. I really have no control over that. However, it is based on solid principles. In the example cited, if the title, keyword and content did all contain the word "apple", shouldn't the relevance be higher than if only one field did? Sure seems reasonable to me.

> Regarding a "Show All" feature, you are correct in that searching
> for a blank string finds all records. This is completely
> unintuitive yet fully logical and functional (ie. Unixy, not
> Mac-like ; ) But thank you for solving a vexing problem
> I've had using Mulberry, an otherwise excellent e-mail
> program. Nevertheless, I would add a "Show All" button.

With respect to the "Show All" feature request: You must not use Mail, Address Book or any of the other Apple apps that use this metaphor. If nothing is searched for then all items are displayed. When there is a search string, and only a subset of items are shown, there is an "X" to the right of the search string to clear it and re-show all the items. That said, I certainly wouldn't mind adding a menu command to "Show All Items", mainly because I could then attach a keyboard shortcut to it. I will put this on the list.

> Regarding searching for substrings, this is probably more a
> philosophical issue than a technical or interface question.
> If the string "Now is the time for all..." exists in the
> database, and I search on "me fo", I expect to find a match.
> I don't want to even have to think about using wildcards
> and other geeky technical unixy terminology.

> Regarding "stop words" - this would be solved by the above
> suggestion. I was going to say that since the Parsnips database
> presumably contains only my files and info, I don't want to be
> "stopped" by my own stuff, but I see now that Parsnips can be
> used to index very large amounts of data, so this is not
> strictly a fair statement, more an expectations asymmetry.

With respect to searching for substrings: It is just not possible to have it work the way you suggest. Parsnips is designed to hold up to millions of items. Searching can't happen by brute text searching. Like all sophisticated search engines, Parsnips build a reversed index to implement quick searching. Stop words are essential to keep the index to a reasonable size. Likewise, that is the reason for wild-card characters. In a perfect world I agree your way would be preferable, but there are tradeoffs.

> Regarding drag and drop - maybe expected too much, but I tried
> the following behaviors and all failed:

> 1) Drag a text file onto the Parsnips icon in the Finder
> 2) Drag a text file onto the Parsnips icon in the dock
> 3) Drag text onto the Parsnips icon in the Finder
> 4) Drag text onto the Parsnips icon in the dock
> 5) Drag a text clipping onto the Parsnips icon in the Finder
> 6) Drag a text clipping onto the Parsnips icon in the dock
> 7) Drag a text file onto the item side of Parsnips when
> not in an editable state
> 8) Drag text onto the item side of Parsnips when not in an
> editable state
> 9) Drag a text clipping onto the item side of Parsnips when
> not in an editable state
> 10) Drag a text file onto the item side of Parsnips when in
> an editable state.

> Dragging must happen onto the list (left) side of the window
> (and yes, this is clearly noted in the documentation, but
> remember, Mac users don't, as a rule, RTFM). But if the
> window is expanded to fill the screen, it is very difficult
> to position things to allow drag and drop to occur. Also,
> the documentation mentions the "Drop Window," but I cannot seem
> to find it.

With respect to your drag and drop issues: This is a Java application and unfortunately Apple doesn't provide any hooks for me to get at anything dropped on the application icon or the doc icon. Sorry, but that is the state of Java on Mac OS X.

With respect to dragging onto the right (Display) side, it works this way because when the item is editable, a drop onto the editable text should insert the text at the insertion point. It should not create a new item with that text. When it is uneditable, I think it would be confusing to have an item created then. The drop should do nothing in this case.

> Another problem is that Parsnips will allow me to import the
> same directory twice, without checking for duplicates and
> warning me, thus bloating the database with duplicates.
> This makes it difficult to keep Parsnips and a directory in sync.

You are right that this is a problem. It will be fixed in the next version that should be out in about a week.

> It also appears that Parsnips will not import subfolders. Perhaps
> a preference, popup dialog, or different target in the Parsnips
> window would allow this functionality.

It used to recursively index subfolders. I disabled this because it was too easy to accidentally try to index something that would take forever (like "/"). I think the suggestion to ask via a popup dialog is the way to go here.

> I see that when I go to a specific item, it is non-editable.
> I can see the benefits for some people, but I would like the
> item to be immediately editable, especially if it is an item
> I manually created inside Parsnips. This would definitely be
> something for a preferences window, as follows:
>
> Make found items immediately editable
> o Always
> o Never
> o Only for items I created in Parsnips

Your suggestion has got me thinking of just always having items be editable. At the very least this could be a preference.

Thanks again for taking the time to provide constructive comments. If you wish to continue perhaps you should just email me bill@otherwise.com