Re: [StrongED] Re: Manual - opinions?

[Fred Graute <fjgraute@xxxxxxxxx>]

In message <f94907b256.John@xxxxxxxxxxxxxxxxxxxxxx>
          John Rickman <rickman@xxxxxxxxxxxxx> wrote:

> In message <56b1c295b1tim@xxxxxxxxx>
>           Tim Hill <tim@xxxxxxxxx> wrote:
> 
> > so I'd be in favour of
> > lots of examples. Maybe have one or two on the main page with "more..."
> > leading to another.
> 
> I agree,and prefer examples to be as short and clear as possible.

More complex examples will be needed too as all the elements of the
advanced search syntax are easy to understand individually. The
difficulty is in how to combine them to achieve the desired outcome.

> The "to be or not to be..." example  tries to do too much.
> It is fine for further study but is overly complex as an introduction.

Agreed, a shorter example to start with would be better.

> Something along the following lines may be easier to grasp:
> 
> Purpose:   Add a string after a date
> 
>      search arg         @1##"."##"."##@2
>      replace arg        @12" -->"

It's not necessary to put markers at the start and end of a search
expression. @0 (start) and @9 (end) are set automatically.

> Second, having read the explanation of couNt, I am not clear on how to
> use it, and the real life example was off-puttingly long and 
> complicated.

Understanding the replace counter takes a bit of time but once mastered
it can be very useful at times. I have another real life example that
might be easier to follow once I've cut it down a bit.

> Overall impression - a colourful start, but someway to go.

Kudos to Richard for taking advanced search on and, yes, it will require
a lot of effort to get it explained properly. It's a difficult subject.

Cheers,
Fred.

-- 
StrongED Developer
http://www.stronged.iconbar.com/

-- 
To unsubscribe send a mail to StrongED+unsubscribe@xxxxxxxxxxx
List archives at http://diy.Torrens.org/RO/StrongED/index.html