LCB API's

[Ali Lloyd]

Probably instead of dots we would just display the whole syntax then, since
delete element *Start* to *Finish* of *Target *
would be just as illustrative but showing the parameter names as well.

I guess ideally it would be something snappier, in the same way that in the
script dictionary we have
Name: answer file
Syntax: answer file[s] <prompt> [with <defaultPath>] [titled <windowTitle>]
[as sheet]


I think having the library name might also be confusing if it was enclosed
in square brackets as this is the syntax specification for an optional
token in the script dictionary.

Is there a problem with:

 /LeftList/ is /RightList/
 /LeftString/ is /RightString/
 /LeftNumber/ is /RightNumber/
 /LeftBoolean/ is /RightBoolean/
 /LeftData/ is /RightData/

?

Needle is just a general term occasionally used for the thing being
searched for within something else (the Haystack). Possibly that would be
clearer if the other variable were called Haystack. (eg
http://php.net/strstr)


On Tue, Sep 1, 2015 at 3:42 PM jameshale <james at thehales.id.au> wrote:

> In the .mlc file an example syntax definition is of the form:
>
>      "delete" "element" <Index: Expression> "of" <Target: Expression>
>
> where the verbs, for want of a better term, are quoted.
>
> Why can't these be the name that is shown in bold at the top of the entry?
>
> So in the above example the entry would have at the top
> *delete element...of*
>
> The listing entry in the top pane could remain as is or duplicate this with
> the addition of the .mlc file from which it comes.
> say (as well as next entry)....
>
>    delete element...of         [lists]
>    delete element...to...of   [lists]
>
> The "is" operator would be shown as
>    is    [com.livecode.string]
>    is    [com.livecode.list]
>    is    [com.livecode.arithmetic]
>    is    [com.livecode.logic]
>    is    [com.livecode.binary]
>
> instead of...
>     /Left/ is /Right/
>     /Left/ is /Right/
>     /Left/ is /Right/
>     /Left/ is /Right/
>     /Left/ is /Right/
>
>
> The current name could then be called something closer to what it is like
> "engine pseudonym" (just kidding) or something.
>
> "Needle" seems to be a pseudonym for "expression" which is OK just seems
> unneeded.
>
> Thoughts?
>
>
>
>
>
>
> --
> View this message in context:
> http://runtime-revolution.278305.n4.nabble.com/LCB-API-s-tp4695794p4695897.html
> Sent from the Revolution - User mailing list archive at Nabble.com.
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>