Re: SilvaFind - a README.txt please

Marc Petitmermet wrote:
> dear developers
> 
> i don't want to offend anybody here; just allow me to give some comments 
> about SilvaFind and my usual nitpickings;-)
> 
> could anybody please write a README.txt for this product? i know that 
> it's not officially released yet but i just did a few tests and i'm 
> almost clueless here. there is a nice form in the edit view but the 
> public view shows "publication time : ('', '');" and a list of links 
> which are from a complete different domain...

The empty time display is fixed on the trunk, (maybe not checked in 
though, I'll check that right away). I'm not sure what you mean by 
different domain, but SilvaFind as it is now searches the Silva catalog 
in its entirety. Limiting the search to the current subtree is on the 
agenda though.

> ahhh, i need to check those boxes to enable the form. what about some 
> notes here (most silva products have notes but not SilvaFind)? or just 
> add a column heading "enable" above the checkboxes? and when nothing is 
> enabled the public view should not show anything.

Yes, thank you, the UI could use some looking at, I'll see that it gets it.

> i still don't know why it shows any results when nothing is searched for 
> and why it shows results from complete different domains (virtual host 
> problem?).

If no search criteria are entered, it returns everything, which is how 
zope catalog queries work, anything entered is used to 'limit' the results.

> the "from" and "to" fields are not fool proofed. i can get nasty zope 
> errors: DateError, SyntaxError, Unable to parse. the user really does 
> not know what syntax is expected.

Partly UI, partly better error handling, I will look at that as well.

> nitpicking 1: there are mixed upper lower cases: "Full", "From", "To" 
> but everything else starts with a lower case.
> 
> nitpicking 2: can you have a look at the rendered xhtml code. is it 
> intended that some fields have a class, some not; some have an id, some 
> not; some have a type, some not? i noticed this because the from/to 
> fields are rendered differently than the other fields in our setup 
> (borders).

> nitpicking 3: empty span tags. let me cite kit here, if you allow;-)
> https://infrae.com/issue/silva/msg7525
> 
> nitpicking 4: there is an "is" missing in the sentence bellow. my old 
> brain expects a "from" after the "or" and then the sentence doesn't make 
> any sense. but i guess that this is only my problem not being a native 
> english speaking person;-)
> 
> "This a special document that can show a list of content items resulting 
> from a search with specific values for criteria or a form to enter 
> search criteria before getting results."

All very good points, and I will take them along with the last 
iteration, thanks for the excellent feedback, and again sorry, for the 
lack of any documentation.

eric